User development,
A new message was posted in the thread "Ability to configure jBPM in
persistence.xml":
http://community.jboss.org/message/521951#521951
Author : Marcin Zaj?czkowski
Profile :
http://community.jboss.org/people/Szpak
Message:
--------------------------------------------------------------
Thanks for your response Ronald!
kukeltje wrote:
Btw, is there a specific reason to not wanting to have two config files? Most likely jBPM
will have it's own persistence.xml file don't you think so, maybe even it's
own datasource so it is replacing one file for another. Or do you want to ditch hibernate
complete in favour op TopLink, OracleLink EclipseLink or some other framework :-)
I
use Hibernate and plan to use it in the future, but wanted to use it as a JPA provider to
be able for example (in theory - there are a few problems with JSF and Seam) to run my app
on Google Apps Engine.
Two config files are ok, but it increase startup time what is especially onerous during
development. I will think about a read need to be provider independent.
kukeltje wrote:
jBPM does not deploy processdefinitions on it's own. Yes it is done trough the jBPM
api but that has to be triggered somewhere (e.g. Seam) so find the source of what is
triggering the deployment and fix it there.
Ok, I will try track it down on Seam
side.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/521951#521951