[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-306?page=co...
]
jpk commented on EJB-306:
-------------------------
Not even a clue?
In the JPA way of auto-configuring through persistence.xml specifically the
hibernate.archive.autodetection flag, creation of concrete Configuration instances are no
longer necessary for bootstrapping Hibernate. Although it is possible via
Ejb3Configuration class, it is arguably not desireable as this burdens the developer with
another artifact to maintain. And the Configuration class holds key schema related
attributes that are not available in ClassMetadata namely the DDL column length
attribute:
E.g.: @Column(nullable=false, length=32)
public String getEntityPojoProperty() ...
So can we make this length attribute available by way of accessing the ClassMetadata
object which is available from the SessionFactory at runtime since the Configuration
instance is NOT available at runtime?
make column length available in StringType
------------------------------------------
Key: EJB-306
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-306
Project: Hibernate Entity Manager
Issue Type: Improvement
Components: EntityManager
Affects Versions: 3.3.1.GA
Reporter: jpk
Why don't we make available the underlying column length for the
org.hibernate.type.StringType?
This way, JPA flavored hibernate deployments can stick with the ClassMetadata
interrogation approach and not have to be beleaguered with having to have a separate
Configuration instance just to get at this highly desirable and useful attribute!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira