Hi I suggest to look at the 2 pom.xml files for the different projects and see if there is any difference.
On Wed, Apr 10, 2013 at 11:21 AM, lmanchanda75 <lmanchand...@gmail.com> wrote: > Hi Claus, > > Thanks for your quick response. I order to try this out I made one more > sample application, with following context > > <camelContext xmlns="http://camel.apache.org/schema/spring";> > <package>com.fusesource.fusebyexample</package> > <route id="Jetty_Sample"> > <from uri="jetty:http://0.0.0.0:1010/volt?sessionSupport=true"; > id="ussd-1"> > <description>This endpoint receives requests from ussd > server.</description> > </from> > <process ref="ussdAdapter"/> > <log message="${in.headers} ${body}"/> > </route> > </camelContext> > > <bean class="com.fusesource.fusebyexample.myBookService" > id="myBookService"/> > <bean class="com.fusesource.fusebyexample.ComvivaUssdAdapter" > id="ussdAdapter" /> > <bean class="com.fusesource.fusebyexample.HelloBean" id="HelloBean"/> > <bean class="com.fusesource.fusebytrial.HelloTrial" id="HelloTrial"/> > > </beans> > > > > Here I am able to call both HelloBean and HelloTrial beans at run time. > > The only difference between these 2 projects is that the first one which is > not working was originally a Java project in which I replaced the POM.xml > from a camel-spring project and then made it Maven project. The second one > which is working fine was created using Fuse as a camel project. > > Please see if with this information you can suggest some difference, as I am > not able to visibility find any difference > > Regds > Lalit > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Registry-not-able-to-find-Bean-at-run-time-tp5730630p5730638.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: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
