-
1. Re: JMS Bridge from WildFly 10 to JBoss 5
mnovak Jul 31, 2017 7:48 AM (in response to timhallwachs)Hi Tim,
JNDI properties for JBoss 5 are different. afaik those are:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.provider.url=jnp://127.0.0.1:1099 java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
Also you will need to create new module with JBoss 5 jars for JNDI lookup and this module must be configured in configuration of JMS bridge like <jms-bridge name="jms-test-bridge" module"org.legacy-jboss-jndi" ... >
Module must be located $WF_HOME/modules directory. I'm not able to say the complete list of jars which you will need but I guess that at least following jars from JBoss 5 are required:
jnp-client.jar
jboss-messaging-client.jar
Thanks,
Mirek -
2. Re: JMS Bridge from WildFly 10 to JBoss 5
timhallwachs Jul 31, 2017 8:37 AM (in response to mnovak)Hi Mirek,
thanks for your help.
I try to create a new module (the first time for me).
Thanks,
Tim
-
3. Re: JMS Bridge from WildFly 10 to JBoss 5
mnovak Aug 1, 2017 4:36 AM (in response to timhallwachs)Creating new module is simple. Create new directory in "modules" dir, for example ..../modules/org/jboss/legacy-jndi/main/ and copy all jars there. Then create module.xml file in this directory which will name this module and include all jars. You can inspire how this file look like in any other module :-)
-
4. Re: JMS Bridge from WildFly 10 to JBoss 5
timhallwachs Aug 1, 2017 10:45 AM (in response to mnovak)Thanks a lot.
With the new module the bridge works fine.
I need the following jars in my new model:
- concurrent.jar
- javassist.jar
- jboss-aop-client.jar
- jboss-common-core.jar
- jboss-logging-spi.jar
- jboss-mdr.jar
- jboss-messaging-client.jar
- jboss-remoting.jar
- jnp-client.jar
- log4j.jar
- trove.jar
-
5. Re: JMS Bridge from WildFly 10 to JBoss 5
mnovak Aug 2, 2017 1:31 AM (in response to timhallwachs)You're welcome! :-)