By the way: Biggest issue I have with it is, that then you have to work with a
RemoteCommandExecutor instead of a CommandService (the real interface).
In my app I want to use the CommandService (interfcae), not knowing that a
RemoteCommandService sits behind it. Would be possible with EJB 3 out of the box, without
using the "EjbRemoteCommandService" wrapper...
For the EjbRemoteCommandService I have a question: Why is the InitialContext created every
time I execute a command (isn't that expensive?)? Should be improved I think (lazy
create it once).
And why can't it read the jndi.properties from the classpath as an alternative?
Can I improve that class a bit? If you don't use it in the ProcessEngine wiring but
directly from a remote client, it is not that nice this way...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236647#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...