Peer Association Deleted Event - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

SDK5 - Plain Java

The following code shows how this can be done with SDK 5 and plain Java event handlers:

import org.alfresco.event.sdk.handling.filter.AssocTypeFilter;
import org.alfresco.event.sdk.handling.filter.EventFilter;
import org.alfresco.event.sdk.handling.handler.OnPeerAssocDeletedEventHandler;
import org.alfresco.event.sdk.model.v1.model.*;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.stereotype.Component;

/**
* Sample event handler to demonstrate reacting to a peer-2-peer assoc being deleted.
*/
@Component
public class Peer2PeerAssocDeletedEventHandler implements OnPeerAssocDeletedEventHandler {
    private static final Logger LOGGER = LoggerFactory.getLogger(Peer2PeerAssocDeletedEventHandler.class);

    public void handleEvent(final RepoEvent<DataAttributes<Resource>> repoEvent) {
        PeerAssociationResource resource = (PeerAssociationResource) repoEvent.getData().getResource();
        LOGGER.info("A Peer-Peer association was deleted: Source {} -> Target {}", resource.getSource().getId(),
                resource.getTarget().getId());
    }

    public EventFilter getEventFilter() {
        return AssocTypeFilter.of("fdk:reviews"); // Make sure the Peer-Peer association is of type FDK Reviews
    }
}

This code uses the org.alfresco.event.sdk.handling.filter.AssocTypeFilter event filter to specify what type of Peer-2-Peer association we are interested in.

For more information about how to extract all the properties from the message payload see the PeerAssociationResource information in Software Development Kits (SDK).

To create an SDK event handler project that uses plain Java event handlers follow the instructions on pure Java event handlers in Software Development Kits (SDK).

SDK5 - Spring Integration

The following code shows how this can be done with SDK 5 and Spring Integration event handlers:

package org.alfresco.tutorial.events;

import org.alfresco.event.sdk.handling.filter.AssocTypeFilter;
import org.alfresco.event.sdk.handling.filter.EventTypeFilter;
import org.alfresco.event.sdk.integration.EventChannels;
import org.alfresco.event.sdk.integration.filter.IntegrationEventFilter;
import org.alfresco.event.sdk.model.v1.model.*;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.integration.dsl.IntegrationFlowAdapter;
import org.springframework.integration.dsl.IntegrationFlowDefinition;
import org.springframework.messaging.Message;
import org.springframework.stereotype.Component;

/**
 * Spring Integration based event handler that will execute code when a peer-2-peer assoc is being deleted.
 */
@Component
public class Peer2PeerAssocDeletedFlow extends IntegrationFlowAdapter {
    private static final Logger LOGGER = LoggerFactory.getLogger(Peer2PeerAssocDeletedFlow.class);

    // Use builder to create an integration flow based on alfresco.events.main.channel event channel
    @Override
    protected IntegrationFlowDefinition<?> buildFlow() {
        return from(EventChannels.MAIN) // Listen to events coming from the Alfresco events channel
                .filter(IntegrationEventFilter.of(EventTypeFilter.PEER_ASSOC_DELETED)) // Filter events and select only Peer2Peer assoc deleted events
                .filter(IntegrationEventFilter.of(AssocTypeFilter.of("fdk:reviews"))) // Make sure the Peer2Peer association is of type FDK Reviews
                .handle(t -> handleEvent(t)); // Handle event with a bit of logging
    }

    private void handleEvent(Message message) {
        RepoEvent<DataAttributes<Resource>> repoEvent = (RepoEvent<DataAttributes<Resource>>)message.getPayload();
        PeerAssociationResource resource = (PeerAssociationResource) repoEvent.getData().getResource();
        LOGGER.info("A Peer-Peer association was deleted: Source {} -> Target {}", resource.getSource().getId(),
                resource.getTarget().getId());
    }
}

This code uses the org.alfresco.event.sdk.handling.filter.AssocTypeFilter event filter to specify what type of Peer-2-Peer association we are interested in.

For more information about how to extract all the properties from the message payload see the PeerAssociationResource information in Software Development Kits (SDK).

To create an SDK event handler project that uses plain Java event handlers follow the instructions on pure Java event handlers in Software Development Kits (SDK).

Apache Camel

The following code snippet shows how this could be done with an Apache Camel route configuration:

public class SimpleRoute extends RouteBuilder {

    @Override
    public void configure() {
        from("amqpConnection:topic:alfresco.repo.event2")
            .id("PeerAssocDeletedRoute")
            .log("${body}") // Log all incoming events on this topic, even those that we are not interested in
            .choice()
            .when() // When the following is true:
            // The event type is peer assoc deleted
            .jsonpath("$[?(@.type=='org.alfresco.event.assoc.peer.Deleted' && " +
                    // and the association type is fdk:reviews
                    "@.data.resource.assocType=='fdk:reviews')]" )
            // Unpack the data into JSON format
            .unmarshal("publicDataFormat")
            // Call a Spring Bean with the event data
            .bean("peerAssocDeletedEventHandlerImpl", "onReceive(*, COPY)")
            .end();
    }
}

The jsonpath expression uses several of the event data properties to filter out exactly the events we are interested in.

In this case a Spring Bean with ID peerAssocDeletedEventHandlerImpl is called at the end of the route from where you could make the necessary ReST API calls.