On 15 July 2011 11:21, Don Doffe <forrestl...@gmail.com> wrote: > Babak, > > I had a problem with camel deployment to JBoss. There was a need for a > special library to enable scanning of the custom packages as camel > components, and a configuation line in appContext.xml (assuming you are > using spring): > > <bean id="jbossResolver" > class="org.apache.camel.jboss.JBossPackageScanClassResolver"/> > > > Have you fixed that? > > If not I could send you the library.
As an aside I raised this issue today... https://issues.apache.org/jira/browse/CAMEL-4233 going forward it'd be good if we could avoid package scanning by default (by having our build generate fully qualified names of type converter classes to be loaded to avoid the package scan). If this were implemented Camel might work out of the box in JBoss without any custom configuration or resolver? -- James ------- FuseSource Email: ja...@fusesource.com Web: http://fusesource.com Twitter: jstrachan, fusenews Blog: http://macstrac.blogspot.com/ Open Source Integration and Messaging
