I feel uncomfortable to make it in Hibernate since the hibernate
configuration is not screwed up (at least not in this area). opening
this door would lead to properties vs programmatic API inconsistency
priorities and/or user unexpectation.
Max Rydahl Andersen wrote:
On Tue, 22 Nov 2005 20:52:30 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
In HEM I have to since the configuration process is standardised,
The only way to provide this feature is through configuration.
Yes I know it is required for HEM and just wondering why we dont also
just add it to hibernate core since it actually makes alot of sense
to be able to do.
/max
Max Rydahl Andersen wrote:
I fail to understand why its ok to add naming_strategy to ejb3
configuration and not hibernate configuration....?
/max
------- Forwarded message -------
From: "Emmanuel Bernard (JIRA)" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: [Hibernate-issues] [Hibernate-JIRA] Resolved: (EJB-35)
Support custom NamingStrategy as property.
Date: Mon, 21 Nov 2005 21:41:55 +0100
[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-35?page=all
]
Emmanuel Bernard resolved EJB-35:
---------------------------------
Assign To: Emmanuel Bernard
Resolution: Fixed
Support custom NamingStrategy as property.
------------------------------------------
Key: EJB-35
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-35
Project: Hibernate Entity Manager
Type: Improvement
Components: EntityManager
Versions: 3.1beta1
Environment: 3.1alpha1
EJB3 public draft
Reporter: Christian Stein
Assignee: Emmanuel Bernard
Fix For: 3.1beta5
Original Estimate: 1 hour
Remaining: 1 hour
As stated here http://forum.hibernate.org/viewtopic.php?t=944931 ,
I'd like to set a custom NamingStrategy implementation in
"persistenc.xml"s properties.
At the moment, you can only set such a custom implementation
programmatically when creating a custom Configuration object. As
this object is hidden by the EJB persistence API, it should be
possible to specify the implementation class name via a property.
Mhhh... maybe the improvement should be issued against
"org.hibernate.cfg.Configuration" which needs a method like:
/**
* Set a custom naming strategy
*
* @param name the class name of NamingStrategy to set
*/
public Configuration setNamingStrategy(String name) {
this.namingStrategy = Class.forName(name);
return this;
}
Maybe, this is the wrong place. :)
Cheers,
Christian
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
