What are the requirements for BPM component when setting persistence=true

[jorgemoralespou_2]

Hi,

We have done some projects with BPM components in them, and looking at the quickstarts it seems that whenever we need persistence, we need to deploy the persistence unit within the composite jar application. If we remove the persistence.xml the process complains that can not find the required persistence unit.

Looking at the configuration created with the installer, it seems that for BPEL, it set persistence configuration in the switchyard subsystem, but for jbpm it doesn't .

Shouldn't persistence definition be configured with the subsystem and dependent modules, and not require to deploy the persitence.xml along with the composite application?

[dward]

I choose to leave it up to the composite applications to include the persistence.xml file so that they have the ability to change the database properties within it. For example, the provider, jta-data-source, dialect, show_sql, etc.

[jorgemoralespou_2]

But shouldn't the core engine for all BPM services deployed in the runtime be run against same DB? Is there a purpose or real use case to allow different services deployed in the switchyard engine to run with different persistence properties?

How would I set a default configuration for the whole engine in case I wanted to?

I think this is the usual use-case, and allowing for different persistence configuration per composite should be a rare case.