You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Rakesh Saxena <ra...@yahoo.com> on 2006/01/24 00:14:18 UTC
Question - How can i use cactus.jar in two independent Web Services in one WAS server? ( details below)
NOTE, the following problem does not arise in case of "Single Class Loader" option. But, I need to use "Multi Class Loader" option in one WAS server due to deployment restriction of other services. I am using the 1.7.1 cactus.jar.
ANY SUGGESTION TO FIX THIS PROBLEM is greatly appeciated.
THE PROBLEM IS DESCRIBED BELOW:
When two separate web service apps (Plan & Claims in this case) are deployed in the same WAS server, the cactus.jar & its class no longer remains available to the second app. And the following error is reported:
" .. Error finding class [test.com.assurant.soap.ClaimsSoapTest] using both the Context classloader and the webapp classloader. Possible causes include: - Your webapp does not include your test classes, - The cactus.jar is not located in your WEB-INF/lib directory and your Container has not set the Context classloader to point to the webapp one ..."
Kindly, let us know if there is a way to fix this issue, or how can we point "context class loader" to "web app class loader" as suggested in the error log above.
Infact, the interesting thing is that both Web Service starts fine with MULTI Class loader option. But as soon as Junit test is run on one service its Service1SoapTest is recognized and test shows success. But when the second service is invoked by Junit test; its class ( for example, Claims) ClaimsSoapTest shows as not found.
I look forward to hearing from you.
Thank you,
rakeshsaxena2003@yahoo.com