Jboss-ejb-client.xml: Difference between revisions
(Created page with "=Internal= * WildFly Deployment Descriptors =Overview=") |
No edit summary |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
jboss-ejb-client.xml is a JBoss-specific deployment descriptor to be included within artifacts deployed on JBoss ''server instances'', which contains configuration that will be used to setup an EJB client context for that deployment. For more details about the EJB client context see: | |||
{{Internal|EJB Concepts#EJB_Client_Context|EJB Client Context}} | |||
jboss-ejb-client.xml is a deployment descriptor to be included with server deployment artifacts. It is usually part of WAR deployments that want to call into remote EJBs. A somewhat equivalent semantics for standalone EJB clients is provided by the [[Jboss-ejb-client.properties|jboss-ejb-client.properties]] configuration file. | |||
=Location= | |||
The deployment descriptor must be present in the /META-INF directory of the JAR or EAR, or in the /WEB-INF directory of the WAR. | |||
=Example= | |||
<pre> | |||
<jboss-ejb-client xmlns:xsi="urn:jboss:ejb-client:1.2" xsi:noNamespaceSchemaLocation="jboss-ejb-client_1_2.xsd"> | |||
<client-context> | |||
<ejb-receivers> | |||
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-container-1"/> | |||
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-container-2"/> | |||
</ejb-receivers> | |||
</client-context> | |||
</jboss-ejb-client> | |||
</pre> | |||
=Required Server Configuration= | |||
The above example will only work if the server instance to be deployed into has its remoting subsystem configured accordingly. The required configuration is described here: | |||
{{Internal|JBoss_Instance_Configuration_to_Support_Deployed_EJB_Client_Contexts|JBoss Instance Configuration to Support Deployed EJB Client Contexts}} | |||
Latest revision as of 20:33, 24 March 2017
Internal
Overview
jboss-ejb-client.xml is a JBoss-specific deployment descriptor to be included within artifacts deployed on JBoss server instances, which contains configuration that will be used to setup an EJB client context for that deployment. For more details about the EJB client context see:
jboss-ejb-client.xml is a deployment descriptor to be included with server deployment artifacts. It is usually part of WAR deployments that want to call into remote EJBs. A somewhat equivalent semantics for standalone EJB clients is provided by the jboss-ejb-client.properties configuration file.
Location
The deployment descriptor must be present in the /META-INF directory of the JAR or EAR, or in the /WEB-INF directory of the WAR.
Example
<jboss-ejb-client xmlns:xsi="urn:jboss:ejb-client:1.2" xsi:noNamespaceSchemaLocation="jboss-ejb-client_1_2.xsd">
<client-context>
<ejb-receivers>
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-container-1"/>
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-container-2"/>
</ejb-receivers>
</client-context>
</jboss-ejb-client>
Required Server Configuration
The above example will only work if the server instance to be deployed into has its remoting subsystem configured accordingly. The required configuration is described here: