could the cxf-codegen-plugin use a parent-last classloader to avoid conflict with Java6 JAXB 2.0 API ?

2008-08-22 Thread nicolas de loof
I'm trying to use CXF 2.1.2 codegen, my dev environment beeing based on jrockit 6.0 - that includes jaxb 2.0 API (as SUN java 6 did prior to update ? ) I get a generation error (with a nice message) due to requirement for JAXB 2.1, but JAXB 2.0 beeing loaded from bootclasspath. As the cxf-codegen-

Re: could the cxf-codegen-plugin use a parent-last classloader to avoid conflict with Java6 JAXB 2.0 API ?

2008-08-22 Thread nicolas de loof
Something like this ... /** * A custom ClassLoader to hidde the system classloader JAXB-API that may * be incompaible with requirement for JAXB-2.1 */ public class OverrideJaxbApiClassLoader extends URLClassLoader { /** A dedicated classloader to access the JAXB 2.1 API */ private URLC

Re: could the cxf-codegen-plugin use a parent-last classloader to avoid conflict with Java6 JAXB 2.0 API ?

2008-08-22 Thread nicolas de loof
metro does something similar ( http://weblogs.java.net/blog/kohsuke/archive/2007/02/howitworks_runn.html) but the classloader code is under GPL :-/ The general idea of a masking classloader could be used anymay. 2008/8/22 nicolas de loof <[EMAIL PROTECTED]> > Something like this ... > > /** > *

Re: Server Response Policy

2008-08-22 Thread Sergey Beryozkin
Hi I reckon it would be useful if it were possible to explicitly state in the CXF WS-Policy feature that a given policy expression is inbound/outbound only. Perhaps another option is to provide reusable policy interceptors which could simply (and blindly) assert some policies using preconfigure