[jbpm-dev] Re: jBPM 4 limitations

[Tom Baeyens]

2 more

* no user provided hibernate sessions
* no user provided jdbc connections

regards, tom.


Tom Baeyens wrote:
> Burr,
> 
> In jBPM 4 one of the main goals is to improve the supportability.  
> Therefor we are seriously expanding the QA capabilities in the project.
> 
> Another part of that is clearly indicate what environments and 
> configurations we support and which not.
> 
> Here are a couple of limitations that I'ld like to start with from a 
> product perspective:
> 
> * only one jBPM instance on a jboss server
> * only installation and configuration of jbpm as in the soa platform
>  - distribution ships with an ant based installer that installs jbpm 
> into jboss
>  - jbpm is installed in jbpm as a service archive
>  - jbpm ProcessEngine is published in JNDI
>  - hibernate session factory configuration as part of the jbpm installation
>  - jta transaction integration
>  - timer and async message run through our JobExecutor
> * only jboss idm identity component integration
> * no async messaging through JMS
> * no timer support through EJB Timer
> * no spring transaction integration.
> 
> We might be offering those to the community in order to get feedback and 
> flesh these out.  But until those extra features get stable and we have 
> the necessary QA build out, I would like not to introduce those into the 
> product.  This focus will help us to deliver in time.
> 
> Do these seem reasonable limitations to you ?
> 
> Do you see other jBPM aspects that need clarification if they are 
> supported or not ?
>