[jira] [Resolved] (CAMEL-7861) Camel-Spring depends on Spring <4
[ https://issues.apache.org/jira/browse/CAMEL-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7861. Resolution: Not a Problem Yep spring-dm dont work with spring 4. The karaf team would need to fix it. > Camel-Spring depends on Spring <4 > - > > Key: CAMEL-7861 > URL: https://issues.apache.org/jira/browse/CAMEL-7861 > Project: Camel > Issue Type: Bug > Components: camel-spring, karaf, osgi >Affects Versions: 2.14.0 > Environment: Karaf 2.4.0 > Spring 4.0.5 >Reporter: Ray Rishty > > When I attempt to start camel-spring in Karaf 2.4.0, I see the below error > stating that I need a version of spring between 3.2 and 4: > karaf@root> osgi:start camel-spring > You are about to access system bundle 81. Do you wish to continue (yes/no): > yes > Error executing command: Error starting bundles: > Unable to start bundle 81: Unresolved constraint in bundle > org.apache.camel.camel-spring [81]: Unable to resolve 81.0: missing > requirement [81.0] osgi.wiring.package; > (&(osgi.wiring.package=org.springframework.beans)(version>=3.2.0)(!(version>=4.0.0))) > Checking out the import-package statement via osgi:headers, I see that the > Spring dependency is explicitly less than 4. > org.springframework.beans;version="[3.2,4)", > org.springframework.beans.factory;version="[3.2,4)", > org.springframework.beans.factory.config;version="[3.2,4)", > org.springframework.beans.factory.parsing;version="[3.2,4)", > org.springframework.beans.factory.support;version="[3.2,4)", > org.springframework.beans.factory.xml;version="[3.2,4)", > org.springframework.context;version="[3.2,4)", > org.springframework.context.event;version="[3.2,4)", > org.springframework.context.expression;version="[3.2,4)", > org.springframework.context.support;version="[3.2,4)", > org.springframework.core;version="[3.2,4)", > org.springframework.core.io;version="[3.2,4)", > org.springframework.expression;version="[3.2,4)", > org.springframework.expression.common;version="[3.2,4)", > org.springframework.expression.spel.standard;version="[3.2,4)", > org.springframework.expression.spel.support;version="[3.2,4)", > org.springframework.jmx.export.annotation;version="[3.2,4)", > org.springframework.jmx.export.assembler;version="[3.2,4)", > org.springframework.jmx.export.metadata;version="[3.2,4)", > > org.springframework.osgi.context;resolution:=optional;version="[1.2,2)", > org.springframework.remoting.support;version="[3.2,4)", > org.springframework.scheduling;version="[3.2,4)", > org.springframework.scheduling.concurrent;version="[3.2,4)", > org.springframework.scheduling.support;version="[3.2,4)", > org.springframework.transaction;version="[3.2,4)", > org.springframework.transaction.support;version="[3.2,4)", > org.springframework.util;version="[3.2,4)", -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-7860) Add sendReply functionality in RabbitMQConsumer
[
https://issues.apache.org/jira/browse/CAMEL-7860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-7860:
---
Assignee: Willem Jiang
> Add sendReply functionality in RabbitMQConsumer
> ---
>
> Key: CAMEL-7860
> URL: https://issues.apache.org/jira/browse/CAMEL-7860
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
>Affects Versions: 2.13.2, 2.14.0
>Reporter: Raymond Cuenen
>Assignee: Willem Jiang
>Priority: Minor
> Labels: improvement, rpc
> Fix For: 2.14.1
>
> Attachments: consumer.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> To provide the RPC functionality with RabbitMQ as described
> [here|http://www.rabbitmq.com/tutorials/tutorial-six-java.html] the
> {{ExchangePattern}} should be changed to {{InOut}} when the {{replyTo}} is
> present in the AMQP properties for the {{RabbitMQConsumer}}.
> After processing the {{Exchange}} the reply message can than be retrieved and
> published to the reply queue.
> For JMS is a similar construction already implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7861) Camel-Spring depends on Spring <4
[ https://issues.apache.org/jira/browse/CAMEL-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147268#comment-14147268 ] Willem Jiang commented on CAMEL-7861: - spring-dm and some other spring-xxx components do not support spring 4.x so import-range must be 3.x only until a solution in karaf exists. > Camel-Spring depends on Spring <4 > - > > Key: CAMEL-7861 > URL: https://issues.apache.org/jira/browse/CAMEL-7861 > Project: Camel > Issue Type: Bug > Components: camel-spring, karaf, osgi >Affects Versions: 2.14.0 > Environment: Karaf 2.4.0 > Spring 4.0.5 >Reporter: Ray Rishty > > When I attempt to start camel-spring in Karaf 2.4.0, I see the below error > stating that I need a version of spring between 3.2 and 4: > karaf@root> osgi:start camel-spring > You are about to access system bundle 81. Do you wish to continue (yes/no): > yes > Error executing command: Error starting bundles: > Unable to start bundle 81: Unresolved constraint in bundle > org.apache.camel.camel-spring [81]: Unable to resolve 81.0: missing > requirement [81.0] osgi.wiring.package; > (&(osgi.wiring.package=org.springframework.beans)(version>=3.2.0)(!(version>=4.0.0))) > Checking out the import-package statement via osgi:headers, I see that the > Spring dependency is explicitly less than 4. > org.springframework.beans;version="[3.2,4)", > org.springframework.beans.factory;version="[3.2,4)", > org.springframework.beans.factory.config;version="[3.2,4)", > org.springframework.beans.factory.parsing;version="[3.2,4)", > org.springframework.beans.factory.support;version="[3.2,4)", > org.springframework.beans.factory.xml;version="[3.2,4)", > org.springframework.context;version="[3.2,4)", > org.springframework.context.event;version="[3.2,4)", > org.springframework.context.expression;version="[3.2,4)", > org.springframework.context.support;version="[3.2,4)", > org.springframework.core;version="[3.2,4)", > org.springframework.core.io;version="[3.2,4)", > org.springframework.expression;version="[3.2,4)", > org.springframework.expression.common;version="[3.2,4)", > org.springframework.expression.spel.standard;version="[3.2,4)", > org.springframework.expression.spel.support;version="[3.2,4)", > org.springframework.jmx.export.annotation;version="[3.2,4)", > org.springframework.jmx.export.assembler;version="[3.2,4)", > org.springframework.jmx.export.metadata;version="[3.2,4)", > > org.springframework.osgi.context;resolution:=optional;version="[1.2,2)", > org.springframework.remoting.support;version="[3.2,4)", > org.springframework.scheduling;version="[3.2,4)", > org.springframework.scheduling.concurrent;version="[3.2,4)", > org.springframework.scheduling.support;version="[3.2,4)", > org.springframework.transaction;version="[3.2,4)", > org.springframework.transaction.support;version="[3.2,4)", > org.springframework.util;version="[3.2,4)", -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7861) Camel-Spring depends on Spring <4
Ray Rishty created CAMEL-7861: - Summary: Camel-Spring depends on Spring <4 Key: CAMEL-7861 URL: https://issues.apache.org/jira/browse/CAMEL-7861 Project: Camel Issue Type: Bug Components: camel-spring, karaf, osgi Affects Versions: 2.14.0 Environment: Karaf 2.4.0 Spring 4.0.5 Reporter: Ray Rishty When I attempt to start camel-spring in Karaf 2.4.0, I see the below error stating that I need a version of spring between 3.2 and 4: karaf@root> osgi:start camel-spring You are about to access system bundle 81. Do you wish to continue (yes/no): yes Error executing command: Error starting bundles: Unable to start bundle 81: Unresolved constraint in bundle org.apache.camel.camel-spring [81]: Unable to resolve 81.0: missing requirement [81.0] osgi.wiring.package; (&(osgi.wiring.package=org.springframework.beans)(version>=3.2.0)(!(version>=4.0.0))) Checking out the import-package statement via osgi:headers, I see that the Spring dependency is explicitly less than 4. org.springframework.beans;version="[3.2,4)", org.springframework.beans.factory;version="[3.2,4)", org.springframework.beans.factory.config;version="[3.2,4)", org.springframework.beans.factory.parsing;version="[3.2,4)", org.springframework.beans.factory.support;version="[3.2,4)", org.springframework.beans.factory.xml;version="[3.2,4)", org.springframework.context;version="[3.2,4)", org.springframework.context.event;version="[3.2,4)", org.springframework.context.expression;version="[3.2,4)", org.springframework.context.support;version="[3.2,4)", org.springframework.core;version="[3.2,4)", org.springframework.core.io;version="[3.2,4)", org.springframework.expression;version="[3.2,4)", org.springframework.expression.common;version="[3.2,4)", org.springframework.expression.spel.standard;version="[3.2,4)", org.springframework.expression.spel.support;version="[3.2,4)", org.springframework.jmx.export.annotation;version="[3.2,4)", org.springframework.jmx.export.assembler;version="[3.2,4)", org.springframework.jmx.export.metadata;version="[3.2,4)", org.springframework.osgi.context;resolution:=optional;version="[1.2,2)", org.springframework.remoting.support;version="[3.2,4)", org.springframework.scheduling;version="[3.2,4)", org.springframework.scheduling.concurrent;version="[3.2,4)", org.springframework.scheduling.support;version="[3.2,4)", org.springframework.transaction;version="[3.2,4)", org.springframework.transaction.support;version="[3.2,4)", org.springframework.util;version="[3.2,4)", -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7860) Add sendReply functionality in RabbitMQConsumer
Raymond Cuenen created CAMEL-7860:
-
Summary: Add sendReply functionality in RabbitMQConsumer
Key: CAMEL-7860
URL: https://issues.apache.org/jira/browse/CAMEL-7860
Project: Camel
Issue Type: Improvement
Components: camel-rabbitmq
Affects Versions: 2.14.0, 2.13.2
Reporter: Raymond Cuenen
Priority: Minor
Fix For: 2.14.1
To provide the RPC functionality with RabbitMQ as described
[here|http://www.rabbitmq.com/tutorials/tutorial-six-java.html] the
{{ExchangePattern}} should be changed to {{InOut}} when the {{replyTo}} is
present in the AMQP properties for the {{RabbitMQConsumer}}.
After processing the {{Exchange}} the reply message can than be retrieved and
published to the reply queue.
For JMS is a similar construction already implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-7860) Add sendReply functionality in RabbitMQConsumer
[
https://issues.apache.org/jira/browse/CAMEL-7860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Cuenen updated CAMEL-7860:
--
Attachment: consumer.patch
> Add sendReply functionality in RabbitMQConsumer
> ---
>
> Key: CAMEL-7860
> URL: https://issues.apache.org/jira/browse/CAMEL-7860
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
>Affects Versions: 2.13.2, 2.14.0
>Reporter: Raymond Cuenen
>Priority: Minor
> Labels: improvement, rpc
> Fix For: 2.14.1
>
> Attachments: consumer.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> To provide the RPC functionality with RabbitMQ as described
> [here|http://www.rabbitmq.com/tutorials/tutorial-six-java.html] the
> {{ExchangePattern}} should be changed to {{InOut}} when the {{replyTo}} is
> present in the AMQP properties for the {{RabbitMQConsumer}}.
> After processing the {{Exchange}} the reply message can than be retrieved and
> published to the reply queue.
> For JMS is a similar construction already implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146258#comment-14146258 ] ASF GitHub Bot commented on CAMEL-7835: --- Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/276 > camel-test-spring doesn't support Spring 4.1.0.RELEASE > -- > > Key: CAMEL-7835 > URL: https://issues.apache.org/jira/browse/CAMEL-7835 > Project: Camel > Issue Type: Task > Components: camel-test >Affects Versions: 2.14.0 >Reporter: Henrik >Assignee: Claus Ibsen > Labels: deprecation, junit, spring, test > Fix For: 2.15.0 > > > CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) > constructor, and the > TestContextManager.getDefaultTestExecutionListenerClasses() method. > Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146251#comment-14146251 ] ASF GitHub Bot commented on CAMEL-7835: --- GitHub user wuwen5 opened a pull request: https://github.com/apache/camel/pull/276 CAMEL-7835:Camel listener with the Ordered You can merge this pull request into a Git repository by running: $ git pull https://github.com/wuwen5/camel CAMEL-7835-Ordered Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/276.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #276 commit 8053a274977d4a710ace777df355cdcfd84d62a4 Author: wuwen Date: 2014-09-24T12:08:01Z CAMEL-7835:Camel listener with the Ordered > camel-test-spring doesn't support Spring 4.1.0.RELEASE > -- > > Key: CAMEL-7835 > URL: https://issues.apache.org/jira/browse/CAMEL-7835 > Project: Camel > Issue Type: Task > Components: camel-test >Affects Versions: 2.14.0 >Reporter: Henrik >Assignee: Claus Ibsen > Labels: deprecation, junit, spring, test > Fix For: 2.15.0 > > > CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) > constructor, and the > TestContextManager.getDefaultTestExecutionListenerClasses() method. > Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146190#comment-14146190 ] ASF GitHub Bot commented on CAMEL-7835: --- Github user wuwen5 closed the pull request at: https://github.com/apache/camel/pull/273 > camel-test-spring doesn't support Spring 4.1.0.RELEASE > -- > > Key: CAMEL-7835 > URL: https://issues.apache.org/jira/browse/CAMEL-7835 > Project: Camel > Issue Type: Task > Components: camel-test >Affects Versions: 2.14.0 >Reporter: Henrik >Assignee: Claus Ibsen > Labels: deprecation, junit, spring, test > Fix For: 2.15.0 > > > CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) > constructor, and the > TestContextManager.getDefaultTestExecutionListenerClasses() method. > Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-7859) Language component - Add support for binary content
[ https://issues.apache.org/jira/browse/CAMEL-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7859. Resolution: Fixed There is a binary option now > Language component - Add support for binary content > --- > > Key: CAMEL-7859 > URL: https://issues.apache.org/jira/browse/CAMEL-7859 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.14.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.14.1, 2.15.0 > > > See nabble > http://camel.465427.n5.nabble.com/Corrupt-pdf-from-classpath-tp5756921.html > So you can read binary content from classpath using the constant language. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7858) Allow to disable Jaxb annotations in JacksonDataFormat
[
https://issues.apache.org/jira/browse/CAMEL-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146099#comment-14146099
]
Nicolás Amador commented on CAMEL-7858:
---
Thank you so much!
> Allow to disable Jaxb annotations in JacksonDataFormat
> --
>
> Key: CAMEL-7858
> URL: https://issues.apache.org/jira/browse/CAMEL-7858
> Project: Camel
> Issue Type: Improvement
> Components: camel-jackson
>Affects Versions: 2.14.0
>Reporter: Nicolás Amador
>Assignee: Willem Jiang
>Priority: Minor
> Fix For: 2.15.0
>
>
> The existing code of camel jackson dataformat does not support that we
> disable the JaxbAnnotationModule()
> {code}
> public JacksonDataFormat(Class unmarshalType, Class jsonView) {
> this.objectMapper = new ObjectMapper();
> this.unmarshalType = unmarshalType;
> this.jsonView = jsonView;
> // Enables JAXB processing
> JaxbAnnotationModule module = new JaxbAnnotationModule();
> this.objectMapper.registerModule(module);
> }
> {code}
> If we have an attribute like this:
> {code}
> @XmlAttribute(name = "has-children", required = true)
> private Boolean hasChildren;
> {code}
> In previous version (2.9.7 for instance):
> {code}
> XML: "has-children"
> Json: "hasChildren"
> {code}
> In the current one (2.14.0):
> {code}
> XML: "has-children"
> Json: "has-children"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7858) Allow to disable Jaxb annotations in JacksonDataFormat
[
https://issues.apache.org/jira/browse/CAMEL-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146096#comment-14146096
]
Willem Jiang commented on CAMEL-7858:
-
Hi Nicolás,
I just apply a patch into master branch.
You can override the default setting by apply the your ObjectMapper when create
the JacksonDataFormat.
Just like this
{code}
JacksonDataFormat formatPojo = new JacksonDataFormat(new ObjectMapper(),
TestJAXBPojo.class);
{code}
> Allow to disable Jaxb annotations in JacksonDataFormat
> --
>
> Key: CAMEL-7858
> URL: https://issues.apache.org/jira/browse/CAMEL-7858
> Project: Camel
> Issue Type: Improvement
> Components: camel-jackson
>Affects Versions: 2.14.0
>Reporter: Nicolás Amador
>Assignee: Willem Jiang
>Priority: Minor
> Fix For: 2.15.0
>
>
> The existing code of camel jackson dataformat does not support that we
> disable the JaxbAnnotationModule()
> {code}
> public JacksonDataFormat(Class unmarshalType, Class jsonView) {
> this.objectMapper = new ObjectMapper();
> this.unmarshalType = unmarshalType;
> this.jsonView = jsonView;
> // Enables JAXB processing
> JaxbAnnotationModule module = new JaxbAnnotationModule();
> this.objectMapper.registerModule(module);
> }
> {code}
> If we have an attribute like this:
> {code}
> @XmlAttribute(name = "has-children", required = true)
> private Boolean hasChildren;
> {code}
> In previous version (2.9.7 for instance):
> {code}
> XML: "has-children"
> Json: "hasChildren"
> {code}
> In the current one (2.14.0):
> {code}
> XML: "has-children"
> Json: "has-children"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-7858) Allow to disable Jaxb annotations in JacksonDataFormat
[
https://issues.apache.org/jira/browse/CAMEL-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-7858.
-
Resolution: Fixed
Fix Version/s: 2.15.0
Applied the patch into camel master branch.
> Allow to disable Jaxb annotations in JacksonDataFormat
> --
>
> Key: CAMEL-7858
> URL: https://issues.apache.org/jira/browse/CAMEL-7858
> Project: Camel
> Issue Type: Improvement
> Components: camel-jackson
>Affects Versions: 2.14.0
>Reporter: Nicolás Amador
>Assignee: Willem Jiang
>Priority: Minor
> Fix For: 2.15.0
>
>
> The existing code of camel jackson dataformat does not support that we
> disable the JaxbAnnotationModule()
> {code}
> public JacksonDataFormat(Class unmarshalType, Class jsonView) {
> this.objectMapper = new ObjectMapper();
> this.unmarshalType = unmarshalType;
> this.jsonView = jsonView;
> // Enables JAXB processing
> JaxbAnnotationModule module = new JaxbAnnotationModule();
> this.objectMapper.registerModule(module);
> }
> {code}
> If we have an attribute like this:
> {code}
> @XmlAttribute(name = "has-children", required = true)
> private Boolean hasChildren;
> {code}
> In previous version (2.9.7 for instance):
> {code}
> XML: "has-children"
> Json: "hasChildren"
> {code}
> In the current one (2.14.0):
> {code}
> XML: "has-children"
> Json: "has-children"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7766) Exception in split does not trigger onException in main route
[ https://issues.apache.org/jira/browse/CAMEL-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146090#comment-14146090 ] Benjamin BONNET commented on CAMEL-7766: Hi, I changed this issue title since exception thrown in the split does propagate to errorHandler but does not trigger onException that applies to main route. Regards. > Exception in split does not trigger onException in main route > - > > Key: CAMEL-7766 > URL: https://issues.apache.org/jira/browse/CAMEL-7766 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 > Environment: JDK7 / W7 >Reporter: Benjamin BONNET > > Exception thrown in a sequential split does not trigger onException applying > to main route. > That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7766) Exception in split does not trigger onException in main route
[ https://issues.apache.org/jira/browse/CAMEL-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin BONNET updated CAMEL-7766: --- Description: Exception thrown in a sequential split does not trigger onException applying to main route. That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) was: Exception thrown in a sequential split is not propagated to main route. That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) > Exception in split does not trigger onException in main route > - > > Key: CAMEL-7766 > URL: https://issues.apache.org/jira/browse/CAMEL-7766 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 > Environment: JDK7 / W7 >Reporter: Benjamin BONNET > > Exception thrown in a sequential split does not trigger onException applying > to main route. > That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7766) Exception in split does not trigger onException in main route
[ https://issues.apache.org/jira/browse/CAMEL-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin BONNET updated CAMEL-7766: --- Summary: Exception in split does not trigger onException in main route (was: Exception in split is not propagated) > Exception in split does not trigger onException in main route > - > > Key: CAMEL-7766 > URL: https://issues.apache.org/jira/browse/CAMEL-7766 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 > Environment: JDK7 / W7 >Reporter: Benjamin BONNET > > Exception thrown in a sequential split is not propagated to main route. > That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7859) Language component - Add support for binary content
Claus Ibsen created CAMEL-7859: -- Summary: Language component - Add support for binary content Key: CAMEL-7859 URL: https://issues.apache.org/jira/browse/CAMEL-7859 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.14.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.14.1, 2.15.0 See nabble http://camel.465427.n5.nabble.com/Corrupt-pdf-from-classpath-tp5756921.html So you can read binary content from classpath using the constant language. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-7858) Allow to disable Jaxb annotations in JacksonDataFormat
[
https://issues.apache.org/jira/browse/CAMEL-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-7858:
---
Assignee: Willem Jiang
> Allow to disable Jaxb annotations in JacksonDataFormat
> --
>
> Key: CAMEL-7858
> URL: https://issues.apache.org/jira/browse/CAMEL-7858
> Project: Camel
> Issue Type: Improvement
> Components: camel-jackson
>Affects Versions: 2.14.0
>Reporter: Nicolás Amador
>Assignee: Willem Jiang
>Priority: Minor
>
> The existing code of camel jackson dataformat does not support that we
> disable the JaxbAnnotationModule()
> {code}
> public JacksonDataFormat(Class unmarshalType, Class jsonView) {
> this.objectMapper = new ObjectMapper();
> this.unmarshalType = unmarshalType;
> this.jsonView = jsonView;
> // Enables JAXB processing
> JaxbAnnotationModule module = new JaxbAnnotationModule();
> this.objectMapper.registerModule(module);
> }
> {code}
> If we have an attribute like this:
> {code}
> @XmlAttribute(name = "has-children", required = true)
> private Boolean hasChildren;
> {code}
> In previous version (2.9.7 for instance):
> {code}
> XML: "has-children"
> Json: "hasChildren"
> {code}
> In the current one (2.14.0):
> {code}
> XML: "has-children"
> Json: "has-children"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-632) hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is included in the generated XSD as documentation
[ https://issues.apache.org/jira/browse/CAMEL-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146008#comment-14146008 ] Claus Ibsen commented on CAMEL-632: --- We could maybe use the javadoc support from the new api component from Dhiraj to access the javadoc, and then transform the XSD to include the > hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is > included in the generated XSD as documentation > - > > Key: CAMEL-632 > URL: https://issues.apache.org/jira/browse/CAMEL-632 > Project: Camel > Issue Type: Improvement > Components: camel-blueprint, camel-core, camel-spring, eip >Reporter: james strachan > Fix For: 2.15.0, 3.0.0 > > > In tools like Eclipse/IDEA there is smart completion when editing the XML > with the XSD; however there's no documentation for elements/attributes. > We should extract the JavaDoc from the Java code and include it into the > generated XSD. There's an existing issue here... > https://jaxb.dev.java.net/issues/show_bug.cgi?id=369 > as part of this we need to improve the javadoc too :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-632) hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is included in the generated XSD as documentation
[ https://issues.apache.org/jira/browse/CAMEL-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-632: -- Fix Version/s: 3.0.0 2.15.0 > hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is > included in the generated XSD as documentation > - > > Key: CAMEL-632 > URL: https://issues.apache.org/jira/browse/CAMEL-632 > Project: Camel > Issue Type: Improvement > Components: camel-blueprint, camel-core, camel-spring, eip >Reporter: james strachan > Fix For: 2.15.0, 3.0.0 > > > In tools like Eclipse/IDEA there is smart completion when editing the XML > with the XSD; however there's no documentation for elements/attributes. > We should extract the JavaDoc from the Java code and include it into the > generated XSD. There's an existing issue here... > https://jaxb.dev.java.net/issues/show_bug.cgi?id=369 > as part of this we need to improve the javadoc too :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-632) hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is included in the generated XSD as documentation
[ https://issues.apache.org/jira/browse/CAMEL-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-632: -- Component/s: eip camel-spring camel-core camel-blueprint > hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is > included in the generated XSD as documentation > - > > Key: CAMEL-632 > URL: https://issues.apache.org/jira/browse/CAMEL-632 > Project: Camel > Issue Type: Improvement > Components: camel-blueprint, camel-core, camel-spring, eip >Reporter: james strachan > Fix For: 2.15.0, 3.0.0 > > > In tools like Eclipse/IDEA there is smart completion when editing the XML > with the XSD; however there's no documentation for elements/attributes. > We should extract the JavaDoc from the Java code and include it into the > generated XSD. There's an existing issue here... > https://jaxb.dev.java.net/issues/show_bug.cgi?id=369 > as part of this we need to improve the javadoc too :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CAMEL-632) hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is included in the generated XSD as documentation
[ https://issues.apache.org/jira/browse/CAMEL-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-632: --- > hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is > included in the generated XSD as documentation > - > > Key: CAMEL-632 > URL: https://issues.apache.org/jira/browse/CAMEL-632 > Project: Camel > Issue Type: Improvement > Components: camel-blueprint, camel-core, camel-spring, eip >Reporter: james strachan > Fix For: 2.15.0, 3.0.0 > > > In tools like Eclipse/IDEA there is smart completion when editing the XML > with the XSD; however there's no documentation for elements/attributes. > We should extract the JavaDoc from the Java code and include it into the > generated XSD. There's an existing issue here... > https://jaxb.dev.java.net/issues/show_bug.cgi?id=369 > as part of this we need to improve the javadoc too :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-632) hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is included in the generated XSD as documentation
[ https://issues.apache.org/jira/browse/CAMEL-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146007#comment-14146007 ] Claus Ibsen commented on CAMEL-632: --- JAXB ticket about support for documentation here https://java.net/jira/browse/JAXB-917 > hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is > included in the generated XSD as documentation > - > > Key: CAMEL-632 > URL: https://issues.apache.org/jira/browse/CAMEL-632 > Project: Camel > Issue Type: Improvement >Reporter: james strachan > > In tools like Eclipse/IDEA there is smart completion when editing the XML > with the XSD; however there's no documentation for elements/attributes. > We should extract the JavaDoc from the Java code and include it into the > generated XSD. There's an existing issue here... > https://jaxb.dev.java.net/issues/show_bug.cgi?id=369 > as part of this we need to improve the javadoc too :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7858) Allow to disable Jaxb annotations in JacksonDataFormat
Nicolás Amador created CAMEL-7858:
-
Summary: Allow to disable Jaxb annotations in JacksonDataFormat
Key: CAMEL-7858
URL: https://issues.apache.org/jira/browse/CAMEL-7858
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Affects Versions: 2.14.0
Reporter: Nicolás Amador
Priority: Minor
The existing code of camel jackson dataformat does not support that we
disable the JaxbAnnotationModule()
{code}
public JacksonDataFormat(Class unmarshalType, Class jsonView) {
this.objectMapper = new ObjectMapper();
this.unmarshalType = unmarshalType;
this.jsonView = jsonView;
// Enables JAXB processing
JaxbAnnotationModule module = new JaxbAnnotationModule();
this.objectMapper.registerModule(module);
}
{code}
If we have an attribute like this:
{code}
@XmlAttribute(name = "has-children", required = true)
private Boolean hasChildren;
{code}
In previous version (2.9.7 for instance):
{code}
XML: "has-children"
Json: "hasChildren"
{code}
In the current one (2.14.0):
{code}
XML: "has-children"
Json: "has-children"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
