Bug 1182351 - (6.3.z) HHH-9467 - Cannot enable NamingStrategyDelegator implementations using standalone schema tools
Summary: (6.3.z) HHH-9467 - Cannot enable NamingStrategyDelegator implementations usin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Hibernate
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.3.3
Assignee: Gail Badner
QA Contact: Martin Simka
URL:
Whiteboard:
Depends On: 1182324
Blocks: eap633-payload 1159890
TreeView+ depends on / blocked
 
Reported: 2015-01-14 22:41 UTC by Carlo de Wolf
Modified: 2019-08-19 12:38 UTC (History)
5 users (show)

Fixed In Version:
Clone Of: 1182324
Environment:
Last Closed: 2019-08-19 12:38:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.