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 "oc
- 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
>
wrote:
>
> - 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 proble
- 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
sonable stub (with
> > Object's in place of DataHandler). I assume that
> if
> > you stub where to cast
> > the Object returned to a DataHandler, it would
> work
> > as expected... however
> > un-verified at this point.
> >
> > So I think this a
this point.
>
> So I think this answers your question... Axis does
> handle the mime section.
> But other platform implementations MAY not (im still
> unsure) like Micro$uks
> .CRAP Framework.
>
> -Original Message-
> From: Mark Mueller [mailto:[EMAIL PROTEC
.CRAP 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 attah
> -Original Message-
> From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 5:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Interoperative attachments
>
>
> Hmmm. So this means SOAP implementations that *don't* encode MIME
>
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
- Ori
- 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 wo
Title: RE: Interoperative attachments
MIME does use separators (called boundaries in MIME). The code generating the MIME boundary is required to guarantee that the boundary doesn't appear in the payload.
Cheers
Simon
-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROT
EMAIL PROTECTED]'
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: [EMAI
- Original Message -
From: "Norris Merritt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 13:07
Subject: RE: Interoperative attachments
> If you have an binary type of attachment such as image/jpeg, then it has
to
> be Base-64
Title: RE: Interoperative attachments
It doesn't when transported over an 8 bit clean transport (such as http), although Apache SOAP would encode it anyway, don't know if axis does. But that is an implementation limitation, not an issue with MIME itself.
Cheers
Simon
www.pock
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" <[EMA
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: RE: Interoperative attachments
> -Original Message-
> From: Norris Merritt [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 2:09 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Interoperative attachments
>
>
> I've had success with the Axis 1.1 beta DIME support demon
- Original Message -
From: "Norris Merritt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 11:09
Subject: RE: Interoperative attachments
> I've had success with the Axis 1.1 beta DIME support demonstrated in the
> echoAtt
esday, January 28, 2003 2:09 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Interoperative attachments
I've had success with the Axis 1.1 beta DIME support demonstrated in the
echoAttachments sample (which also has a mode in which it uses MIME). Axis
1.1 beta DIME support interoperates both with
rwise 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 Muelle
- Original Message -
From: "Mark Mueller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 28, 2003 08:18
Subject: RE: Interoperative attachments
> Josh,
>
> Yes, I am trying to develop the service that is
> language and platform ne
AIL PROTECTED]]
Sent: Tuesday, January 28, 2003 11:19 AM
To: [EMAIL PROTECTED]
Subject: RE: Interoperative attachments
Josh,
Yes, I am trying to develop the service that is
language and platform neutral, so I'm trying to find
the "right" way to handle attachments. Unfortunately
I do
eller [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 27, 2003 4:32 PM
> 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 a
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 do
rt's to it.
>
> Hope this helps
>
> -Original Message-
> From: Mark Mueller [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 23, 2003 1:27 PM
> To: [EMAIL PROTECTED]
> Subject: Interoperative attachments
>
>
> I've been following this list for we
D]]
Sent: Thursday, January 23, 2003 1:27 PM
To: [EMAIL PROTECTED]
Subject: Interoperative attachments
I've been following this list for weeks now and
concepts are slowly sinking in. I'm still a bit
puzzled by attachments, though.
I'm developing a service that returns a file
I've been following this list for weeks now and
concepts are slowly sinking in. I'm still a bit
puzzled by attachments, though.
I'm developing a service that returns a file to the
client. In the server code I return a DataHandler
object which Axis nicely turns into an attachment. My
concern is t
27 matches
Mail list logo
