Bug 1182351

Summary: (6.3.z) HHH-9467 - Cannot enable NamingStrategyDelegator implementations using standalone schema tools
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Carlo de Wolf <cdewolf>
Component: HibernateAssignee: Gail Badner <gbadner>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Simka <msimka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: cdewolf, gbadner, jawilson, msimka, smarlow
Target Milestone: CR1   
Target Release: EAP 6.3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1182324 Environment:
Last Closed: 2019-08-19 12:38:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1182324    
Bug Blocks: 1151405, 1159890    

Description Carlo de Wolf 2015-01-14 22:41:13 UTC
+++ This bug was initially created as a clone of Bug #1182324 +++

Description of problem:
It is not possible to configure a NamingStrategyDelegator when using the standalone schema tools (SchemaExport, SchemaUpdate, SchemaValidator) or schema ant tasks (SchemaExportTask, SchemaUpdateTask, SchemaValidatorTask).

This fix completes Hibernate's support for NamingStrategyDelegator.

How reproducible: always

Steps to Reproduce:
Use a schema tool with --namingdelegator=<NamingStrategyDelegator_class_name>
See org.hibernate.test.schematoolsnaming.StandaloneSchemaToolsNamingTest for test.

Actual results:
--namingdelegator=<NamingStrategyDelegator_class_name> is ignored and the default (LegacyNamingStrategyDelegator) is used instead.


Expected results:
The specified NamingStrategyDelegator implementation should be used.

--- Additional comment from Gail Badner on 2015-01-14 21:52:55 CET ---

https://hibernate.atlassian.net/browse/HHH-9467

--- Additional comment from Gail Badner on 2015-01-14 21:56:57 CET ---

This was fixed in 4.2.17.Final.

Comment 1 Martin Simka 2015-01-21 09:01:57 UTC
verified on EAP 6.3.3.CP.CR1