|
First, I will be mentioning Muse quite a bit in this email, but stay with me. My question/issue does seem to resolve around Axis.
My goal is to deploy multiple WARs in the same container that each contains a web service built using muse 1.0. Upon deploying a second WAR, I receive a NameAlreadyBoundException and am unable to deploy.
The only solution I could come up with meant deploying one the un-touched Muse exploded WAR, and then another WAR for each of my web services (this way all of my web services could consume the resources deployed from the Muse WAR). This did not work at first, as the axis servlet deployed in the muse WAR does not know about the services deployed in any of my other WARs. So, I added the axis servlet in each of my web services’ WAR as well. When attempting to deploy one of my web service WARs after the muse WAR, a NullPointerException was thrown due to the fact I had removed items from the jndi-config.xml in the web service WAR that were already included in the muse WAR. To fix this, I have to add those items back into the jndi-config.xml, which in turns throws the original NameAlreadyBoundException I received.
To summarize, it seems as though I cannot deploy an axis servlet in two separate WARs in the same container due to the fact they each require items in their own jndi-config.xml (which causes the NameAlreadyBoundException upon deployment of the second WAR).
1) Is there any way to deploy an Axis servlet in one WAR and utilize that one axis servlet for web services in other, separate WARs? 2) Is it true that the axis servlet must have certain items in its WAR’s jndi-config.xml, even if those resources are already available? (I don’t really know much about JNDI. My understanding is a resource listed in JNDI is globally available in the container. So, it seems that a second axis-servlet should be able to consume those resources without having them listed in its jndi-config.xml)
Chad Sturtz Associate Consultant Gestalt, LLC
Office: 417.626.6521 Cell: 618.920.3437 Fax: 417.625.1810
|
