I have a .jar with EJBs and a .war that invokes these EJBs.
They used to be deployed in a Jboss SOA Platform 5 and now must be in a Jboss EAP 6.
The .war is looking up the EJBs with ejbname/remote. This is hardcoded (I checked with a decomplier).
I know that, in EAP 6, the EJBs are registered in the JNDI like [/<application-name>]/<module-name>/<bean-name>[!<full-qualified-interface-name>].
Is there any way for me to change the JNDI registry name of the EJBs. Maybe via Jboss CLI?
I only have the binaries and have no access to the source.
Related
Since Drools 7.24.0, no .war file for EAP7 is shipped anymore. Any reason why? Can we use the Wildfly war file instead?
How to configure remote EJB connection details in wildfly-config.xml for a EJB client application deployed on JBoss EAP 7.1?
I tried placing it inside /META-INF folder of the EJB Jar and configure below tags but it doesn't seems to work pick the configuration from there.
<configuration>
<jboss-ejb-client xmlns="urn:jboss:wildfly-client-ejb:3.0">
<invocation-timeout seconds="10"/>
<connections>
<connection uri="remote+http://x.y.d.c:8080"/>
</connections>
</jboss-ejb-client>
"wildfly-config.xml" was introduced in EAP 7.1 as a common configuration file for all client configuration files. For EJB it would replace "jboss-ejb-client.properties" file which is configured for EJB standalone client applications.
So ideally I think "wildfly-config.xml" would only work on standalone EJB application, not with the application deployed to JBoss server.
For EJB client deployed on EAP, there is an alternative to configure ejb-receivers "jboss-ejb-client.xml" File and place it in /META-INF folder.
Eg -:
<ejb-receivers>
<!-- This is the connection to access the application. -->
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection-1" />
</ejb-receivers>
Please try the same.
I am converting a glassfish web application (.war) to be able to deploy it on a jboss (wildfly) server.
The original glassfish .war contains a sun-web.xml file. I am simply wondering if I'm required to convert the sun-web.xml file before it can be added to the equivalently converted jboss war.
Stated another way, is the sun-web.xml file compatible with only glassfish servers, or it is also applicable/compatible with jboss?
Thank-you kindly
There is two Weblogic servers with different versions, one is WebLogic Server 12.1.1.0.3 PSU and the other is WebLogic Server 12.1.1.0.6 PSU.
When I install the .ear on the 3 PSU server everything fine, and if I open the deployed instance all the Beans and DAOs are there az the EJBs section.
When I install it on the 6 PSU and open deployment it says: EJBs - None to display however Modules and Web Services are there.
There is an ejb-jar.xml and weblogic-ejb-jar.xml are present with no ejb definitions, because the beans have annotations like #Stateless, #EJB.
Why the server with the old patch finds the EJBs and the newer dont?
Thanks in advance.
Has anyone deployed autopatch (the database upgrade tool) in an ear application (on jboss server). Autopatch supports war kind of applications out of the box but for ear kind of applications it would need some extensions.
Moreover I am unable to provide the .sql files inside the ejb jar inside the ear as the location to look for patches to autopatch. Jboss 5 uses VFS and hence there is no reliable way to know the full URL to the jars.
Thanks in advance.