Our commercial application used to run on different application servers, and we began to configure it to run on the JBoss server. The problem is that this application launches JBoss cache and as part of the integration with this infrastructure, web-inf \ lib contains the following banks:
jboss-aop.jar, jbosscache-core.jar, jboss-common.jar, jboss-common -core.jar, jboss-j2ee.jar, jboss-jmx.jar, jboss-logging-spi.jar
This causes a problem using JNDI through the application because jboss-common-core.jar contains a naming package that makes JBoss JNDI work incorrectly. Therefore, I need to find a way to organize my banks, which, on the one hand, will be stored in the jboss cache, and on the other hand, do not interfere with JNDI
Perhaps this includes moving some or all of these jars from web-inf \ lib to / server / default / lib Searching for someone familiar with this topic
(continuation of this topic:
https://stackoverflow.com/questions/2847375/problem-configure-jboss-to-work-with-jndi3
)
source
share