dkulp wrote: > > On Thursday 21 August 2008 8:35:30 am [EMAIL PROTECTED] wrote: >> Which versions of this standards will be supported in future versions od >> CXF? > >>> Right now, for ws-securitypolicy, I'm targetting 1.2. However, the >>> model >>> supports 1.1 as well since 1.2 is mostly extensions to 1.1. That said, >>> the >>> underlying tools we use (wss4j for example), don't support everything we >>> need >>> for full compatibility with some of the ws-security profiles and such. >>> (xpaths for example) > >>> WS-Policy itself is another story. Right now, it only seems to support >>> the >>> 1.5 framework. It doesn't recognize the 1.2 framework namespace. I >>> ran >>> into this problem pulling some metro based ws-secpol policies into the >>> tests. >>> If I get a chance, I may go back and update the ws-p stuff to at least >>> support the 1.2 namespace. > >>> In anycase, I'd be very interesting in any "ws-security policy" >>> documents/fragments that you might have so I can see what users find >>> important so I can tackle those first. > >>> Any help implementing it would be great too. :-) I'd be more than >>> happy to >>> help someone out that would like to dive into some of that code and >>> contribute. :-) > > -- >>>Daniel Kulp >>>[EMAIL PROTECTED] >>>http://www.dankulp.com/blog > >
Thank You for answer. My task was to write wsdl for my web service with using standards which works on both ALSB 3.0 and CXF. But ALSB is using is own security policy standard (namespace: http://www.bea.com/wls90/security/policy). WS-Policy is from http://schemas.xmlsoap.org/ws/2004/09/policy namespace Regards, mariusz -- View this message in context: http://www.nabble.com/ws-securitypolicy-ws-policy-tp19089256p19196570.html Sent from the cxf-user mailing list archive at Nabble.com.
