entity-rmi-invoker : a RMI/JRMP configuration for entity beans

clustered-entity-rmi-invoker : a RMI/JRMP configuration for clustered entity beans

stateless-rmi-invoker : a RMI/JRMP configuration for stateless session beans

clustered-stateless-rmi-invoker : a RMI/JRMP configuration for clustered stateless session beans

stateful-rmi-invoker : a RMI/JRMP configuration for clustered stateful session beans

clustered-stateful-rmi-invoker : a RMI/JRMP configuration for clustered stateful session beans

message-driven-bean : a JMS invoker for message driven beans

singleton-message-driven-bean : a JMS invoker for singleton message driven beans

message-inflow-driven-bean : a JMS invoker for message inflow driven beans

jms-message-inflow-driven-bean : a JMS inflow invoker for standard message driven beans

iiop : a RMI/IIOP for use with session and entity beans.

name : The name element gives a unique name for the invoker-proxy-binding. The name is used to reference the binding from the EJB container configuration when setting the default proxy binding as well as the EJB deployment level to specify addition proxy bindings. You will see how this is done when we look at the jboss.xml elements that control the server side EJB container configuration.

invoker-mbean : The invoker-mbean element gives the JMX ObjectName string of the detached invoker MBean service the proxy invoker will be associated with.

proxy-factory : The proxy-factory element specifies the fully qualified class name of the proxy factory, which must implement the org.jboss.ejb.EJBProxyFactory interface. The EJBProxyFactory handles the configuration of the proxy and the association of the protocol specific invoker and context. The current JBoss implementations of the EJBProxyFactory interface include:

proxy-factory-config : The proxy-factory-config element specifies additional information for the proxy-factory implementation. Unfortunately, its currently an unstructured collection of elements. Only a few of the elements apply to each type of proxy factory. The child elements break down into the three invocation protocols: RMI/RJMP, RMI/IIOP and JMS.

client-interceptors : The client-interceptors define the home, remote and optionally the multi-valued proxy interceptor stacks.

web-class-loader : The web class loader defines the instance of the org.jboss.web.WebClassLoader that should be associated with the proxy for dynamic class loading.

web-class-loader : The web class loader defines the instance of the org.jboss.web.WebClassLoader that should be associated with the proxy for dynamic class loading.

poa : The portable object adapter usage. Valid values are per-servant and shared.

register-ejbs-in-jnp-context : A flag indicating if the EJBs should be register in JNDI.

jnp-context : The JNDI context in which to register EJBs.

interface-repository-supported : This indicates whether or not a deployed EJB has its own CORBA interface repository.

MinimumSize : This specifies the minimum pool size for MDBs processing . This defaults to 1.

MaximumSize : This specifies the upper limit to the number of concurrent MDBs that will be allowed for the JMS destination. This defaults to 15.

MaxMessages : This specifies the maxMessages parameter value for the createConnectionConsumer method of javax.jms.QueueConnection and javax.jms.TopicConnection interfaces, as well as the maxMessages parameter value for the createDurableConnectionConsumer method of javax.jms.TopicConnection. It is the maximum number of messages that can be assigned to a server session at one time. This defaults to 1. This value should not be modified from the default unless your JMS provider indicates this is supported.

KeepAliveMillis : This specifies the keep alive time interval in milliseconds for sessions in the session pool. The default is 30000 (30 seconds).

MDBConfig : Configuration for the MDB JMS connection behavior. Among the elements supported are: