META-INF.mule-ejb.xsd Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of mule-transport-ejb Show documentation

A Mule transport for Ejb Connectivity that allows you to invoke an ejb object using an endpoint.

There is a newer version: 3.9.0



    
    
    
    
    
        
            The EJB transport allows EJB session beans to be invoked as part of an event flow. Components can be given an EJB outbound endpoint, which will invoke the remote object and optionally return a result.

            The Javadoc for this transport can be found {javadoc:mule/transport/ejb}here{javadoc}.
        
            
        EJB
        EJB Transport
                
                    
        
        
        h2. Using the EJB Connector

        EJB endpoints are configured the same way as [RMI endpoints|RMI Transport]. Note that only outbound endpoints can use the EJB transport. For a given endpoint, you must provide the following information:

        - registry host
        - registry port
        - remote home name
        - remote method name

        These values will be used to establish the dispatcher connection. For example:
        {code:xml}
        <ejb:endpoint host="localhost" port="1099" object="SomeService" method="remoteMethod"/>
        {code}

        Alternatively, you could use URI-based configuration:
        {code:xml}
        <outbound-endpoint address="ejb://localhost:1099/SomeService?method=remoteMethod"/>
        {code}

        If the method can take one or more input arguments, you configure their types as a comma-separated list using the methodArgumentTypes attribute. Multiple arguments are passed in as an array of objects as the payload of the Mule event.

        h2. Transformers

        There are no specific transformers required for EJB.
        
        
    
    
        
        
                The Mule EJB Connector provides connectivity for EJB beans.
        
        
    
    
        
        
            
            
                
                            Period (ms) between polling connections.
                
            
            
            
            
                
                            Bean reference to the security manager that should be used.
                
            
            
            
                        
                
                            The security policy (file name) used to enable connections.
                
            
                    
            
            
                
                            The target class name.
                
            
            
            
            
                
                            The target method.