JBossDeveloper

Hi kukeltje,

Thank you :)
Could you even answer my other question one post above? The one with the communication possibilities.

Wolf

Thank you once again.
What is ESB?
I will make a summary lates this evening :)

ESB = Enterprise Service Bus? Then i got it ;)

Summary:

Question: Regarding jPDL: Can it be converted to another language? For example XPDL? Is there any correlation btw. both of them (XPDL and jPDL)?
Answer: Each activity has an implementation, which can be a task (task in a task-node) or a sub-flow (proceess-state), among others. Transitions can be attached conditions (transitions conditions in a decision node). Nodes can impose restrictions on incoming and outgoing transitions to model choice, concurrency and partial or total synchronization (fork, join and decision nodes).

Given this shallow comparison, I'm convinced there is a mechanical procedure to convert XPDL documents to jPDL documents. The inverse is not possible if the jPDL document contains delegations. In a nutshell, jPDL can be converted to XPDL. It's just that we feel, with the feedback from the community in mind, that the considerable effort needed to provide an XPDL converter does not add enough value to justify it.

Question: Regarding the BPEL Extension: Which BPEL Standard is supported? I found standard 1.1 and 2.0 mentioned. Are both of them fully supported?
Answer: Regarding BPEL, we aim to support versions 1.1 and 2.0. The latter is a moving target, tough, because the OASIS technical committee is still working on it. Right now we are working in the draft dated Sep 1, 2005.

Question: What does the role concept of jBPM look like? With role concept i mean that processes can be attached to different roles.
Answer: jBPM makes a separation between process roles, termed swimlanes after the equivalent concept in UML activity diagrams, and organization roles. This allows you to group responsibilities irrespective of the actual shape of the organization.
See the jBPM user guide, section 9.4 for details about swimlanes.

Question: BPEL doesnt support any kind of roles, as far as i know. Is this right?
Answer: BPEL, as an orchestration language, defines service roles. There is a construct in BPEL called partner link, which models the conversational relationship between two (web) services. Further, it defines the role of each service in the conversation. A partner link type defines the connection between these two services. Note the two roles in the relationship and how a port type specifies the interface each service presents to the other.

Question: Is some kind of admin tool available for jBPM? (for monitoring running processes and so on)?
Answer: The jBPM web application supports the creation of new process instances, task lists, and several monitoring capabilities. Try the starters kit. You can have it running in 5 minutes and it will give you a better idea of what we offer.

Question: Is there the possibility of administrating work- / todo lists?
Answer: With "todo lists" you mean a list of tasks to be performed by a given person? If so, jBPM and the web app do it.

Question: What communication possibilities does jBPM provide? SOAP? RMI? etc.
Answer: jBPM itself does not provide specific actionhandlers or components to achieve this (yet). Since actionhandlers are written in Java, you can do anything you like.
e.g. Get a WSDL, generate javacode and make an actionhandler out of it. There has been some thinking of providing some soap wrapper, but it is not high on the list, since it is very to have any kind of communication.
If you think esb (Enterprise Service Bus) (e.g. the upcomming jboss implementation or others, mule, servicemix) they provide you with service bindings (jbi communication service) for e.g. mq, jms, soap, ftp etc.... now that would be great....

Question: Does jBPM support process simulation?
Answer: No.

@PiN: Ja, bin ich ;)