|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Already fixed this :( Sanjiva Weerawarana wrote: > Please open a JIRA .. the ID must be a URI; what we're generating > is wrong. > > Sanjiva. > > On Tue, 2006-01-24 at 19:10 -0500, Tony Dean wrote: > >> Hi, >> >> I am starting to integrate some attachment processing into my >> webservices and found problem with MS [MS client/Axis2 server]. >> >> They complain about WS-A messageID not being a valid URI. >> >> Here's a sample of what Axis2 sends: <wsa:MessageID >> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">2B5D48043825641218113814178055274</wsa:MessageID> >> >> >> >> And here's a sample of what MS sends and expects: >> <wsa:MessageID>urn:uuid:2a5b38c2-c87a-4c10-9dd8-3753e2cbfefb</wsa:MessageID> >> >> >> >> This may be an interpretation issue, but it causes non-interop. >> The WS-A spec does say that it must be a valid URI. >> >> What do you guys thing? >> >> I will be happy to open a JIRA. >> >> Thanks, Tony >> >> Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED] >> >> SAS... The Power to Know http://www.sas.com >> > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) iD8DBQFD3abajON2uBzUhh8RAqtiAJ0fSGL1iI1Jz6iHnnDiUO15lSsG4ACcCM7W jp9Yl5LGQqMiPFDyp8AwKqw= =foO8 -----END PGP SIGNATURE----- |
