[ https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug... ] Andy Black edited comment on JBRULES-3305 at 12/14/11 1:48 PM: --------------------------------------------------------------- Jim Tyrell posted this for me as I didn't have an account setup at the time. We are basically looking to be able to use OpenJPA for the peristence layer. The reason for this is our deployment environment. We'd like to run the JBPM/Drools middleware on IBM Websphere running on z/OS. The JPA provider for this platform is a fork of OpenJPA. IBM has made enhancements to this fork in order to support their pureQuery environment for DB2. This support would allow us to leverage DB2 static execution for the JPA environment. Basically this means better performance at the database layer. Also, our DBA would like to map the JBPM/Drools persistence table name to different names in our environment. I think he wants to shorten the name a little and add JBPM_ as a prefix on all JBPM/Drools persistence table names. If we eliminate all hibernate specific annotations and imports then we could accomplish the table name mapping using an appropriate orm.xml file. was (Author: arblack.bop): Jim Tyrell posted this for me as I didn't have an account setup at the time. We are basically looking to be able to use OpenJPA for the peristence layer. The reason for this is our deployment environment. We'd like to run the JBPM/Drools middleware on IBM Websphere running on z/OS. The JPA provider for this platform is a fork of OpenJPA. IBM has made enhancements to this fork in order to support their pureQuery environment for DB2. This support would allow us to leverage DB2 static execution for the JPA environment. Basically this means better performance at the database layer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira