Hi Sam,
I have a similar deployment scenario where I have incorporated the SOAP 2.2
web.xml with my applications and I have deployed it as a war file into tomcat.
The only issue I found is that unless the class you're trying oto access
through SOAP is defined in the classpath that starts tomcat, then the SOAP 2.2
class loading code fails. I have tried to figure out how it is possible to
deploy a self-contained WAR file which has a soap interface without having to
alter the classpath of the servlet container itself and no one has given a
clear explanation of why this is. Perhaps this time someone else will
clarify... I looked at the code, but I was unable to find anything strange
about the way class loading was done. In the meantime, if you add a jar file
containing the class to the weblogic classpath, you should be able to access it
correctly..
hope this helps,
-javier
Suntian Qian wrote:
> I used to deploy SOAP application using WebLogic 6.0 for NT with other web
> application. It works fine. When I try to combined these two web application
> together by incorporate SOAP admin JSPs into the other application and
> combined web.xml, everything seems fine: I can still deploy and list the
> services. But when I make the SOAP call, it gave me such exception:
>
> [Aug 03 11:01:42] ERROR: soap: [Attributes={}] [faultCode=SOAP-ENV:Server]
> [faul
> tString=Exception from service object: null]
> [faultActorURI=/servlet/rpcrouter]
> [DetailEntries=] [FaultEntries=]
>
> Looks like the service object cannot be created. Since in WebLogic, web
> application cannot easily access components from another application, that's
> why I want to deploy them together. Can SOAP be deployed by being
> incorporated in another application? My understanding is that so long as
> rpcservlet is defined and mapped correctly, it should be fine.
>
> Any insight into this issue?
>
> Thanks very much!
>
> Sam
