camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Taariq Levack <taar...@gmail.com>
Subject Re: Problem with REST DSL (2.14.0) and String bean
Date Fri, 14 Nov 2014 15:15:37 GMT
Thought it would be weird to be jaxb versions in camel components.

Glad you found it, thanks for sharing your fix as well.

On Fri, Nov 14, 2014 at 11:36 AM, Vaïsse-Lesteven Arthur <
arthurvaisse@yahoo.fr> wrote:

> Thanks to a teammate, I finally understood the error.
>
> Problem really come from the definition of a "java.lang.String" bean in the
> camel context.
> When putting <bean id="source" class="java.lang.String"><constructor-arg
> type="java.lang.String" value="file:/opt/a/directory/data/audio" /></bean>
> in the camel context I got the following log :
>
> [                          main] JaxbDataFormat                 INFO
> Creating JAXBContext with contextPath: file:/opt/a/directory/data/audio and
> ApplicationContextClassLoader: sun.misc.Launcher$AppClassLoader@3485def8
>
> My understanding of the situation is that if any "java.lang.String" object
> is defined it is then used by the JAXBContext. They probably seek for an
> autowired String parameter that is normally always "null".
> Replacing "source" bean by a bean with a string attribute solve the
> problem.
>
> Unexpected side effect discovered !
>
> Thank for your attention and your time.
>
> Arthur.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Problem-with-REST-DSL-2-14-0-and-String-bean-tp5758812p5759102.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message