All Downloads are FREE. Search and download functionalities are using the official Maven repository.

rvicemix.servicemix-eip.2013.01.source-code.servicemix-eip.xsd Maven / Gradle / Ivy

Go to download

The ServiceMix EIP component is a routing container where different routing patterns can be deployed as service unit.

The newest version!





  
  
    
      
The AsyncBridge uses a correlation identifier to be able to correlate the received
In-Out exchange, the In-Only sent as the request and the In-Only received as the response.
Defaults values are provided to configure those correlation ids. The default behavior
is to use the exchange id of the incoming In-Out exchange as the correlation id and set
it on the request exchange. The same property with the same value should be present on the
response exchange in order for the AsyncBridge to work. ServiceMix components usually take
care of propagating such properties, but failing to propagate it will result in errors.
      ]]>
    
    
      
        
          
            
          
          
            
          
        
        
          
            
          
          
            
          
        
        
          
            
          
          
            
          
        
        
          
            
          
          
            
              
              
            
          
        
        
          
            
          
          
            
          
        
        
          
            
          
          
            
              
              
            
          
        
        
          
            
          
          
            
          
        
        
      
      
        
          
Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
false
which means that an In-Only exchange will be used. When using a Robust-In-Only exchange and when a fault is received, this fault will be sent back to the consumer on the In-Out exchange and the response exchange (if any) would be discarded. For both In-Only and Robust-In-Only, if the request exchange comes back with an Error status, this error will be conveyed back to the consumer in the same way. ]]> Content-Based Router pattern. ]]> Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
Content-Enricher Pattern. ]]> true, message attachments from the incoming exchange and the enricher exchange will be copied to the outgoing message exchange. The default value is false (do not copy message atachments). ]]> true, message properties from the incoming exchange and the enricher exchange will be copied to the outgoing message exchange. The default value is false (do not copy message properties). ]]> Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
sequenceNumberKey property. ]]> Message Filter pattern. ]]> Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
true ]]> Get the service qualified name of the endpoint.

]]>
messageElementName property. ]]> true. ]]> true. ]]> Get the endpoint implementation.

]]>
0 and count - 1 included. ]]> Get the qualified name of the endpoint interface.

]]>
null, messages contents will be appended directly as children of the root element. ]]> false, meaning that such exchanges will be silently sent back with a DONE status and discarded with respect to the aggregation process. ]]> false, meaning that if any error occur, this error will be lost. Note that if this flag is set to true, all exchanges received as part of a given aggregate will be hold until the aggregate is sent and the DONE / ERROR status is received back. ]]> false, meaning that such exchanges will be silently sent back a DONE status. ]]> false, the timeout will expire when the specified amount of time elapsed after the first message is received for this aggregate. If true, the timeout will expire when the specified amount of time elapsed after the last message is received. The default value is false. ]]> Get the service qualified name of the endpoint.

]]>
false. ]]> 0 which means that the timeout is not used at all. ]]>
Resequencer EIP pattern. The aim of this pattern is to put back into correct order a flow of out-of-sequence messages. ]]> Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
Aggregator pattern. This aggregator collect messages with a count, index and correlationId properties. These properties are automatically set by splitters. A timeout may be specified so that the aggregator will not keep data forever if a message is missing. ]]> messageElementName property. ]]> true. ]]> true. ]]> Get the endpoint implementation.

]]>
0 and count - 1 included. ]]> Get the qualified name of the endpoint interface.

]]>
null, messages contents will be appended directly as children of the root element. ]]> false, meaning that such exchanges will be silently sent back with a DONE status and discarded with respect to the aggregation process. ]]> false, meaning that if any error occur, this error will be lost. Note that if this flag is set to true, all exchanges received as part of a given aggregate will be hold until the aggregate is sent and the DONE / ERROR status is received back. ]]> false, meaning that such exchanges will be silently sent back a DONE status. ]]> false, the timeout will expire when the specified amount of time elapsed after the first message is received for this aggregate. If true, the timeout will expire when the specified amount of time elapsed after the last message is received. The default value is false. ]]> Get the service qualified name of the endpoint.

]]>
false. ]]> 0 which means that the timeout is not used at all. ]]>
Recipient List pattern, with the limitation that the recipient list is static. ]]> Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
Routing Slip pattern, with the limitation that the routing table is static. This endpoint only uses In-Out MEPs and errors or faults sent by targets are reported back to the consumer, thus interrupting the routing process. In addition, this endpoint is fully asynchronous and uses an exchange store to provide full HA and recovery for clustered / persistent flows. ]]> Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
The property is interpreted as a boolean value. ]]> WireTap pattern. It can handle all 4 standard MEPs, but will only send an In-Only MEP to the listener. In addition, this component is fully asynchronous and uses an exchange store to provide full HA and recovery for clustered / persistent flows. ]]> true, properties on the in message will be copied to the out / fault message before it is sent. ]]> Get the endpoint implementation.

]]>
Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>
XPathFactory.newInstance(). ]]> XPathFactory.newInstance(). ]]> Splitter pattern using an xpath expression to split the incoming xml. ]]> XPathFactory.newInstance(). ]]> Get the endpoint implementation.

]]>
XPathFactory.newInstance(). ]]> Get the qualified name of the endpoint interface.

]]>
Get the service qualified name of the endpoint.

]]>




© 2015 - 2025 Weber Informatics LLC | Privacy Policy