cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <sberyoz...@gmail.com>
Subject Re: Moving org.apache.cxf.jaxb.attachment from cxf-rt-databinding-jaxb to cxf-common-utilities
Date Fri, 19 Mar 2010 16:10:35 GMT
Hmm...Those classes depend on the CXF Attachment class which lives in the
api module built after the common-utilities.
Moving it into rt/core, org.apache.cxf.attachment.jaxb, may not be the best
idea. I'll probably just add copies to a rt/frontend/jaxrs, given that there
won't be a need to override addSwaRefAttachment()... It is strange indeed
addSwaRefAttachment() is available at the JAXB level...
And then I'll refactor some code into AttachmentUtil in the core

cheers, Sergey

On Fri, Mar 19, 2010 at 3:26 PM, Sergey Beryozkin <sberyozkin@gmail.com>wrote:

> Hi
>
> I need to update a JAXRS JAXBElementProvider to create attachment
> marshallers/unmarshallers for a xop packaging format be supported.
>
> cxf-rt-databinding-jaxb/org.apache.cxf.jaxb.attachment has all the classes
> I need but I'm not sure I should add a strong dependency on
> cxf-rt-databinding-jaxb at this moment of time, instead I suggest moving the
> package to a common-utilities component, which already has an
> org.apache.cxf.jaxb package.
>
> Any objections ?
>
> cheers, Sergey
>
>

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