[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6132?page=c...
]
Hardy Ferentschik commented on HHH-6132:
----------------------------------------
{quote}
i haven't process (mocking annotations) for all
NamedQuery/NamedNativeQuery/SequenceGenerator/TableGenerator/SqlResultSetMapping defined
in orm.xml, but just collected them so, i need to know if this issue starts from index or
you'd prefer a generated jaxb class instances collection.
{quote}
Both approaches are possible. From a design point of view I would prefer the mock
approach. Seems to makes most sense imo.
{quote}
if, this starts from index, one way i'd think is i can just find a class and mock all
these annotations on to it, wdyt?
{quote}
right the problem is to which class/package to bind these mock annotations. First I
thought about the default package which can be specified, but I think even that is
optional. In the worst case the initial annotation based index might be even empty in case
the application is purely configured via xml.
I am wondering though if we couldn't just make create even a mock "default
package" annotation. I don't think that for these annotations we have to actually
load the annotation target, so it can be pretty much whatever we want. WDYT?
Process and bind global configuration annotations
-------------------------------------------------
Key: HHH-6132
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6132
Project: Hibernate Core
Issue Type: Sub-task
Components: metamodel
Reporter: Hardy Ferentschik
Assignee: John Verhaeg
Fix For: 4.0.0.Alpha3
--
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