Forum Discussion
epolkerman
14 years agoNew Contributor
Hi Ole,
Thanks for your fix. It works as expected and now the default identifier complies to the RfC.
But now the next problem arises. SoapUI uses the optional <wsrm:Offer> element in de CreateSequence message. The only child element SoapUI uses is <wsrm:Identifier>. But if the RM source uses the offer part in WS-RM version 1.1 (and 1.2 also) in the CreateSequence, also the <wsrm:Endpoint> element must be included. Below follows an example (with only mandatory elements):
<wsrm:CreateSequence>
<wsrm:AcksTo> wsa:EndpointReferenceType </wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier> xs;anyURI </wsrm:Identifier>
<wsrm:Endpoint> wsa:EndpointReferenceType </wsrm:Endpoint>
</wsrm:Offer>
</wsrm:CreateSequence>
Because of the optionality of the <wsrm:Offer> element, it would be nice if that part is also configurable in SoapUI.
Question: should I make (in the future) a new post? The newly described problem has in fact nothing to do with the original problem description.
Thanks for your fix. It works as expected and now the default identifier complies to the RfC.
But now the next problem arises. SoapUI uses the optional <wsrm:Offer> element in de CreateSequence message. The only child element SoapUI uses is <wsrm:Identifier>. But if the RM source uses the offer part in WS-RM version 1.1 (and 1.2 also) in the CreateSequence, also the <wsrm:Endpoint> element must be included. Below follows an example (with only mandatory elements):
<wsrm:CreateSequence>
<wsrm:AcksTo> wsa:EndpointReferenceType </wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier> xs;anyURI </wsrm:Identifier>
<wsrm:Endpoint> wsa:EndpointReferenceType </wsrm:Endpoint>
</wsrm:Offer>
</wsrm:CreateSequence>
Because of the optionality of the <wsrm:Offer> element, it would be nice if that part is also configurable in SoapUI.
Question: should I make (in the future) a new post? The newly described problem has in fact nothing to do with the original problem description.