Tan,

Thanks for reporting the inconsistencies in the bundle id and start/stop
commands - I'll correct these and the changes should be online in an hour or
two.

About the 'Adding ActiveMQ to the 'Mix' example - could you do an
log:display and check for exceptions that might give us an idea what's going
wrong there?  I'll give things a go myself as well here...

Regards,

Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/


On Tue, Aug 9, 2011 at 1:01 PM, newbie <[email protected]> wrote:

> Thank you all for great inputs. This encourages me even more to learn the
> product.
> I am trying the give at
> "http://servicemix.apache.org/docs/4.3.0-SNAPSHOT/quickstart/camel.html";
> The example given in the "Routing with Camel" works fine. But here is what
> I
> have found:
>
> At the bottom of the page it says "From this output, you also learn that
> the
> bundle id for your XML file is 209. "
> Where as in the screen shot the bunble id is 200!
>
> Then it says the following:
> "As soon as you restart the route, the pending files will get moving
> again."
> But the next line is "karaf@root> osgi:stop 200" .... I think it should be
> "karaf@root> osgi:start 200"
>
> I could easily spot these mistakes but at the same time I am worried about
> the accuracy of your stuff!
>
> Next, I started next section "Adding ActiveMQ to the 'Mix"
>
> I have copied the code from "Moving files and sending event messages" and
> put it in the deploy folder, but the is not created. When I apply the
> command osgi:list it shows "failure" in the colom
>
> I am stuck here.... and don't know why your example is not working. Can you
> please confirm that there is not error in the code for "Moving files and
> sending event messages" and "Receiving the event messages"
>
> Thank you
> Tan
>
>
>
>
> --
> View this message in context:
> http://servicemix.396122.n5.nabble.com/ServiceMix-4-3-and-tutorials-tp4659769p4681605.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

Reply via email to