Difference between the remote access to jBPM through service interfaces and RemoteCommandExecutor

[jiemin]

Hello all

We can communicate with jBPM, which is deployed on a JBoss serer, through the service interfaces (using jbpm.jbossremote.cfg.xml) or the RemoteCommandExecutor (using jndi.properties). I have tried the two ways by jBPM 4.1 with sucess. But I don't know the difference between them.

When should I use the service interfaces?

And when should I use the RemoteCommandExecutor?

How can I download the souce code for the classes in package org.jbpm.enterprise.internal.ejb? it is not in the src folder.

Thanks a lot for your help.

Greeting, Jiemin

[kukeltje]

The services use the commandExecutor internally. So they are a wrapper.  Personally, I try to use the services as much as possible.

[huber]

Hello Jiemin,

I'm very interested in !remote! access to jbpm4 using the new (high level) service interfaces (executionService, taskService, ...).

I only succeded in getting remote access through the RemoteCommandExecutor ("ejb-Solution").

Could you please give some more detailled information, how you did in getting remote access to the new service API.

I searched the forum for remote access to the new service API, but could not find non-ambiguous information or any coding instructions (http://community.jboss.org/message/399124#399124 - ..."The jBPM service bound to the JNDI is not a remote component, like an  EJB or Servlet."...;

http://community.jboss.org/message/399195#399195; http://community.jboss.org/thread/120245

Your help is very much appreciated.

Thanks

Johannes