On Thursday 17 January 2008, Rodriguez, Jose wrote: > Hi All, > > I need some help with Websphere 6.1 and CXF. I wrote a Web Services > client (using basic authentication) with CXF. I followed these > instructions nto setup Websphere: > http://cwiki.apache.org/confluence/display/CXF20DOC/AppServerGuide#App >ServerGuide-Websphere > > But I have the same issue than this guy: > http://www.ibm.com/developerworks/forums/thread.jspa?messageID=1401773 >3 > > Basically WAS 6.1 checks the annotation and complains about > org.apache.cxf.js.rhino.DOMPayloadProvider not implemented in the > right way. Is this guy from IBM right?
Well, yes and no. For the Axis implementation, yes. He is correct. The spec only mandates that you HAVE to support Provider<Source>. (and Provider<SOAPMessage>) However, it does allow other Provider<foo> things. DOMSource is a specialization for CXF that the axis implementation apparantely doesn't like. > Our generated client uses only standard Web services annotations and > we have to use a HTTPConduit. > > Any ideas how to disable this check or to make it works? Well, I guess the only suggestion would be to not use the big cxf-2.0.3-incubator.jar in lib and instead use all the cxf-*-2.0.3-incubator.jar jars in the modules directory EXCEPT for the cxf-rt-frontend-js-2.0.3-incubator.jar that is there. Thus, that specific provider wouldn't be in the jar. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
