gcdbrown2011
asked on
spring web services
Hi,
I am developing a SOAP web service using Spring 3.0, Spring-WS, SpringSource toolsuite
running tc server v6. When I run the application on the server, I get the following
exception in SpringSource toolsuite.
"type Exception report message description
The server encountered an internal error () that prevented it from fulfilling this request.
exception javax.servlet.ServletExcep tion: Wrapper cannot find
servlet class org.springframework.ws.tra nsport.htt p.MessageD ispatcherS ervlet
or a class it depends on
com.springsource.insight.c ollection. tcserver.r equ est.
HttpRequestOperationCollec tionValve. invoke(Htt pRequestOp erationCol lectionVal ve.java:60 )
org.apache.catalina.valves .ErrorRepo rtValve.in voke(Error ReportValv e.java:102 )
org.apache.catalina.connec tor.Coyote Adapter.se rvice(Coyo teAdapter. java:293)
org.apache.coyote.http11.H ttp11Proce ssor.proce ss(Http11P rocessor.j ava:849)
org.apache.coyote.http11.H ttp11Proto col$Http11 Connection Handler.pr ocess(Http 11Protocol .java:583)
org.apache.tomcat.util.net .JIoEndpoi nt$SocketP rocessor.r un(JIoEndp oint.java: 379)
java.util.concurrent.Threa dPoolExecu tor$Worker .runTask(T hreadPoolE xecutor.ja va:886)
java.util.concurrent.Threa dPoolExecu tor$Worker .run(Threa dPoolExecu tor.java:9 08)
java.lang.Thread.run(Threa d.java:619 )"
The org.springframework.ws.tra nsport.htt p.MessageD ispatcherS ervlet class is contained within
the spring-ws-core-2.0.0.RELEA SE.jar which is on my classpath.
I have verified that the .JAR is contained within the WAR file but still getting the above exception.
any help is appreciated.
Thanks, George
I am developing a SOAP web service using Spring 3.0, Spring-WS, SpringSource toolsuite
running tc server v6. When I run the application on the server, I get the following
exception in SpringSource toolsuite.
"type Exception report message description
The server encountered an internal error () that prevented it from fulfilling this request.
exception javax.servlet.ServletExcep
servlet class org.springframework.ws.tra
or a class it depends on
com.springsource.insight.c
HttpRequestOperationCollec
org.apache.catalina.valves
org.apache.catalina.connec
org.apache.coyote.http11.H
org.apache.coyote.http11.H
org.apache.tomcat.util.net
java.util.concurrent.Threa
java.util.concurrent.Threa
java.lang.Thread.run(Threa
The org.springframework.ws.tra
the spring-ws-core-2.0.0.RELEA
I have verified that the .JAR is contained within the WAR file but still getting the above exception.
any help is appreciated.
Thanks, George
http://forum.springsource.org/showthread.php?t=49488
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In the above link mention that u need include saaj-api-1.3 & saaj-impl-1.3 on my classpath.
and security jar deatils .
>>in adsense of relevent expert reply I worked on this until I came to above solution myself.
Dear gcdbrown2011: All are give idea only no one going to work for you !!
and security jar deatils .
>>in adsense of relevent expert reply I worked on this until I came to above solution myself.
Dear gcdbrown2011: All are give idea only no one going to work for you !!
Thats why in pointing they are giving (grading a- fully help and b-particalue help)
I Have some link he accept that link info is helped him but he didnt accept my solution
ASKER
The link does not work for Spring 3.0, which the question related to. The link listed 8 jars:
* jaxen
* jdom
* saaj-api
* saaj-impl
* spring
* spring-ws-core
* spring-ws-core-tiger
* spring-xml
The solution required 29 jars. Of the 8 listed, in the link, only 4 were relevant. When I tried the solution in the link, and it did not work, I then went back to Maven rather than guessing which JARs to include.
* jaxen
* jdom
* saaj-api
* saaj-impl
* spring
* spring-ws-core
* spring-ws-core-tiger
* spring-xml
The solution required 29 jars. Of the 8 listed, in the link, only 4 were relevant. When I tried the solution in the link, and it did not work, I then went back to Maven rather than guessing which JARs to include.