Agree for camel-ejb, but as you said it's useless. I mostly used it
remotely (or using a EJB proxy).
For the push in Camel, let me know if I can help ;)
Regards
JB
On 01/24/2012 09:39 AM, Romain Manni-Bucau wrote:
camel-ejb component can do local invocation too playing with the initial
context ;) but i think it is pretty useless since you can always add your
ejb proxies to the came registry.
the camel-openejb component uses camel-core and openejb-core (and
optionnally openejb-provisionning) as dependencies.
+1 to push it in camel since it is where users could search it
- Romain
2012/1/24 Jean-Baptiste Onofré<[email protected]>
Hi Romain,
it looks interesting.
As reminder, in Camel, we have the camel-ejb component to perform RMI-IIOP
EJB call.
I will take a deeper look in the camel-openejb component.
Depending of the dependencies, don't you think it could be in camel
directly (like the others components) ?
Regards
JB
On 01/24/2012 09:31 AM, Romain Manni-Bucau wrote:
Hi guys!
i pushed a little camel here
https://svn.apache.org/repos/**asf/openejb/trunk/camel/camel-**openejb/<https://svn.apache.org/repos/asf/openejb/trunk/camel/camel-openejb/>
the goal is not to invoke ejbs (as it could be expected) but to
deploy/undeploy application to an openejb instance.
you can have a look to the test (
https://svn.apache.org/repos/**asf/openejb/trunk/camel/camel-**
openejb/src/test/java/org/**apache/openejb/camel/**
OpenEJBDeploymentCamelTest.**java<https://svn.apache.org/repos/asf/openejb/trunk/camel/camel-openejb/src/test/java/org/apache/openejb/camel/OpenEJBDeploymentCamelTest.java>
)
for a sample.
It lets you to use the power of camel (= number of connectors) to deploy
your app.
it is compatible with the provisionning module we have on trunk (to deploy
from maven or http urls).
- Romain
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
