Hi Thilina Thanks. The way I see it (referring to my example here) is that only the "Outerboundary " is missing.
Regards Stefan. On Thu, 2007-01-04 at 16:17 +0530, Thilina Gunarathne wrote: > Hi Stefan, > Only now I realized the real issue you have mentioned in the previous mail.. > > If Axis2 shows that behaviour, then it's definitely a bug... The > boundary should be the same as the one given in the header.. > > I'll test and correct it... > > Thanks, > Thilina > > > > 1) Control of SWA attachment types. Base64 or Binary for example. > > > > I understand and agree that binary is the best but not all target > > servers/applications will necessarily support binary attachments. This I > > suppose is not critical as one can create a datahandler to take care of > > it, but it would be great to have. > > 2) That the Mime boundary used in the header is used to end the message > > for example: > > > > POST /uri HTTP/1.1 > > Content-Type: multipart/related; boundary="OuterBoundary"; > > type=text/xml; start="</maerx-200102/mm7-submit>" > > . > > . > > . > > --OuterBoundary > > --InnerBoundary > > . > > --InnerBoundary > > . > > --InnerBoundary-- > > --OuterBoundary-- > > > > My motivation: > > > > 1) It will make axis2 more flexible. > > 2) Its unlikely that I will be the only person in the world with this > > need. I realize that this is a matter of RFC and other standards > > interpretation. But the MM7 spec interprets it so and I am sure there > > might be more. > > > > > > I understand that axis2 is a very large and complex project and that > > there is a lot more to consider than my two reasons. At the same time > > let me express my appreciation and admiration for the Axis team. I know > > that I am not capable of what they are doing. So please view this as > > constructive. > > > > Regards > > Stefan. > > > > PS. Curently using 2.1.1 > > > > On Wed, 2007-01-03 at 16:25 +0200, Stefan Kok wrote: > > > Hi Thilina > > > > > > I have found this article on the IBM website : > > > > > > http://www-128.ibm.com/developerworks/webservices/library/ws-soapatt/?open&l=930,t=grws#figure1 > > > > > > They also end it off with the MIME boundary the stated in the header. > > > > > > Regards > > > Stefan. > > > > > > > > > > > > On Wed, 2007-01-03 at 15:23 +0200, Stefan Kok wrote: > > > > Hi Thilina > > > > > > > > Yes I agree the RFC's is very vague on the subject. Wiki is somewhat > > > > better. I have found one other reference to axis on the subject [1] I > > > > think its axis 1. > > > > > > > > [1] http://article.gmane.org/gmane.text.xml.axis.devel/38906/match= > > > > > > > > My problem is that I am coding for the MM7 Spec. It does not leave me > > > > any choice. All mmsc servers fail my messages with "MM7 > > > > multipart/related message must have exactly two parts". They are looking > > > > for the last MIME boundary as I have indicated. See the sample below. > > > > > > > > POST /mm7 HTTP/1.1 > > > > Content-Type: multipart/related; boundary="OuterBoundary"; > > > > type=text/xml; start="</maerx-200102/mm7-submit>" > > > > . > > > > . > > > > . > > > > --OuterBoundary > > > > --InnerBoundary > > > > . > > > > . > > > > . > > > > --InnerBoundary-- > > > > --OuterBoundary--[*] > > > > > > > > [*] The messages ends here. > > > > > > > > Would it be possible for me to change the axis2 source code to put it > > > > in. I suppose the problem is then I wont have a standard axis2 > > > > implementation. Which will painful long term. > > > > > > > > Please let me know what you are thinking. > > > > > > > > Regards > > > > Stefan. > > > > > > > > > > > > On Wed, 2007-01-03 at 18:21 +0600, Thilina Gunarathne wrote: > > > > > Stefan, > > > > > It's the MIME boundary you are talking about. It is required according > > > > > to the MIME specs.. MIME packaging works based on this boundary.. It > > > > > is used to separate out the MIME parts.. AFAIK It is not possible to > > > > > change that.. > > > > > > > > > > You can find the MIME RFC's here[1]... Unfortunately they are not so > > > > > straight forward regarding the use of this boundary.. Wikipedia seems > > > > > to be doing more justice to the definition of boundary [2] than the > > > > > RFC's. > > > > > > > > > > ~Thilina > > > > > > > > > > [1] http://www.mhonarc.org/~ehood/MIME/ > > > > > [2] http://en.wikipedia.org/wiki/MIME#Multipart_Messages > > > > > > > > > > On 1/3/07, Stefan Kok <[EMAIL PROTECTED]> wrote: > > > > > > I have looked at the mm7 spec. All their multipart/related > > > > > > messages > > > > > > end with the boundary in the header. I still am not sure if this is > > > > > > applies only to mm7 or not. > > > > > > > > > > > > Would it be possible to change this behavior ? Or is it by design ? > > > > > > > > > > > > Regards > > > > > > Stefan. > > > > > > > > > > > > On Wed, 2007-01-03 at 08:25 +0200, Stefan Kok wrote: > > > > > > > I have noticed that when SWA sends a multipart/related message it > > > > > > > looks > > > > > > > like: (Trimmed to keep it short) > > > > > > > > > > > > > > > > > > > > > POST /mm7 HTTP/1.1 > > > > > > > SOAPAction: "" > > > > > > > User-Agent: Axis2 > > > > > > > Content-Length: 37588 > > > > > > > Content-Type: multipart/related; > > > > > > > boundary=MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015337975; > > > > > > > type="text/xml"; > > > > > > > start="<0.urn:uuid:[EMAIL PROTECTED]>"; > > > > > > > charset=UTF-8 > > > > > > > Authorization: Digest username="username", realm="somerealm", > > > > > > > nonce="RZs7zw==babe2df5bea49ce4", uri="/some", response="44a", > > > > > > > qop=auth, > > > > > > > nc=00001, cnonce="e4c3c3", algorithm="MD5" > > > > > > > Host: fqdn:8080 > > > > > > > > > > > > > > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343 > > > > > > > content-type: text/xml; charset=UTF-8 > > > > > > > content-transfer-encoding: 8bit > > > > > > > content-id: <0.urn:uuid:[EMAIL PROTECTED]> > > > > > > > > > > > > > > <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header><mm7:TransactionID > > > > > > > > > > > > > > xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"; > > > > > > > > > > > > > > mustUnderstand="1">MyTransaction</mm7:TransactionID></soapenv:Header> > > > > > > > <soapenv:Body> > > > > > > > . > > > > > > > . > > > > > > > .<Content href="urn:uuid:A9D5ECF2C417B3D84B11678015319801" /> > > > > > > > </SubmitRequest> > > > > > > > </soapenv:Body> > > > > > > > </soapenv:Envelope> > > > > > > > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343 > > > > > > > content-type: image/jpeg > > > > > > > content-transfer-encoding: binary > > > > > > > content-id: <urn:uuid:A9D5ECF2C417B3D84B11678015319801> > > > > > > > > > > > > > > ......JFIF.............>Exif..II*.......................ACD > > > > > > > Systems > > > > > > > Digital Imaging.....ACD Systems Digital > > > > > > > Imaging.......d....".......................... > > > > > > > .. > > > > > > > .. > > > > > > > ...............("..&...#/#&)*---.!141+4(,-+..........@ > > > > > > > +$+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@...% > > > > > > > 67U..............................................A..! > > > > > > > 1.Q.".Bq............?...E...,..o.pi=...R...F;....Mul0.d.. > > > > > > > .c......QK .R f..k....?n/.&.....o.K..X.....vN(.....8.....m..(. > > > > > > > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343 > > > > > > > content-type: application/octet-stream > > > > > > > content-transfer-encoding: binary > > > > > > > content-id: <urn:uuid:A9D5ECF2C417B3D84B11678015321042> > > > > > > > > > > > > > > #!AMR > > > > > > > [EMAIL PROTECTED] > > > > > > > "X....IM.8L..:....Cl'[EMAIL PROTECTED]:.C[E..W.}..4S..,... > > > > > > > .u=Ge.&[EMAIL > > > > > > > PROTECTED]@.6b.Qs.N.....L....w....W..).\.A....{K"..gC.3.go.!......8.\'[EMAIL > > > > > > > PROTECTED]:[EMAIL PROTECTED]"....`...[T.KU. > > > > > > > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343-- > > > > > > > > > > > > > > Should it not end something like: > > > > > > > > > > > > > > [EMAIL PROTECTED]"....`...[T.KU. > > > > > > > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343-- > > > > > > > --boundary=MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015337975-- > > > > > > > [1] > > > > > > > > > > > > > > [1] Taken from the header. > > > > > > > > > > > > > > I have seen many samples with this format. I am not an expert but > > > > > > > it > > > > > > > seems odd. > > > > > > > > > > > > > > Kind regards > > > > > > > Stefan. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > -- > > > > > > Stefan Kok <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > -- > > Stefan Kok <[EMAIL PROTECTED]> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- Stefan Kok <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
