[jira] [Updated] (CAMEL-7978) QuartzEndpoint should share the same camel context name when it working in cluster mode
[ https://issues.apache.org/jira/browse/CAMEL-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7978: Component/s: (was: camel-quartz) QuartzEndpoint should share the same camel context name when it working in cluster mode --- Key: CAMEL-7978 URL: https://issues.apache.org/jira/browse/CAMEL-7978 Project: Camel Issue Type: Bug Components: camel-quartz2 Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0, 2.13.4 It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when two cluster camel-quartz endpoints are share different camel context name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7978) QuartzEndpoint should share the same camel context name when it working in cluster mode
[ https://issues.apache.org/jira/browse/CAMEL-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7978: Description: It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when two cluster camel-quartz endpoints are share different camel context name. We can add an option in the QuartzEndpoint to use CamelContext Name instead of management name. was: It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when two cluster camel-quartz endpoints are share different camel context name. QuartzEndpoint should share the same camel context name when it working in cluster mode --- Key: CAMEL-7978 URL: https://issues.apache.org/jira/browse/CAMEL-7978 Project: Camel Issue Type: Bug Components: camel-quartz2 Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0, 2.13.4 It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when two cluster camel-quartz endpoints are share different camel context name. We can add an option in the QuartzEndpoint to use CamelContext Name instead of management name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7978) QuartzEndpoint should share the same camel context name when it working in cluster mode
[ https://issues.apache.org/jira/browse/CAMEL-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7978: Description: It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when camel-quartz endpoints is share different camel context name. We can add an option in the QuartzEndpoint to use CamelContext Name instead of management name. was: It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when two cluster camel-quartz endpoints are share different camel context name. We can add an option in the QuartzEndpoint to use CamelContext Name instead of management name. QuartzEndpoint should share the same camel context name when it working in cluster mode --- Key: CAMEL-7978 URL: https://issues.apache.org/jira/browse/CAMEL-7978 Project: Camel Issue Type: Bug Components: camel-quartz2 Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0, 2.13.4 It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when camel-quartz endpoints is share different camel context name. We can add an option in the QuartzEndpoint to use CamelContext Name instead of management name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7978) QuartzEndpoint should share the same camel context name when it working in cluster mode
[ https://issues.apache.org/jira/browse/CAMEL-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7978: Fix Version/s: (was: 2.13.4) (was: 2.14.1) QuartzEndpoint should share the same camel context name when it working in cluster mode --- Key: CAMEL-7978 URL: https://issues.apache.org/jira/browse/CAMEL-7978 Project: Camel Issue Type: Bug Components: camel-quartz2 Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.15.0 It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when camel-quartz endpoints is share different camel context name. We can add an option in the QuartzEndpoint to use CamelContext Name instead of management name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7978) QuartzEndpoint should share the same camel context name when it working in cluster mode
[ https://issues.apache.org/jira/browse/CAMEL-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7978: Component/s: camel-quartz QuartzEndpoint should share the same camel context name when it working in cluster mode --- Key: CAMEL-7978 URL: https://issues.apache.org/jira/browse/CAMEL-7978 Project: Camel Issue Type: Bug Components: camel-quartz, camel-quartz2 Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.15.0 It could cause [some trouble|http://camel.465427.n5.nabble.com/Quartz-job-data-deletion-in-clustered-quartz2-tp5757508.html] when camel-quartz endpoints is share different camel context name. We can add an option in the QuartzEndpoint to use CamelContext Name instead of management name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8066) Add swagger ui to the camel swagger rest example
[ https://issues.apache.org/jira/browse/CAMEL-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Moulliard reassigned CAMEL-8066: Assignee: Charles Moulliard Add swagger ui to the camel swagger rest example Key: CAMEL-8066 URL: https://issues.apache.org/jira/browse/CAMEL-8066 Project: Camel Issue Type: Improvement Components: examples Affects Versions: 2.14.0 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.15.0 The example camel-example-servlet-rest-tomcat uses the camel swagger component to register the swagger servlet able to discover and generates json files for the REST service. The goal of this improvement is to add the swagger-ui resources (html, css, js, ...) to allow the user to discover the operations of the REST services and play with them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8066) Add swagger ui to the camel swagger rest example
Charles Moulliard created CAMEL-8066: Summary: Add swagger ui to the camel swagger rest example Key: CAMEL-8066 URL: https://issues.apache.org/jira/browse/CAMEL-8066 Project: Camel Issue Type: Improvement Components: examples Affects Versions: 2.14.0 Reporter: Charles Moulliard Fix For: 2.15.0 The example camel-example-servlet-rest-tomcat uses the camel swagger component to register the swagger servlet able to discover and generates json files for the REST service. The goal of this improvement is to add the swagger-ui resources (html, css, js, ...) to allow the user to discover the operations of the REST services and play with them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8066) Add swagger ui to the camel swagger rest example
[ https://issues.apache.org/jira/browse/CAMEL-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Moulliard resolved CAMEL-8066. -- Resolution: Fixed Add swagger ui to the camel swagger rest example Key: CAMEL-8066 URL: https://issues.apache.org/jira/browse/CAMEL-8066 Project: Camel Issue Type: Improvement Components: examples Affects Versions: 2.14.0 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.15.0 The example camel-example-servlet-rest-tomcat uses the camel swagger component to register the swagger servlet able to discover and generates json files for the REST service. The goal of this improvement is to add the swagger-ui resources (html, css, js, ...) to allow the user to discover the operations of the REST services and play with them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8067) Allow 'file' to use attachments content instead of body
Christoph Läubrich created CAMEL-8067: - Summary: Allow 'file' to use attachments content instead of body Key: CAMEL-8067 URL: https://issues.apache.org/jira/browse/CAMEL-8067 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Christoph Läubrich It would be nice if the file component would be able to save attachments to files (e.g. from the mail component). Currently I invoke a script that first fetch the attachment, get the input stream and then set it to the body. It would be nice if the file-component can do this directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
Christoph Läubrich created CAMEL-8068: - Summary: SplitAttachmentsExpression should set ID of splited attachment Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8069) Provide xml component to add attachments
Christoph Läubrich created CAMEL-8069: - Summary: Provide xml component to add attachments Key: CAMEL-8069 URL: https://issues.apache.org/jira/browse/CAMEL-8069 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Christoph Läubrich Currently you can only add attachments from java or scripting code. It would be nice to have something like addAttachment (like addHeader) for the XML, so you can define (and add) attachments by: - supply name + file by header values (-FileDataSource) - supply URL by header values (-URLDataSource) - use the body of the input message (Inputstream, byte[]) This would allow for easier and uniform handling of attachments e.g. in the mail component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8069) Provide xml component to add attachments
[ https://issues.apache.org/jira/browse/CAMEL-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8069. Resolution: Won't Fix Provide xml component to add attachments Key: CAMEL-8069 URL: https://issues.apache.org/jira/browse/CAMEL-8069 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Christoph Läubrich Currently you can only add attachments from java or scripting code. It would be nice to have something like addAttachment (like addHeader) for the XML, so you can define (and add) attachments by: - supply name + file by header values (-FileDataSource) - supply URL by header values (-URLDataSource) - use the body of the input message (Inputstream, byte[]) This would allow for easier and uniform handling of attachments e.g. in the mail component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8067) Allow 'file' to use attachments content instead of body
[ https://issues.apache.org/jira/browse/CAMEL-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8067. Resolution: Won't Fix Allow 'file' to use attachments content instead of body --- Key: CAMEL-8067 URL: https://issues.apache.org/jira/browse/CAMEL-8067 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Christoph Läubrich It would be nice if the file component would be able to save attachments to files (e.g. from the mail component). Currently I invoke a script that first fetch the attachment, get the input stream and then set it to the body. It would be nice if the file-component can do this directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8069) Provide xml component to add attachments
[ https://issues.apache.org/jira/browse/CAMEL-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220761#comment-14220761 ] Claus Ibsen commented on CAMEL-8069: Attachments is rarely used and only supported by a few components. We do not want to add more into the DSL that will never/very rarely be used. Provide xml component to add attachments Key: CAMEL-8069 URL: https://issues.apache.org/jira/browse/CAMEL-8069 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Christoph Läubrich Currently you can only add attachments from java or scripting code. It would be nice to have something like addAttachment (like addHeader) for the XML, so you can define (and add) attachments by: - supply name + file by header values (-FileDataSource) - supply URL by header values (-URLDataSource) - use the body of the input message (Inputstream, byte[]) This would allow for easier and uniform handling of attachments e.g. in the mail component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8068: --- Estimated Complexity: Novice (was: Unknown) SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Priority: Minor The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220764#comment-14220764 ] Claus Ibsen commented on CAMEL-8068: Good idea, a PR is welcome http://camel.apache.org/contributing.html SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Priority: Minor The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8068: --- Priority: Minor (was: Major) SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Priority: Minor The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8069) Provide xml component to add attachments
[ https://issues.apache.org/jira/browse/CAMEL-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220783#comment-14220783 ] Christoph Läubrich commented on CAMEL-8069: --- well it might be rarely used because its atm alittle bit hard to use. IMO it would also be okay to have a processor that could be used as a bean instead of a special tag or something. Beside thus, doing this via script languages is not very compfortable. Having such a thing prebuild into camel would make things like, reading from a file or report generator and send this to one or more mail accounts attaching it to mail (e.g. billing to customer) much more easy and understandable instead of forching one to write custom code. And such a use case is I think more likeley than rare... Provide xml component to add attachments Key: CAMEL-8069 URL: https://issues.apache.org/jira/browse/CAMEL-8069 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Christoph Läubrich Currently you can only add attachments from java or scripting code. It would be nice to have something like addAttachment (like addHeader) for the XML, so you can define (and add) attachments by: - supply name + file by header values (-FileDataSource) - supply URL by header values (-URLDataSource) - use the body of the input message (Inputstream, byte[]) This would allow for easier and uniform handling of attachments e.g. in the mail component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8067) Allow 'file' to use attachments content instead of body
[ https://issues.apache.org/jira/browse/CAMEL-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220788#comment-14220788 ] Christoph Läubrich commented on CAMEL-8067: --- Why is this marked as resolved? Currently it is not possible to write data from an attachment to a file (e.g. reading from a mailbox storing all attachments to an output directory for further processing) without having some extra code. So I think this is a valid enhancement-request. Allow 'file' to use attachments content instead of body --- Key: CAMEL-8067 URL: https://issues.apache.org/jira/browse/CAMEL-8067 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Christoph Läubrich It would be nice if the file component would be able to save attachments to files (e.g. from the mail component). Currently I invoke a script that first fetch the attachment, get the input stream and then set it to the body. It would be nice if the file-component can do this directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8070) Supporting byte[] messages in camel-websocket
Akitoshi Yoshida created CAMEL-8070: --- Summary: Supporting byte[] messages in camel-websocket Key: CAMEL-8070 URL: https://issues.apache.org/jira/browse/CAMEL-8070 Project: Camel Issue Type: Improvement Components: camel-websocket Affects Versions: 2.14.0 Reporter: Akitoshi Yoshida Assignee: Akitoshi Yoshida Fix For: 2.14.1 camel-websocket currently does not handle byte[] messages. http://camel.465427.n5.nabble.com/AHS-WS-problem-td5759334.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Läubrich updated CAMEL-8068: -- Attachment: CAMEL-8068.patch Set Header CamelSplitAttachmentId with the attachment ID on the copy message SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Priority: Minor Attachments: CAMEL-8068.patch The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Läubrich updated CAMEL-8068: -- Labels: patch (was: ) SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Priority: Minor Labels: patch Attachments: CAMEL-8068.patch The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220882#comment-14220882 ] Christoph Läubrich edited comment on CAMEL-8068 at 11/21/14 1:13 PM: - Attached a patch that set header CamelSplitAttachmentId with the attachment ID on the copy message. was (Author: laeubi): Set Header CamelSplitAttachmentId with the attachment ID on the copy message SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Priority: Minor Labels: patch Attachments: CAMEL-8068.patch The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
Michael Feichtegger created CAMEL-8071:
--
Summary: DefaultPackageScanClassResolver unable to handle
JAR-Files located at WEB-INF/lib
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.3, 2.13.2
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
Fix For: 2.13.4
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that DefaultPackageScanClassResolver is
trying to open an InputStream like this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course to not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
[
https://issues.apache.org/jira/browse/CAMEL-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Feichtegger updated CAMEL-8071:
---
Description:
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
was:
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that DefaultPackageScanClassResolver is
trying to open an InputStream like this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course to not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well.
DefaultPackageScanClassResolver unable to handle JAR-Files located at
WEB-INF/lib
-
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.2, 2.13.3
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
Fix For: 2.13.4
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like
this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
[
https://issues.apache.org/jira/browse/CAMEL-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220923#comment-14220923
]
Claus Ibsen commented on CAMEL-8071:
You need a special camel-jboss resolver, see
http://camel.apache.org/camel-jboss.html
DefaultPackageScanClassResolver unable to handle JAR-Files located at
WEB-INF/lib
-
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.2, 2.13.3
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
Fix For: 2.13.4
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like
this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
[
https://issues.apache.org/jira/browse/CAMEL-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220933#comment-14220933
]
Michael Feichtegger commented on CAMEL-8071:
Since we are using 2.13.3 we've thought that it camel-jboss is obsolete.
From Camel 2.8 onwards there is no longer the need for using this camel-jboss
component as Camel is now capable of loading type converters without package
scanning. This requires though that all 3rd party components with type
converter must define the name of the converter classes as FQN in the
META-INF/org/apache/camel/TypeConverter file. See more details at Type
Converter.
One exception is if you are using Bindy component as it still needs this JBoss
resolver.
DefaultPackageScanClassResolver unable to handle JAR-Files located at
WEB-INF/lib
-
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.2, 2.13.3
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
Fix For: 2.13.4
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like
this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
[
https://issues.apache.org/jira/browse/CAMEL-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8071:
---
Issue Type: Wish (was: Bug)
DefaultPackageScanClassResolver unable to handle JAR-Files located at
WEB-INF/lib
-
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Wish
Components: camel-core
Affects Versions: 2.13.2, 2.13.3
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like
this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
[
https://issues.apache.org/jira/browse/CAMEL-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8071:
---
Fix Version/s: (was: 2.13.4)
DefaultPackageScanClassResolver unable to handle JAR-Files located at
WEB-INF/lib
-
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.2, 2.13.3
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like
this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
[
https://issues.apache.org/jira/browse/CAMEL-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220950#comment-14220950
]
Claus Ibsen commented on CAMEL-8071:
Yes when using bindy its needed.
Though there is a wildfly-camel project so maybe in the future JBoss EAP can
ship this resolver out of the box?
https://github.com/wildflyext/wildfly-camel
DefaultPackageScanClassResolver unable to handle JAR-Files located at
WEB-INF/lib
-
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Wish
Components: camel-core
Affects Versions: 2.13.2, 2.13.3
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
Priority: Minor
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like
this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8071) DefaultPackageScanClassResolver unable to handle JAR-Files located at WEB-INF/lib
[
https://issues.apache.org/jira/browse/CAMEL-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220956#comment-14220956
]
Claus Ibsen commented on CAMEL-8071:
On your system is there a file path for this
{code}
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/
{code}
And in that lib directory there is the JAR files (but they are not expanded) ?
If so the trick would be to know this from the url above which is just a
string. And then add some logic that tries to list the dir for .jar files and
then use a jar url loader to scan inside those JARs. All extra work needed to
do so, which with some hard-work may be possible to add in camel-core.
You can welcome to experiment with this as you got an EAP app server on your
system and use bindy.
DefaultPackageScanClassResolver unable to handle JAR-Files located at
WEB-INF/lib
-
Key: CAMEL-8071
URL: https://issues.apache.org/jira/browse/CAMEL-8071
Project: Camel
Issue Type: Wish
Components: camel-core
Affects Versions: 2.13.2, 2.13.3
Environment: Ubuntu 14.04 (64bit)
JBoss EAP 6.3
Oracle JDK 1.6.0_45
Reporter: Michael Feichtegger
Priority: Minor
We are creating a WebApplication which also provides camel endpoints.
One of the endpoints triggers a bindy action to read records from a
fixed-length-record input file. For this purpose we are using camel bindy.
I this conjuction we discovered that there is an issue when trying to locate
those classes which are annotated with {{@FixedLengthRecord}} since the are
located in a JAR-File.
The project structure looks like this:
- project-ear
-- project-war
--- WEB-INF/lib/project-jar
If we locate the classes directly at WEB-INF/classes/my/package camel is able
to discover the annotated classes.
After some debugging we have found out, that
{{DefaultPackageScanClassResolver}} is trying to open an InputStream like
this:
/opt/jboss-eap/current/standalone/deployments/bindy-ear.ear/bindy-ws-0.0.1-SNAPSHOT.war/WEB-INF/lib/bindy-core-0.0.1-SNAPSHOT.jar/my/package/
which of of course does not exist.
If you remove in those cases /my/package from the File the resolver works
perfectly well since {{loadImplementationsInJar}} will be called correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8068. Resolution: Fixed Fix Version/s: 2.15.0 2.14.1 Assignee: Claus Ibsen Thanks for the patch. We do like when there is an unit test with code changes so we can verify this. SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Assignee: Claus Ibsen Priority: Minor Labels: patch Fix For: 2.14.1, 2.15.0 Attachments: CAMEL-8068.patch The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8067) Allow 'file' to use attachments content instead of body
[ https://issues.apache.org/jira/browse/CAMEL-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220991#comment-14220991 ] Claus Ibsen commented on CAMEL-8067: You should use the mail attachments splitter so its from mail split mail attachments to file What can be enhanced is the mail attachments splitter to let it store the attachment as the message body and set the name as a Exchange.FILE_NAME. So I suggest you can take a look at extending this code to introduce an option to configure enable this. Allow 'file' to use attachments content instead of body --- Key: CAMEL-8067 URL: https://issues.apache.org/jira/browse/CAMEL-8067 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Christoph Läubrich It would be nice if the file component would be able to save attachments to files (e.g. from the mail component). Currently I invoke a script that first fetch the attachment, get the input stream and then set it to the body. It would be nice if the file-component can do this directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8066) Add swagger ui to the camel swagger rest example
[ https://issues.apache.org/jira/browse/CAMEL-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220994#comment-14220994 ] Claus Ibsen commented on CAMEL-8066: Charles, is all that javascript code you added, are you sure they are in compliance with ASF licesning? I am not really fond of copying a bunch of javascript code we do not maintain into an example. Instead people should run swagger ui external, and connect to the example as that is what it can do. I am in fact favor of removing the code you added and point people into that other direction. Though anyone have any other thoughts or comments? Add swagger ui to the camel swagger rest example Key: CAMEL-8066 URL: https://issues.apache.org/jira/browse/CAMEL-8066 Project: Camel Issue Type: Improvement Components: examples Affects Versions: 2.14.0 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.15.0 The example camel-example-servlet-rest-tomcat uses the camel swagger component to register the swagger servlet able to discover and generates json files for the REST service. The goal of this improvement is to add the swagger-ui resources (html, css, js, ...) to allow the user to discover the operations of the REST services and play with them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8072) Netty Http Server should close the channel once it return an error message
Willem Jiang created CAMEL-8072: --- Summary: Netty Http Server should close the channel once it return an error message Key: CAMEL-8072 URL: https://issues.apache.org/jira/browse/CAMEL-8072 Project: Camel Issue Type: Improvement Components: camel-netty-http, camel-netty4-http Affects Versions: 2.14.0, 2.13.3 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0 It's a common practice that http server close the connection once it send the error message to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8073) Camel may clear attachments during routing
Claus Ibsen created CAMEL-8073: -- Summary: Camel may clear attachments during routing Key: CAMEL-8073 URL: https://issues.apache.org/jira/browse/CAMEL-8073 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.14.0, 2.13.3 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.1, 2.15.0, 2.13.4 See nabble http://camel.465427.n5.nabble.com/Camel-cleans-attachments-if-error-is-thrown-during-routing-tp5759410.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8073) Camel may clear attachments during routing
[ https://issues.apache.org/jira/browse/CAMEL-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8073. Resolution: Fixed Camel may clear attachments during routing -- Key: CAMEL-8073 URL: https://issues.apache.org/jira/browse/CAMEL-8073 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.13.3, 2.14.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.1, 2.15.0, 2.13.4 See nabble http://camel.465427.n5.nabble.com/Camel-cleans-attachments-if-error-is-thrown-during-routing-tp5759410.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8068) SplitAttachmentsExpression should set ID of splited attachment
[ https://issues.apache.org/jira/browse/CAMEL-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221073#comment-14221073 ] Christoph Läubrich commented on CAMEL-8068: --- Currently I'm not able to build the test, they complain about missing documentation... Also compilation fails on my pc becuase MailSorter uses Java 7 style and the compile level seems java 1.6 ... So I'm currently try to sort out how to build camel at all from the git checkout :-( SplitAttachmentsExpression should set ID of splited attachment -- Key: CAMEL-8068 URL: https://issues.apache.org/jira/browse/CAMEL-8068 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 2.14.0 Reporter: Christoph Läubrich Assignee: Claus Ibsen Priority: Minor Labels: patch Fix For: 2.14.1, 2.15.0 Attachments: CAMEL-8068.patch The https://svn.apache.org/repos/asf/camel/trunk/components/camel-mail/src/main/java/org/apache/camel/component/mail/SplitAttachmentsExpression.java currently splits the attachments by each ID but do not provide the ID as an additional header. It would be usefull for the processing code to know the ID so they simply get them e.g. by getAttachment(header[CamelSplitAttachmentName]) instead of looking in the map for names etc. or iterate over it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8067) Allow 'file' to use attachments content instead of body
[ https://issues.apache.org/jira/browse/CAMEL-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221081#comment-14221081 ] Christoph Läubrich commented on CAMEL-8067: --- Yes thats what I try, the problem is that as you said the splitter simply splits the attachments, so the file task fails (since it tries to write the body = Mail message). Maybe the MailSplitter is a better place to support this. Allow 'file' to use attachments content instead of body --- Key: CAMEL-8067 URL: https://issues.apache.org/jira/browse/CAMEL-8067 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Christoph Läubrich It would be nice if the file component would be able to save attachments to files (e.g. from the mail component). Currently I invoke a script that first fetch the attachment, get the input stream and then set it to the body. It would be nice if the file-component can do this directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8067) Allow 'file' to use attachments content instead of body
[ https://issues.apache.org/jira/browse/CAMEL-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221081#comment-14221081 ] Christoph Läubrich edited comment on CAMEL-8067 at 11/21/14 4:14 PM: - Yes thats what I try, the problem is that as you said the splitter simply splits the attachments, so the file task fails (since it tries to write the body = Mail message). Maybe the MailSplitter is a better place to support this. But I still think it is worth to make the file task support attachments, so you are able to read/write attachments from files. was (Author: laeubi): Yes thats what I try, the problem is that as you said the splitter simply splits the attachments, so the file task fails (since it tries to write the body = Mail message). Maybe the MailSplitter is a better place to support this. Allow 'file' to use attachments content instead of body --- Key: CAMEL-8067 URL: https://issues.apache.org/jira/browse/CAMEL-8067 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Christoph Läubrich It would be nice if the file component would be able to save attachments to files (e.g. from the mail component). Currently I invoke a script that first fetch the attachment, get the input stream and then set it to the body. It would be nice if the file-component can do this directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8067) Allow 'file' to use attachments content instead of body
[ https://issues.apache.org/jira/browse/CAMEL-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221096#comment-14221096 ] Christoph Läubrich commented on CAMEL-8067: --- Maybe it would be an option to create a new camel-attachment component for all tasks around adding/splitting/moving attachment, this could also be an option for CAMEL-8069 wdyt? Allow 'file' to use attachments content instead of body --- Key: CAMEL-8067 URL: https://issues.apache.org/jira/browse/CAMEL-8067 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Christoph Läubrich It would be nice if the file component would be able to save attachments to files (e.g. from the mail component). Currently I invoke a script that first fetch the attachment, get the input stream and then set it to the body. It would be nice if the file-component can do this directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8066) Add swagger ui to the camel swagger rest example
[ https://issues.apache.org/jira/browse/CAMEL-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221295#comment-14221295 ] Preben Asmussen commented on CAMEL-8066: Or maybe use swagger-ui as a web-jar http://mvnrepository.com/artifact/org.webjars/swagger-ui/2.0.12. that is Apache Licensed https://github.com/swagger-api/swagger-ui/blob/master/LICENSE. But still the js etc in the jar has a mix. of different licenses. Add swagger ui to the camel swagger rest example Key: CAMEL-8066 URL: https://issues.apache.org/jira/browse/CAMEL-8066 Project: Camel Issue Type: Improvement Components: examples Affects Versions: 2.14.0 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.15.0 The example camel-example-servlet-rest-tomcat uses the camel swagger component to register the swagger servlet able to discover and generates json files for the REST service. The goal of this improvement is to add the swagger-ui resources (html, css, js, ...) to allow the user to discover the operations of the REST services and play with them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
