ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Ws Wiki] Update of "FrontPage/WsFx/wsfx-axis2" by JaliyaEkanayake
Date Thu, 17 Nov 2005 04:02:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by JaliyaEkanayake:
http://wiki.apache.org/ws/FrontPage/WsFx/wsfx-axis2

------------------------------------------------------------------------------
+ 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?'''
+ 
+ = WS-SecureConversation/ WS-Trust =
+ ''Specification:'' ftp://www6.software.ibm.com/software/developer/library/ws-secureconversation.pdf
+ 
+ RequestSecurityToken message and other protocol specific messages are intended to separate
Web services. E.g. SecurityTokenService
+ 
+ = WS-RelibaleExchange =
+ ''Specification:'' http://xml.coverpages.org/WS-ReliableMessaging200502.pd
+ ''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. 
+ 
+ = WS-Coordination/ WS-Trust =
+ ''WS-Coordination Specification:'' ftp://www6.software.ibm.com/software/developer/library/WS-Coordination.pdf
+ ''WS-Trust Specification:'' ftp://www6.software.ibm.com/software/developer/library/ws-trust.pdf
+ 
+ Coordination Service and the Registration service are again, separate entities and we don’t
have the problem that we have in WS-RX
+ 
  = WS-Security =
- = WS-SecureConversation =
- = WS-Trust =
- = WS-ReliableExchange =
+ ''Specification:'' http://www.verisign.com/wss/wss.pdf
+ 
+ No protocol specific messages, and hence handled using handlers.
+ 
  = Resources =
- == Plug Feast, Sample Messages ==
+ '''Microsoft Plug Feast, Sample Messages'''
     http://131.107.72.15/ilab/wcfinteroplab.htm
  

Mime
View raw message