converted to 1.6 markup
|No differences found!|
The aim of this wiki page is to discuss the issues that may arise when implementing WS-* on top Axis2. Please add your comments under the following headings.
Handling protocol specific messages?
Reliable Asynchronous Messaging Profile: http://xml.coverpages.org/IBM-WS-RAMP-20050826.pdf
Protocol specific messages are sent to the Web service itself. E.g. CreateSequenceRequest message is sent to the Web service and not for a separate service. Dispatching should happen by looking at the <wsa:action> For this scenario adding operations to the service seems correct way to handle it However, these protocol specific messages can be processed and responded at the handlers, without letting them to go till the operation.
I spell out a concern we already discussed for record a) RM suppose to stop any message that do not have RM Headers..( or does it give RM only to messages that has RM Headers (both could be ok for RM .. may be security do not work like that)) b) If yes ..and If we use operation approch, the Secuirty Protocol specific Headers should go past RMHeader, and they do not have RM Headers and so will be stopped
We need to discuss the notion of Handler stopping the messages that do not have given Headers, I see few options to counter this
- Give up the operation injections
- mark the injected Operations with a flag, and stop messsages depend on absense of the Headers IFF they are to reguler operations not injected operations
Give up the notion, the Handlers stop the messages (e.g. We can check for presence of the RMContext ect at the MessageReciver and fails inteligently )
I opt for #2
WS-Coordination Specification: ftp://www6.software.ibm.com/software/developer/library/WS-Coordination.pdf
Coordination Service and the Registration service are again, separate entities and we don’t have the problem that we have in WS-RX.
No protocol specific messages, and hence handled using handlers.
Microsoft Plug Feast, Sample Messages