Nice catch Mark!!!
-Original Message-
From: Mark Mueller [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 8:19 PM
To: [EMAIL PROTECTED]
Subject: RE: Interoperative attachments (MIME types)
I think I may have solved the problem. I think
there's a misspelling of octet-stream
Framework.
-Original Message-
From: Mark Mueller [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 4:09 PM
To: [EMAIL PROTECTED]
Subject: RE: Interoperative attachments
Folks,
I originally used the method in the EchoAttachments
sample which did use MIME to send the attahcment
.
-Original Message-
From: Mark Mueller [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 4:09 PM
To: [EMAIL PROTECTED]
Subject: RE: Interoperative attachments
Folks,
I originally used the method in the EchoAttachments
sample which did use MIME to send the attahcment
PROTECTED]]
Sent: Tuesday, January 28, 2003 4:09 PM
To: [EMAIL PROTECTED]
Subject: RE: Interoperative attachments
Folks,
I originally used the method in the
EchoAttachments
sample which did use MIME to send the attahcment
--
but the WSDL identified the type
- Original Message -
From: Mark Mueller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 30, 2003 17:19
Subject: RE: Interoperative attachments (MIME types)
I think I may have solved the problem. I think
there's a misspelling of octet-stream in line 702
:
- Original Message -
From: Mark Mueller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 30, 2003 17:19
Subject: RE: Interoperative attachments (MIME types)
I think I may have solved the problem. I think
there's a misspelling of octet-stream in line
702
- Original Message -
From: Mark Mueller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 30, 2003 19:48
Subject: Re: Interoperative attachments (MIME types)
Steve,
What would be the downside of mapping any MIME type to
a java.lang.Object by default (via
To: [EMAIL PROTECTED]
Subject: RE: Interoperative attachments
Josh,
This was very helpful -- thanks a lot! I've
implemented my service this way, and I return the URL
of the attachment content-id as the return-value of
the call.
I have another question. The WSDL created by
Java2WSDL doesn't
need
to be Base-64 encoded. Its much more efficient than MIME.
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 9:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Interoperative attachments
- Original Message -
From: Mark Mueller [EMAIL
]'
Subject: RE: Interoperative attachments
If you have an binary type of attachment such as image/jpeg, then it
has to
be Base-64 encoded if MIME is used
-Original Message-
From: Dan Allen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 12:40 PM
To: [EMAIL PROTECTED]
Subject
- Original Message -
From: Dennis Sosnoski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 28, 2003 14:15
Subject: Re: Interoperative attachments
Hmmm. So this means SOAP implementations that *don't* encode MIME
attachments work as long as the data being sent doesn't
Thanks, its useful to know that MIME over HTTP doesn't require encoding of
binary attachments.
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 1:41 PM
To: [EMAIL PROTECTED]
Subject: Re: Interoperative attachments
- Original
Josh,
This was very helpful -- thanks a lot! I've
implemented my service this way, and I return the URL
of the attachment content-id as the return-value of
the call.
I have another question. The WSDL created by
Java2WSDL doesn't mention the file that I return as an
attachment. Should I
Mark,
After working with Axis for a while then migrating to BEA Weblogic, I have
found that the best way to attach files is to do it through handlers.
However it's equaly as viable to do it in your Web Service for example:
Message message =
14 matches
Mail list logo
