You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/06/20 07:11:00 UTC

[jira] Closed: (CAMEL-526) Attachment support - avoid dependency on JAF

     [ https://issues.apache.org/activemq/browse/CAMEL-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen closed CAMEL-526.
-----------------------------

    Resolution: Won't Fix

Not possible. Camel 1.4 is also nearly out of the door with this dependency.

> Attachment support - avoid dependency on JAF
> --------------------------------------------
>
>                 Key: CAMEL-526
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-526
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>             Fix For: 1.5.0
>
>
> CAMEL-385 added attachment support to camel 1.4 but it requires the JAF jar on the classpath for camel-core even though end users does not use the attachment support at all.
> We should try to avoid this dependency and let somekind of delegate/lazy init determine of the JAF jar is on the classpath or not - As AXIS 1.x does and logs that activation is not supported since class XXX was not found on the classpath
> See more on the forum:
> http://www.nabble.com/Attachment-support-in-camel-core-depends-on-JAF-but-where-is-it-td16931910s22882.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.