You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by dont_know <do...@sharklasers.com> on 2013/01/20 23:59:59 UTC
Re: Bindy/JBoss 7 classloading problems
own reply due to mailing list problems...
--
View this message in context: http://camel.465427.n5.nabble.com/Bindy-JBoss-7-classloading-problems-tp5725684p5725852.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Bindy/JBoss 7 classloading problems
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Jan 21, 2013 at 8:37 AM, dont_know <do...@sharklasers.com> wrote:
> Hello,
>
> I've discovered a classloading problem when using Bindy (from Camel 2.10) in
> a JBoss 7 environment. Camel itself works great, but Bindy fails, because it
> uses the "build-in" classloading strategy which doesn't support the
> VFS-protocol.
>
> My current solution is to register the JBossPackageScanClassResolver from
> camel-jboss6-extras (http://camel.apache.org/camel-jboss.html) in the route
> context. This is a little bit strange, because the documentation states that
> Camel 2.8 (or greater) should work fine without
> JBossPackageScanClassResolver.
>
> My question is: Is the documentation incorrect or is it a bug?
>
camel-bindy is a special case that needs this. In the future camel-bindy will be
refactored to avoid this need.
> Greetings
> Stefan
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Bindy-JBoss-7-classloading-problems-tp5725684p5725865.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: Bindy/JBoss 7 classloading problems
Posted by dont_know <do...@sharklasers.com>.
Hello,
I've discovered a classloading problem when using Bindy (from Camel 2.10) in
a JBoss 7 environment. Camel itself works great, but Bindy fails, because it
uses the "build-in" classloading strategy which doesn't support the
VFS-protocol.
My current solution is to register the JBossPackageScanClassResolver from
camel-jboss6-extras (http://camel.apache.org/camel-jboss.html) in the route
context. This is a little bit strange, because the documentation states that
Camel 2.8 (or greater) should work fine without
JBossPackageScanClassResolver.
My question is: Is the documentation incorrect or is it a bug?
Greetings
Stefan
--
View this message in context: http://camel.465427.n5.nabble.com/Bindy-JBoss-7-classloading-problems-tp5725684p5725865.html
Sent from the Camel - Users mailing list archive at Nabble.com.