camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-3914) camel-jaxb should not try to convert to BeanInvocation when routing to beans using JAXB payloads
Date Fri, 29 Apr 2011 12:58:03 GMT

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

Claus Ibsen resolved CAMEL-3914.
--------------------------------

    Resolution: Fixed
      Assignee: Claus Ibsen

> camel-jaxb should not try to convert to BeanInvocation when routing to beans using JAXB
payloads
> ------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3914
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3914
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jaxb
>    Affects Versions: 2.6.0, 2.7.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>
> When Camel uses beans in routes, the type convert system will check if the payload is
a bean invocation (used by proxy and whatnot).
> The JAXB fallback converter should not support this as it will lead to unnecessary attempts
to convert payloads to JAXB as part of the bean invocation. And that may lead to issue if
JAXB cannot do this due no ObjectFactory and whatnot.
> So even if users are routing to beans and have a signature as follows
> {code}
> public void doSomething(Exchange exchange) { 
> ...
> }
> {code}
> The end user would not expect any type converter attempt for his JAXB payload, as the
parameter type is Exchange.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message