[
https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug...
]
Marco Rietveld commented on JBRULES-3318:
-----------------------------------------
Jim,
This _should be_ possible if the client modifies their persistence.xml and orm.xml files:
They can use the "xml-mapping-metadata-complete" attribute to make sure that
none of the JPA annotations in the code are used.
If they're purely using drools-persistence-jpa (no jbpm), then this shouldn't be
an issue. With jBPM and JPA 1, this isn't possible because of functionality that
exists in hibernate 3.x, but not in JPA 1. If they migrate to JPA 2, then it also becomes
possible for jBPM.
Of course, it'd probably be helpful if we provided the example alternate
persistence.xml and orm.xml files for them that do this? :)
I'll see if I can provide these by the beginning of next week (july 23rd).
Enable the Use of Different Table Names in drools-persistence-jpa
-----------------------------------------------------------------
Key: JBRULES-3318
URL:
https://issues.jboss.org/browse/JBRULES-3318
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Jim Tyrrell
Assignee: Marco Rietveld
Fix For: FUTURE
Customer is noticing a few table names that they would like to change out, ie use
different ones. They also would like the table structure to match the naming conventions
their organization employes.
--
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