|
Saminda Yes.. it should be like this.. let me explain with an example If you want to enable WS-RM/Security etc on a Proxy service you could do as follows: <proxy name="JMSInvesbotSequenceProxy" transports="jms" description="This uses the stockquote named sequence for mediation"> <syn:enableRM/> <syn:enableSec/> <target sequence="stockquote"/> <parameter name="transport.jms.ConnectionFactory" locked="true">myTopicConnectionFactory</parameter> <parameter name="transport.jms.Destination" locked="true">dynamicTopics/something.TestTopic</parameter> </proxy> If you want to enable WS-RM/Security etc on messages going to an Endpoint you could do as follows: <endpoint name="invesbot" address="http://ws.invesbot.com/stockquotes.asmx"> <syn:enableRM/> <syn:enableSec/> </endpoint> The above examples would cause WS-Security and WS-RM to be engaged on the proxy service, and for all messages destined to the endpoint. This would be the (whatever) "default" WS-RM/Sec configuration that applies in the above cases. If you want to specify custom properties (say RM attributes or security) you could use a Policy and attach it to the proxy service. The mediators to perform WS-RM/Security would apply for *incoming* messages only, and the mediators would send them through Sandesha/Rampart etc. allowing WS-Sec/RM to be available for message level mediation as well. (as opposed to service level mediation with proxy services). These mediators would be something like follows: <RMMediator> <SecurityMediator> Maybe we could allow the attachment of policies to the mediator as well, and this is open for discussion. The main point to note is that 1) We will have a neat way to specify RM/Sec on Proxy services and endpoints 2) We will have mediators to perform RM/Security asankha Saminda Abeyruwan wrote: Hi Devs,--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] |
