[Installation, Configuration & Deployment] - Isolating web app classpath
by sselda
Hi.
I have two web apps:
- an older web app (directory app-prod.war in server/default/deploy)
- a newer web app (directory app-dev.war in server/default/deploy)
the two web apps are the same project, an older and a newer release.
The jars inside every WEB-INF/lib are the same, the newer has obviously new classes or new methos/attributes.
I use:
- JDK 1.4.2
- JBoss 3.2.6
- Spring 1.2.8
- Struts 1.2.9
- Web app version 2.4
When I start JBoss, the app-dev web app cannot deploy correctly because starts after app-prod web app. I think uses in its classpath the jars in WEB-INF/lib of the oldest web app: in fact it doesn't see the changes described in its Spring XML files because uses the jars of app-prod, which is inconsistent with XML files of more recent app-dev.
If I undeploy app-prod.war and reboot JBoss, app-dev.war is deployed correctly.
My questions are:
1) is there any JBoss configuration to set to force every web app uses in its classpath only the jar specified in the shared libraries and its WEB-INF/lib or WEB-INF/classes and not the jar specified in other web apps?
2) is there any JBoss configuration to set to force insert of jars in WEB-INF/lib and classes in WEB-INF/classes in classpath before shared libraries to prevent version incompatibility with jar's older version existing for example in server/default/lib?
NOTE: the same web apps in Tomcat 5.0.28 standalone starts correctly without problems.
Thanks
sselda
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990382#3990382
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990382
19 years
[JCA/JBoss] - Re: Integrating / Deploying SunOne OpenMessageQueue with JBo
by jsalvo
FYI .... I have implemented a JMSProviderAdapter taken from the code in this link:
http://swforum.sun.com/jive/thread.jspa?threadID=45414
.. although instead of using LDAP, I am simply using a filestore for the administered objects. I have then created a JAR for the the JMSProviderAdapter implementation class, placed it into server/lib.
Then I added the following in deploy/jms/jms-ds.xml ( I did NOT replace the DefaultJMSProvider ):
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=SunOneJMSProvider">
| <attribute name="ProviderName">SunOneJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JMSProviderAdapterSunOneImpl
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">java:/SunOneXAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">java:/SunOneQueueXAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">java:/SunOneTopicXAConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
| java.naming.provider.url=file:///home/jsalvo/workspace/softgame-latest/development/conf/sunone/mq/test
| </attribute>
| </mbean>
|
So far, everything is starting up ... though I have not yet tried anything useful.
Will update soon.
John
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990378#3990378
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990378
19 years