[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1423) idenitfy supported deployments

[Tom Baeyens (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBPM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12426409#action_12426409 ] 

Tom Baeyens commented on JBPM-1423:
-----------------------------------

@Miguel, 

The execution modes are basically split into 2 categories: service and client.

Service execution modes means that there is a XxxService being used.  Translating the method into a command and then the command is executed behind a set of interceptors and inside an environment block.  These are the persistent use cases in standard java and enterprise java.

Client execution mode means that the process is executed by invoking methods on the java object model (ClientExecution) directly.   This is used for in-memory execution.  Because of the cross cutting concerns (persistence/transactions and so on), these API's were differentiated.

The client execution mode is used to test the functional behaviour of the PVM features in the PVM test suite.  Each time we develop a new feature, the client execution mode is used to develop it.  Once that is done, we add persistence into the mix.

Now, coming back to your point:  For the service execution modes, there are a lot of configurations thinkable.  But all of those should be used with the same API. So for all the service (read persistent) execution modes, we should make sure that these are tested (at least in the continuous integration) in all the supported configurations.





> idenitfy supported deployments
> ------------------------------
>
>                 Key: JBPM-1423
>                 URL: https://jira.jboss.org/jira/browse/JBPM-1423
>             Project: JBoss jBPM
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: PVM
>            Reporter: Tom Baeyens
>            Assignee: Tom Baeyens
>            Priority: Blocker
>
> Identify the supported deployment environments and the corresponding configurations.
> This basically will come down to transaction configurations in pvm, hibernate, spring, ejb and the likes.
> Configurations:
> * pvm
> * hibernate
> * ejb
> Controlling transactions:
>  * Hibernate transaction programmatic
>  * Direct JDBC connection programmatic 
>  * JTA UserTransaction programmatic (== BMT?)
>  * CMT through EJB deployment descriptors
> Also take given JDBC connections into account

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira