You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Oliver Wulff <ow...@progress.com> on 2009/03/18 21:32:06 UTC
AW: Does anyone successfully deployed CXF services with WS-Security (Signature and Encyrption) in WebSphere 6.1
Hi Lawrence
I had also problems to deploy a CXF based application into websphere 6.1. The problem was also related to saaj. I've then configured a seperate classloader on the websphere server(!) level for saaj and wsdl4j. I've referenced the cxf libraries on the websphere application level. Please ensure that you configure the child-first option for the classloaders (don't have the exact naming in mind).
Websphere 6.1 ships an older saaj library.
HTH
Thanks
Oliver
-----Ursprüngliche Nachricht-----
Von: Lawrence Johnbosco [mailto:lawrence.johnbosco@gmail.com]
Gesendet: Mi 18.03.2009 21:23
An: users@cxf.apache.org
Betreff: Does anyone successfully deployed CXF services with WS-Security (Signature and Encyrption) in WebSphere 6.1
Hello,
Does anyone successfully deployed CXF services with WS-Security (Signature
and Encyrption) in WebSphere 6.1?
I followed the wiki instructions for Webshpere but ran into some issues (
java.lang.NoClassDefFoundError:
com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl ) and I fixed this by
removing the SAAJ jars from CXF application.
However, while sending an encrypted and signed request, the web service
application hangs and the Client failes with Timeout exception.
Thanks,
Lawrence Johnbosco
Re: Does anyone successfully deployed CXF services with WS-Security (Signature and Encyrption) in WebSphere 6.1
Posted by Daniel Kulp <dk...@apache.org>.
On Thu March 19 2009 4:30:49 pm Lawrence Johnbosco wrote:
> Thanks for the direction. I tried with all that and got into the following
> issue:
> This error indicates that the class:
> com.sun.org.apache.xerces.internal.dom.DocumentImpl could not be located
> while defining the class: com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl
Add the jaxp-ri jar from:
http://repo1.maven.org/maven2/com/sun/xml/parsers/jaxp-ri/1.4.2/
For Sun JVM's, that jar is built in so the classes are found. That's not
true for the IBM JDK so you need to add them into your application
classloader.
Dan
> Thanks,
> Lawrence
>
> On Wed, Mar 18, 2009 at 4:32 PM, Oliver Wulff <ow...@progress.com> wrote:
> > Hi Lawrence
> >
> > I had also problems to deploy a CXF based application into websphere 6.1.
> > The problem was also related to saaj. I've then configured a seperate
> > classloader on the websphere server(!) level for saaj and wsdl4j. I've
> > referenced the cxf libraries on the websphere application level. Please
> > ensure that you configure the child-first option for the classloaders
> > (don't have the exact naming in mind).
> >
> > Websphere 6.1 ships an older saaj library.
> >
> > HTH
> >
> > Thanks
> > Oliver
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Lawrence Johnbosco [mailto:lawrence.johnbosco@gmail.com]
> > Gesendet: Mi 18.03.2009 21:23
> > An: users@cxf.apache.org
> > Betreff: Does anyone successfully deployed CXF services with WS-Security
> > (Signature and Encyrption) in WebSphere 6.1
> >
> > Hello,
> >
> > Does anyone successfully deployed CXF services with WS-Security
> > (Signature and Encyrption) in WebSphere 6.1?
> >
> > I followed the wiki instructions for Webshpere but ran into some issues (
> > java.lang.NoClassDefFoundError:
> > com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl ) and I fixed this by
> > removing the SAAJ jars from CXF application.
> >
> > However, while sending an encrypted and signed request, the web service
> > application hangs and the Client failes with Timeout exception.
> >
> > Thanks,
> > Lawrence Johnbosco
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Does anyone successfully deployed CXF services with WS-Security
(Signature and Encyrption) in WebSphere 6.1
Posted by Lawrence Johnbosco <la...@gmail.com>.
Thanks for the direction. I tried with all that and got into the following
issue:
This error indicates that the class:
com.sun.org.apache.xerces.internal.dom.DocumentImpl could not be located
while defining the class: com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl
Thanks,
Lawrence
On Wed, Mar 18, 2009 at 4:32 PM, Oliver Wulff <ow...@progress.com> wrote:
> Hi Lawrence
>
> I had also problems to deploy a CXF based application into websphere 6.1.
> The problem was also related to saaj. I've then configured a seperate
> classloader on the websphere server(!) level for saaj and wsdl4j. I've
> referenced the cxf libraries on the websphere application level. Please
> ensure that you configure the child-first option for the classloaders (don't
> have the exact naming in mind).
>
> Websphere 6.1 ships an older saaj library.
>
> HTH
>
> Thanks
> Oliver
>
>
> -----Ursprüngliche Nachricht-----
> Von: Lawrence Johnbosco [mailto:lawrence.johnbosco@gmail.com]
> Gesendet: Mi 18.03.2009 21:23
> An: users@cxf.apache.org
> Betreff: Does anyone successfully deployed CXF services with WS-Security
> (Signature and Encyrption) in WebSphere 6.1
>
> Hello,
>
> Does anyone successfully deployed CXF services with WS-Security (Signature
> and Encyrption) in WebSphere 6.1?
>
> I followed the wiki instructions for Webshpere but ran into some issues (
> java.lang.NoClassDefFoundError:
> com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl ) and I fixed this by
> removing the SAAJ jars from CXF application.
>
> However, while sending an encrypted and signed request, the web service
> application hangs and the Client failes with Timeout exception.
>
> Thanks,
> Lawrence Johnbosco
>
>