Hi Skudx, I suggest you handle MessageContext directly if you want to solve the attachment interoperability issue. The MessageContext give you flexibility to handle your attachments.
Axis2 recommend the use of "start" parameter but doesn't mandate it. I have tested that. But as for preserving the order of attachments, I don't think Axis2 developers will consider this request. 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] > >
