Re: WSDL MIME Issues

        Simon,

        thanks for your reply, I'll go back to the person who pointed in
your direction and see if their memory can be jogged some more.

        I did look on your WSDL issues list and didn't see anything that
related to the need to define each and every attachment as a specific part.
?

        A lot of newsgroup chat in this area often resolves the use of
attachments for requirements to send large files etc.. so a bunch of people
must have come across it.

        From your DIME comment below, does that mean that there is potential
for resolution within the WSDL/DIME bindings spec ?

        Fraser.



        From:   Simon Fell <[email protected]> on 08/01/2003 04:08
        Please respond to Discussion of implementing SOAP applications today
<[email protected]>@SMTP@NUExchange
        Office Phone No:
        To:     [email protected]@SMTP@NUExchange
        cc:
        Subject:        Re: [SOAP] WSDL MIME Issues

        HI,

        I remember saying this part "All in all, WSDL & Attachments is not a
        good place to be !" but I can't remember where exactly. I didn't
write
        the rest.

        The problem with the WSDL  MIME binding is that it can't describe
SOAP
        messages that have arrays of attachments. see
        http://groups.yahoo.com/group/soapbuilders/message/8105 for an
example
        SwA message that can't be described using the WSDL MIME binding. I
        don't see how the approach below would really solve that problem, as
        its not a SwA problem, but a WSDL problem.

        I'd say use DIME, but in practical terms its no better off, there is
a
        draft WSDL DIME binding, but I'm not aware that anyone supports it
        yet.

        All in all, WSDL & Attachments is not a good place to be !

        Sorry, probably not what you want to hear.
        Cheers
        Simon
        www.pocketsoap.com

        On Tue, 07 Jan 2003 10:34:47 +0000, in soap you wrote:

        >Simon,
        >
        >I been trying to track down an article that is attributed to you
concerning
        >the use of SwA/multipart MIME and WSDL.
        >
        >Specifically, I am trying to figure a way of being able to create a
WSDL
        >that allows for an arbritary number of attachment parts associated
with an
        >input or output message.
        >
        >I was given this snippet, but is there more ??
        >
        >Cheers
        >
        >Fraser
        >
        >== snippet begins
        >
        >"All in all, WSDL & Attachments is not a good place to be !"
        >
        >However that doesn't mean the end of the line. You can create a
"content
        >mime part"  that uses a  multipart/related media type, e.g.
        >
        ><mime:part>
        ><mime:content part="body" type="multipart/related;
        >boundary=BoUnDaRy-987123"/>
        ></mime:part>
        >
        >This places all of the content "body parts" into one body part
within the
        >SwA multipart/related envelope. These "sub body parts" are
accessible to a
        >mime parser via the Content-ID contained in the href associated
with each
        >part from within the SOAP body.
        >
        >=== snippet ends

        You can read messages from the SOAP archive, unsubscribe from SOAP,
or subscribe to other
        DevelopMentor lists at http://discuss.develop.com.




**********************************************************************
This email and any files sent with it are intended only for the named
recipient. If you are not the named recipient please telephone/email
the sender immediately. You should not disclose the content or
take/retain/distribute any copies.
**********************************************************************


Norwich Union Insurance Limited
Registered Office 8 Surrey Street Norwich
Norfolk NR1 3NG
Registered in England Number 99122
Member of the General Insurance Standards Council

For Further enquiries 01603 622200

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.