There is another similar thread on this. Glen Mazza points to the CXF documentation discussing this in that thread as well.
http://cxf.547215.n5.nabble.com/CXF-Websphere-7-not-working-td5518335.html#a5518859 Here was a note from that thread: http://www.jroller.com/gmazza/entry/deploying_webservices_on_websphere And then the CXF doc ref is here: http://cxf.apache.org/docs/application-server-specific-configuration-guide.html#ApplicationServerSpecificConfigurationGuide-ForWebSphere6.1.0.29%2CV7andV8 On Mon, Feb 27, 2012 at 10:18 AM, kumarasamyr <[email protected]> wrote: > When third-party JAX-WS applications(CXF or Metro) is deployed on *WAS > 6.1*, > the Application Server's JAX-WS Web services engine must be disabled so it > doesn’t conflict with the third-party implementation. > > Can anyone explain how to do that in WAS 6.1 please? > > I know there is an option in admin console to make PARENT Classloader to be > loaded last. but can't do this in all the environments and also it doesn't > work with some JARs. > > There might be a existing post which explains this but I couldn't catch > that. > > Thanks a lot. > > Kumar > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/How-to-disable-JAX-WS-Web-services-engine-in-WAS-6-1-tp5519221p5519221.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Mark * *
