Nandana: Thanks for your reply. 1) is WS-Security Policy the preferred approach. If so where can I see some exampels on how to do dynamically using code. May be the policy examples has one for dynamic configuration. 2) I guess you meant it is recommended not to use the OutflowConfiguration. 3) Also could you point me to some good resource on WS Security policy. My requirement is to invoke Webservice using dynamic code ( no wsdl2java) with WS-Security.
Regards, cabear On Fri, Jan 30, 2009 at 7:18 PM, Nandana Mihindukulasooriya < [email protected]> wrote: > Yes, In Rampart , there are two configurations. One used custom > configuration language and the other option uses standard WS - Security > Policy. You are looking in to the custom configuration one which is > deprecated. Please look at the Rampart policy based samples (samples/policy) > for policy based configuration. It also can be configured either using files > or dynamically using code. > > thanks, > nandana > > > > On Fri, Jan 30, 2009 at 6:43 AM, Wishing Carebear < > [email protected]> wrote: > >> OutflowConfiguration is deprecated. >> Right now I'm able to do dynamic invocation using OperationClient and >> OutflowConfiguration for WSSecurity. Is there any other equivalent for >> OutflowConfiguration that is recommended. >> >> >> On Thu, Jan 29, 2009 at 4:47 PM, Wishing Carebear < >> [email protected]> wrote: >> >>> Got the source code from Googling :) >>> >>> >>> >>> On Thu, Jan 29, 2009 at 2:08 PM, Wishing Carebear < >>> [email protected]> wrote: >>> >>>> Hello: Read the following of sample 11 for dynamic configuration with >>>> axis2 for WSSeurity. But could not find the file in Rampart distribution. >>>> Could someone point me to the location where I can get it: >>>> >>>> >>>> http://blog.sweetxml.org/2007/12/rampart-basic-examples-how-you-add-ws.html >>>> 11. Dynamic configuration : Get rid of the config files ... let's use >>>> code! >>>> >>>> Both client and servce are configured to first sign and then encrypt the >>>> outgoing message and to decrypt and verify the incoming message using their >>>> key pairs. >>>> >>>> Note that we don't use any parameters in the client.axis2.xml, see >>>> org.apache.rampart.samples.sample11.Client's >>>> getOutflowConfiguration() and getInflowConfiguration() methods and >>>> their usage. >>>> Thanks, cabear >>>> >>> >>> >> > > > -- > Nandana Mihindukulasooriya > WSO2 inc. > > http://nandana83.blogspot.com/ > http://www.wso2.org >
