cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: Bundling ASM in CXF
Date Thu, 30 Oct 2008 01:22:13 GMT
Hi Ian,

I went through the WrapperHelper that you show me. I think the code just
  works as button which enables of disables the WrapperHelperCompiler.
The WrapperHelperCompiler uses the ASM with the hard dependencies and
maven shade plugin will take care of it.

If you have a wrong version ASM for CXF in your class patch and you
can't endorse it with the CXF shipped version, you just need to use the
ASM relocated CXF bundler to go around it.

So I don't think it is necessary to add a cxf-util-asm into the our
maven repository.


Ian Roberts wrote:
> Willem Jiang wrote:
>> I just wrote a pom.xml which leverage the shade plugin to  bundle ASM in
>> CXF. It may help to you.
> Willem,
> I've just done a quick grep through the CXF code and I've noticed that
> besides the hard dependencies (import org.objectweb.asm...) there's one
> place (line 240 of org.apache.cxf.jaxws.interceptors.WrapperHelper in
> rt/frontend/jaxws) where CXF tries to load an ASM class by
> Class.forName.  Is this something the shade plugin can cope with or does
> that need another approach?
> Given the headaches that mismatched ASM versions can cause I'd certainly
> be keen on the idea of using the relocated ASM in CXF by default.  Maybe
> have a new module in the CXF tree that just builds a relocated ASM jar
> and deploys that to your local repository as (say) cxf-util-asm.  Then
> have the other modules depend on that rather than the original ASM and
> use the relocated package names explicitly in the code [I'm not a maven
> expert so please excuse me if I've mis-used some standard terms].
> What do people think of that idea?  One issue might be how does it
> interact with the Apache licensing?  Can one deploy a relocated ASM to
> the apache maven repo?  For reference the ASM licence is
> Ian

View raw message