0

I've built a web service using WSE 3.0 that should interface with various other platforms like IBM's WebSphere. In the addressing part of the request the content of MessageID needs to be in the format uuid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Anything else results in a "Bad Request" error. I've been told that according to WS-Addressing RFC MessageID can contain anything. Is there a way to allow a MessagdID that doesn't conform to that format?

Thanks!

System Down
  • 6,192
  • 1
  • 30
  • 34

1 Answers1

1

From memory: I think the MessageID in WSE is a URI. I guess you can try with any string that has a URL moniker (http, ftp etc) and a string after that.

Charles Prakash Dasari
  • 4,964
  • 1
  • 27
  • 46
  • Any kind of format is troublesome since the client has his own in house format. – System Down Dec 14 '09 at 05:51
  • Then you have tough luck. WS-Addressing states that the Message ID is a URI. "A URI that uniquely identifies this message in time and space. No two messages with a distinct application intent may share a [message id] property." ... snip ... "The value of this property is an opaque URI whose interpretation beyond equivalence is not defined in this specification." See: http://www.w3.org/Submission/ws-addressing/#_Toc77464322 – Charles Prakash Dasari Dec 14 '09 at 07:18
  • Thanks for that link. I always suspected this, but having an official ruling on it would definitely help in convincing the other party. Thanks again. – System Down Dec 20 '09 at 06:17