[ 
https://issues.apache.org/jira/browse/CAMEL-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880161#comment-16880161
 ] 

Claus Ibsen edited comment on CAMEL-13678 at 7/8/19 1:59 PM:
-------------------------------------------------------------

I have not migrated the components and we dont rely on attachments api for 
camel-core. There is a new camel-attachments JAR that has this logic. This also 
makes using Camel on JDK9+ onwards easier as you dont have to add attachments 
JAR because it was not in the JDK anymore and camel-core required it - now its 
just like any component with transitive dependencies via camel-attachments.

Outstanding work
- Update karaf feature *DONE*
- Consider storing attachments somewhere else than exchange property



was (Author: davsclaus):
I have not migrated the components and we dont rely on attachments api for 
camel-core. There is a new camel-attachments JAR that has this logic. This also 
makes using Camel on JDK9+ onwards easier as you dont have to add attachments 
JAR because it was not in the JDK anymore and camel-core required it - now its 
just like any component with transitive dependencies via camel-attachments.

Outstanding work
- Update karaf feature
- Consider storing attachments somewhere else than exchange property


> Attachments API on Message - Deprecate and remove
> -------------------------------------------------
>
>                 Key: CAMEL-13678
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13678
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0, 3.0.0.M5
>
>
> We should consider making the Camel Message API more simpler and remove stuff 
> that are seldom in use, or can be component specific.
> The javax.attachment is removed from JDK11 onwards and its not really much in 
> use in the future.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to