Hi Dennis, Actually i have reported a JIRA for this some time ago:
https://issues.apache.org/jira/browse/AXIS2-2426 Regards, Angel On 4/11/07, Angel Todorov <[EMAIL PROTECTED]> wrote:
Hi Dennis, I have also tried it but it doesn't work, at least with Rampart (WS-SecurityPolicy in mind). What it should do is automatically configure the rampart module on the client side (engage, etc.) Otherwise, when using WS-SecurityPolicy I don't get any value out of wsdl2java if I still have to manually modify the generated code. Regards, Angel On 4/11/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote: > The release notes have mentioned Neethi WS-Policy support since 1.1, but > it's unclear to me exactly what this means. When I try to embed > WS-Policy statements in a WSDL and use WSDL2Java I either get an NPE > from the Neethi code (showing that at least the Neethi code is being > called), or WSDL2Java runs to completion but nothing appears to be > different in the generated code. > > I thought WSDL2Java was supposed to be extracting the WS-Policy > information from the WSDL and using it to configure Rampart and/or > Sandesha2. Is anything going on with this? > > Thanks, > > - Dennis > > -- > Dennis M. Sosnoski > SOA and Web Services in Java > Training and Consulting > http://www.sosnoski.com - http://www.sosnoski.co.nz > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
