depends on your deployment model... what docs did you read? the core/server can be just a jar, so in tyhat case you contact it via a pojo interface.... or the enterprise way where you can also connect via ejb or jms
Your last question leads me to think you did way to little reading.....
Well I've read some documentation on the forum and the jPDL User Guide, I guess I was hopping the find some documentation on the API (except the javadoc), with some examples and stuff like that.
About my classes deployment, like Actions, how is the deployment done? Is there an API for that?
look at the testcases... LOTS of 'examples' there that use te api, including deployment etc
Yeah I'm getting there, but slowly... :)
Just don't get one thing, where are the classes deployed on the database? I'm asking this because my purpuse is to use the same Actions to many process definitions.
the processarchive is spread over more than one table. If you want actions to be used in more than one process, then either do that in a packaging step or deploy a separate jar outside the process
The classes are not deployed on the database as such. The proces definition is stored in the db. This includes the definition of each and every node, action, assignment and all the other definitions in a process. Note that all these element are always bound to one proces definition. No reuse as far as I understand it.
What you could reuse are the classes for the different handlers.