Since Drools 7.24.0, no .war file for EAP7 is shipped anymore. Any reason why? Can we use the Wildfly war file instead?
Related
I have a JBoss EAP 6.4 implementation which runs a bunch of separate applications within it. All living in the same WAR file.
For one of those applications I want to modify the class-path. Specifically I want it to exchange two jars for two others.
Is that possible?
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.
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
A war file created from weblogic server. Is that same war file work in websphere Server
Maybe. Depends on if any weblogic-specific features were used, or if you stuck to the servlet spec.
I would like to use a custom version of the HSQL DB in an application that I am deploying in JBoss. However, JBoss already contains an HSQLDB.jar. The JBoss jar is being resolved by my application instead of the custom jar in my ear.
How can I use a different version of HSQL in my web application from the one that JBoss uses internally?
Can I remove the HSQLDB.jar included with JBoss without negatively impacting the Application Server?
The custom version it's just a newer version? If it's that the case than you can simply replace the jar in the Jboss lib folder. Jboss uses HSQLDB as far as I know for queue persistence.