cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject Re: policy namespace change
Date Wed, 25 Apr 2007 18:08:30 GMT
On 4/25/07, Andrea Smyth <andrea.smyth@iona.com> wrote:
>
> Dan Diephouse wrote:
>
> > It seems the http://www.w3.org/2006/07/ws-policy/ policy namespace is
> > deprecated and we should use http://www.w3.org/ns/ws-policy/ now
> instead.
> > Should we make the switch internally before 2.0?
>
> I have no problems with that.


Cool.

>
> > Also, I noticed PolicyConstants is tied to one specific version. Does
> > this
> > mean we can't support both 1.2 and 1.5 inside CXF?
>
> Actually we can - but not simultaneously -  there is a
> setNamespace(String ns) in PolicyConstants,  and change the static
> initialiser in PolicyContants to switch the default.
> Not sure if it's more work to modify existing resources, or to adjust
> the runtime for these tests to use the old
> http://www.w3.org/2006/07/ws-policy/ though, which 's is what I have
> done to reuse the neethi test resources for policy normalisation (they
> use the http://schemas.xmlsoap.org/ws/2004/09/policy namespace).
> Could improve that by making PolicyConstants a configurable instance,
> available either attached to another dynamically created object
> (PolicyBuilder or PolicyEngine) or as a BusExtension itself.
>
> Andrea.


In my mind it'd be ideal if we could just support all transparently. I don't
know how feasible that is though.  I would have to poke around the policy
layer a lot more.  At the very least what you propose is a good step in that
direction.

- Dan

-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message