Hi Thilina, What do you mean Axis2 preserve the order?
I tried the attachment test in Axis2 1.2. At that time, I can see that the order of the attachment is not preserved, at least by default the order is not preserve. I encountered scenarios that I even encountered scenarios that I retrieved attachment parts before SOAP body when I iterated the AttachmentMap. The WS-I Attachment Profile 1.0 Final R2921 specifies that the order of mime parts should not be inferred from the parts definition in WSDL. I.e., the order of attachment parts should not be preserved. Hi skudx, Which order do you want to preserve? You want the attachment parts have the same order as the definition in WSDL, or you want the attachment parts received in the same order as they are sent? As for the former order, it should not be preserved as specified by WS-I Attachment Profile 1.0 Final R2921. As for the latter order, the AttachmentMap is a map, I don't know how you can preserve the order. Maybe some Axis2 developer can help you. But as a walkaround, I would prefer to use the contentID or some element specified in the WSDL Schema part to associate each attachment part with a name. Regards, Xinjun On 10/17/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > > But as for preserving the order of attachments, I don't think Axis2 > > developers will consider this request. > I think we do support that... Can you please double check and let us > know whether it's broken. > > thanks, > Thilina > > >You should not rely on the order of > > the attachments. You should use something like contentID or name to > > associate an ID with certain attachment. > > > > > > Regards, > > Xinjun > > > > > > > > On 10/10/07, skudx <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi Thilina/ Xinjun, > > > > > > Could you pl have a look at > > https://issues.apache.org/jira/browse/AXIS2-3245 > > > & give me some pointers to move ahead? > > > > > > My current requirements force me to use jax-ws-ri on the server-side & > > axis2 > > > on the client-side. The request/ response messages typically have more > > than > > > one binary attachments and the order of attachments must be preserved. > > > > > > Thanks > > > Regards > > > > > > > > > -- > > > View this message in context: > > > http://www.nabble.com/-Axis2-1.2--Axis2-attachment-interoperability----tf3906797.html#a13125936 > > > Sent from the Axis - User mailing list archive at Nabble.com. > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > -- > Thilina Gunarathne - http://thilinag.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
