[
https://issues.jboss.org/browse/WFLY-6149?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-6149:
------------------------------------
Chris, thank you again for the discussion about this issue and your viewpoint. I think
the best suggestion is to have the Hibernate integration ([under
wildfly/jpa|https://github.com/wildfly/wildfly/tree/master/jpa]) allow the system property
"hibernate.id.new_generator_mappings" override other settings, which is what you
had expected but we do not currently do.
I'm leaving this unassigned for now. If someone wants to do the work, it will be a
useful change. If not, I'll do it. Add a comment here if your interested in
contributing a patch for this change. I'll try to provide guidance on making the
change.
Scott
Improve control over 'hibernate.id.new_generator_mappings'
setting
------------------------------------------------------------------
Key: WFLY-6149
URL:
https://issues.jboss.org/browse/WFLY-6149
Project: WildFly
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 9.0.2.Final, 10.0.0.Final
Reporter: Chris Poulsen
It would be great if Wildfly offered better control over the properties used for
configuring persistence units.
For instance the 'hibernate.id.new_generator_mappings' setting has proven hard to
control it currently requires one to change persistence.xml to turn it off.
Hibernate supports specifying the properties in various ways, for example via system
properties, but wildfly forces the new mappings to be enabled unless the persistence.xml
says to disable them.
There are some suggestions to how [~smarlow] imagines this to be implemented in the forum
thread:
https://developer.jboss.org/thread/267613
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)