I am sorry but I have not understood your example.
Coming back to your rules:
> 1. Blueprint requires the presence of all the objects (beans) in the
public OSGi part.
You can create blueprint beans with a class from a private package. Why
should that not work?
> 2. These objects can create objects from the private OSGi part.
That is correct of course.
> 3. Objects must not contain public methods taking or transmitting
other objects from the private part.
If you publish an object as a service for example then of course it can
not have parameters from the private part as the user of the service
would not see them. What objects are you talking about here? Objects
used in your camel route? I would assume that objects from private
packages can be used for example as processors. If that does not work I
would assume this is a bug.
So what I typically do is create a camelcontext and a RouteBuilder bean
in blueprint. As far as I know the RouteBuilder impl can be private.
Christian
On 20.01.2014 12:26, alexey-s wrote:
Hi, Christian
My sample code:
blueprint error code:
Move class A from package myapp to package myapp.imp.camel.processes
Create Java DSL RouteBuilder
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-main-class-in-osgi-bundle-tp5746113p5746246.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
