Re: message id interoperability issue with .net 2.0
Hi, Uthaiyashankar [EMAIL PROTECTED] writes: .NET 2.0 client expects urn:uuid prefix in the message id. (i.e wsa:MessageIDurn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05/wsa:MessageID ). To be able to interoperate with .NET 2.0 it is better to add urn:uuid prefix to message id. WDYT? +1 , after adding urn:uuid to message id please make sure that it won't break other interoperability cases such as Axis2 , Axis etc thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: message id interoperability issue with .net 2.0
Dinesh Premalal wrote: Hi, Uthaiyashankar [EMAIL PROTECTED] writes: .NET 2.0 client expects urn:uuid prefix in the message id. (i.e wsa:MessageIDurn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05/wsa:MessageID ). To be able to interoperate with .NET 2.0 it is better to add urn:uuid prefix to message id. WDYT? +1 , after adding urn:uuid to message id please make sure that it won't break other interoperability cases such as Axis2 , Axis etc We have tested interoperability, and everything works fine. I have committed it to trunk. If possible, we can include this functionality in Axis2/C 1.5.0 Regards, Shankar thanks, Dinesh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]Axis2/C 1.5.0 RC2
Hi All, I have re-packed and uploaded Apache Axis2/C 1.5.0 RC2 here [1]. Please test and send your feedback. [1] http://people.apache.org/~supun/axis2/release_1_5/rc2/ Thanks, Supun..
[jira] Updated: (AXIS2C-595) XPath support in AXIOM
[ https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varuna Parinda Jayasiri updated AXIS2C-595: --- Attachment: xpath.zip XPath support in AXIOM -- Key: AXIS2C-595 URL: https://issues.apache.org/jira/browse/AXIS2C-595 Project: Axis2-C Issue Type: New Feature Components: xml/om Environment: Any Reporter: Malinda Kaushalye Kapuruge Assignee: S.Uthaiyashankar Attachments: xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip, xpath.zip We need to have the X-Path support in AXIOM/C. This is essential in many scenarios where we need to specify a particular set of XML nodes. On example comes with WS-Security Policy where we have to specify a particular node that is needed to be encrypted/signed. Due to lack of X-Path support in AXIOM we are forced to find alternative methods. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
