|
From: Patrick Y. <kc...@ce...> - 2003-01-28 08:33:53
|
Hi Gait,
Do you think this is a bug of JAXM? Should we (or you) to report this to Sun
JAXM team?
Regards, -Patrick
----- Original Message -----
From: "Gait Boxman" <gai...@ti...>
To: <ebx...@li...>
Sent: Tuesday, January 28, 2003 3:10 PM
Subject: Re: [ebxmlms-general] Problem when sending attachments through
Hermes
> Hi,
>
> I've observed the same problem while doing some tests against other
> receivers. In my case, the other party was responding with a 200 OK
message,
> and a nice HTML document telling me my message was well received. Very
> friendly, but not what the Sun JAXM implementation was expecting.
According
> to the specs, the response is valid unless you're running synchronous
> communications. In fact, any 2XX response is fine when using async
> responses. So I ended up patching JAXM to catch the error on the response
> message.
> Get JAXM 1.1 from SUN, and change line 333 of
>
jaxm1.1-scsl\jaxm-ri\src\com\sun\xml\messaging\saaj\client\p2p\HttpSoapConne
> ction.java to look like:
>
> try {
> response = messageFactory.createMessage(headers, in);
> } catch (SOAPException ex) {
> if( responseCode== HttpURLConnection.HTTP_INTERNAL_ERROR ) {
> throw ex;
> }
> response = null;
> }
>
> then rebuild jaxm, and copy the patched saaj-ri.jar into your ebxmlms.
That
> should do the trick.
> Of course, this will also catch the error while doing synchronous
> communications, which is probably not what we want.
> As an aside, be aware that the createMessage call will print a stack trace
> before the error is caught, so don't worry if you still get the error
trace
> in the tomcat console.
>
> --Gait.
>
> ----- Original Message -----
> From: "V Visvanathan" <vk...@ho...>
> To: <ebx...@li...>
> Cc: <vk...@ho...>
> Sent: Tuesday, January 28, 2003 5:30 AM
> Subject: [ebxmlms-general] Problem when sending attachments through Hermes
>
>
> > Hello everyone:
> > I have this problem when I try to sendan attachment through Hermes.
> > (I was able to send an attachment sometime back, but don't know what
went
> > wrong
> > now)
> >
> > When I use AttachmentDataSource with type "text/xml" and thepayload is a
> xml
> > document, I get an "unable to internalize message: invlaid type
text/html"
> > exception from msh. The message flow (send, ack, etc.) works fine with
no
> > attachments.
> >
> > I saw the message that was being sent, and it has --Part...in the
> beginning.
> > Apparently it is not a valid SOAP message that is being sent.
> >
> > I am using a regular Requestobject to send the message with the listener
> and
> > receivers being servlet URLs.
> >
> > THanks inadvance for ny help.
> >
> > Regards,
> > Visva
> >
> > _________________________________________________________________
> > The new MSN 8: smart spam protection and 2 months FREE*
> > http://join.msn.com/?page=features/junkmail
> >
> >
> >
> > -------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> > http://www.vasoftware.com
> > _______________________________________________
> > ebxmlms-general mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>
|