Nope. I tried placing saaj libraries in shared lib and made the application classloader to load first which only brought further misery to our problems because of dependencies that saaj libraries have with jdk itself. I am wondering whether to move forward with cxf or opt for a different stack which would satisfy our needs. I know cxf has come too far for it to change the implementations but it would be nice to have support for saaj1.2 similar to what Spring-WS supports wherein we can specify which implementation of SAAJ should be used.
Srinivas dkulp wrote: > > On Thursday 24 April 2008, smodekurti wrote: >> I was trying to add a JaxWS Handler on my Webservice deployed on IBM >> WebSphere 6.1.0.9. I see that the SOAPHandlerInterceptor is failing >> while getting operation name. THe error is >> >> java.lang.IllegalArgumentException: WSWS4100E: Method >> getElementQName() of class javax.xml.soap.SOAPElement is not supported >> in SAAJ 1.2. >> >> This is because cxf uses SAAJ 1.3 while websphere runtime has SAAJ >> 1.2. Is there any work around for this. > > Yea. Websphere's version is a bit too old. > > I THINK if you follow the stuff at: > http://cwiki.apache.org/CXF20DOC/appserverguide.html#AppServerGuide-Websphere > for dealing with wsdl4j but also do it for saaj-impl and saaj-api, it > should work. Not 100% possitive though as I don't have WebSphere to > try it. > > -- > J. Daniel Kulp > Principal Engineer, IONA > [EMAIL PROTECTED] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/CXF-failing-on-Websphere-while-using-Handlers-tp16851517p16895850.html Sent from the cxf-user mailing list archive at Nabble.com.
