Hi mr. Jayanti,
You are right, I am sorry. I didn't a wrong manipulation with the used
libraries so nevermind the last message I send.
The problem is in fact like I said but the error is the following:
compile-single:
31-Jan-2008 15:56:14
com.sun.xml.messaging.saaj.soap.MessageImplidentifyContentType
SEVERE: SAAJ0537: Invalid Content-Type. Could be an error message instead
of a SOAP message
31-Jan-2008 15:56:14 com.sun.xml.messaging.saaj.soap.MessageImpl <init>
SEVERE: SAAJ0535: Unable to internalize message
com.sun.xml.messaging.saaj.SOAPExceptionImpl:
java.security.PrivilegedActionException:
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(
HttpSOAPConnection.java:127)
at TstSAAJ.main(TstSAAJ.java:96)
This error hapens when the client and the webservices projects have the SAAJ
1.2.2 library release (from JWSDP1.6).
If both projects use SAAJ 1.3 library release or if the client project use
SAAJ 1.2.2 and webservice project use SAAJ 1.3 release, everything works
fine.
Did I explain weel the problem?
Thanks
On 1/31/08, V B Kumar Jayanti <Vbkumar.Jayanti_at_sun.com> wrote:
>
> Hi Paulo,
>
> Paulo Carvalho wrote:
>
> Hi,
>
> I dowloaded JWSDP 1.5 and JWSDP1.6.
> JWSDP 1.5 comes with the SAAJ 1.2.1_01 release.
> JWSDP 1.6 comes with the SAAJ 1.2.2 release.
>
> 1 - When I have the SAAJ 1.3 libraries on client and webservice projects
> everything works fine.
>
> 2 - When I have the SAAJ 1.2.2 release on client project and SAAJ 1.3release on webservice project, eveything works fine
>
> 3 - Finally, when I have the SAAJ 1.2.2 libraries on both projets, I steal
> have an error, but not the same one. In that way, le client reachs the
> webservice. The error is the next one and hapens when the web service tries
> to get the body of the SOAP message:
>
> The error happens when the webservice calls the getSOAPBody():
>
> public SOAPMessage onMessage(SOAPMessage message) {
> ...
> if(message != null) {
> ...
> SOAPBody inBodyMsg = message.getSOAPBody();
> ...
>
> Error description:
>
> INFO: Server startup in 6718 ms
> java.lang.NullPointerException
> at org.apache.axis2.saaj.SOAPMessageImpl.getSOAPBody(
> SOAPMessageImpl.java:371)
> at crpgl.InfoWSSAAJ.onMessage(InfoWSSAAJ.java:68)
>
>
> I am very confused now, the class org.apache.axis2.saaj.SOAPMessageImpldoes not belong to Sun's SAAJ impl at all. It is an Apache SAAJ Impl class.
>
> regards.
>
> Any idea/suggestion of the cause/solution for this error?
>
> Thanks
>
>
> On 1/31/08, Paulo Carvalho <pjinsc_at_gmail.com> wrote:
> >
> > Hello
> >
> > Thank you for your reply.
> > No errors appends while deploying my webservice and I can access to is
> > WSDL with no problem using IE.
> > Since I am using the SAAJ jar files which were delivered with the
> > jwsdp-1.3, I'm gonna try to get the JWSDP 1.5 or 1.6 version to see if
> > the version is the SAAJ 1.2 and if the error persists.
> >
> > Thanks
> >
> > Best regards
> >
> >
> > On 1/31/08, V B Kumar Jayanti <Vbkumar.Jayanti_at_sun.com> wrote:
> > >
> > > Paulo Carvalho wrote:
> > >
> > > > Hello
> > > >
> > > > I am having a stange problem using SAAJ 1.2 (which I had installing
> > > > jwsdp-1.3 because I can't find anywhere any release of SAAJ 1.2).
> > > >
> > > > Here is the problem. I have a client which sends a SOAP message with
> > > > an attachment to a WebService.
> > > >
> > > > 1 - When my client project and my webservice project have the
> > > > saaj-api.jar and saaj-impl.jar files of SAAJ 1.3 release, everything
> > > > works fine.
> > > >
> > > > 2 - When my client project have the saaj-api.jar and saaj-impl.jar
> > > > files of SAAJ 1.2 release and my webservice project have the
> > > > saaj-api.jar and saaj-impl.jar files of SAAJ 1.3 release, everything
> > > > works fine
> > > >
> > > > 3 - When my client project and my webservice project have the
> > > > saaj-api.jar and saaj-impl.jar files of SAAJ 1.2 release, the
> > > > following error occurs:
> > > >
> > > >
> > > > 31-Jan-2008 10:41:56
> > > > com.sun.xml.messaging.saaj.soap.MessageImpl identifyContentType
> > > > SEVERE: SAAJ0537: Invalid Content-Type. Could be an error message
> > > > instead of a SOAP message
> > > > com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid
> > > > Content-Type:text/html. Is this an error message instead of a SOAP
> > > > response?
> > > > at
> > > > com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(
> > > MessageImpl.java:258)
> > > > at
> > > > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java
> > > :127)
> > > > at
> > > > com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
> > > .<init>(Message1_1Impl.java:43)
> > > > ...
> > > >
> > >
> > > This kind of an error generally means there was a problem in deploying
> > > your webService or that your WebService was not initialized properly
> > > can
> > > you check your server logs. Are you able to access the WSDL of the
> > > service using a Browser.
> > >
> > > A lot of bugs which were in SAAJ 1.2 have been fixed in SAAJ 1.3 so it
> > > may be that you are hitting some bug when using SAAJ 1.2.
> > >
> > > The latest SAAJ 1.2 will be in JWSDP 1.5 or 1.6 i believe.
> > >
> > > regards,
> > > kumar
> > >
> > > >
> > > > 3.1 - To be more specific (I found that trying to figure out
> > > > what was the problem), when my client project have the saaj-api.jar
> > > > and saaj-impl.jar files of SAAJ 1.2 and my webservice project have
> > > the
> > > > saaj-api.jar of SAAJ 1.3 release and have the saaj-impl.jar file
> > > from
> > > > SAAJ 1.2 release, everything works fine!
> > > >
> > > >
> > > > Any help about this strange problem is very welcome!
> > > >
> > > > Regards
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe_at_saaj.dev.java.net
> > > For additional commands, e-mail: users-help_at_saaj.dev.java.net
> > >
> > >
> >
>
>