Hi ND,
Some answers inline.
Thanks
AmilaJ
On Thu, Dec 9, 2010 at 1:39 AM, Nick Duan A-CTR <
[email protected]> wrote:
> Is including WS security policy in WSDL still required in Rampart 1.5?
> It looks like, based on the samples I saw, that client is able to retrieve
> policy directly from a policy file, not from WSDL.
>
I beleive your question is related to client side. To my understanding
client can retreive policy directly from a file as follows,
Options options = serviceClient.getOptions();
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
loadPolicy("/home/aj/development/policy.xml"));
loadPolicy method returns a policy object. Therefore i think it is not
required to include security policy in WSDL (As far as client is concerned).
>
>
> If embedding WS Security Policy inside WSDL, does it contribute anything to
> client stub and server skeleton code generation via wsdl2java? And how?
>
As far as i know wsdl2java does not generate any security policy specific
code. Therefore embedding security policy in WSDL does not contribute
anything to generated code.
>
>
> Thanks!
>
>
>
> ND
>
>
> The information contained in this transmission may contain privileged and
> confidential information.
> It is intended only for the use of the person(s) named above.
> If you are not the intended recipient, you are hereby notified that any
> review, dissemination, distribution or duplication of this communication is
> strictly prohibited.
> If you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> Technica Corporation does not represent this e-mail to be free from any
> virus, fault or defect and it is therefore the responsibility of the
> recipient to first scan it for viruses, faults and defects.
> To reply to our e-mail administrator directly, please send an e-mail to
> [email protected]. Thank you.
>
