[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-893?page=co...
]
Max Rydahl Andersen commented on HBX-893:
-----------------------------------------
yes we are on the same page and if you set the property I listed it should not complain.
With respect to "disable" connected entities to something that errors then
a) it would require us not using the auto scanning actually used in hibernate
b) it would require us to have a completely seperate parsing of the entities/model that
validates the model before handing it to hibernate...
i'm not saying this is not something we should do; but right now i/we focus on not
reimplementing major parts of the parsing in the tooling.
"Can't create session factory" if any @NamedQuery
annotations on entities have errors in them
---------------------------------------------------------------------------------------------
Key: HBX-893
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-893
Project: Hibernate Tools
Type: Bug
Versions: 3.2beta8
Reporter: Joseph Marques
This seems to be a pretty big restriction - especially if you want to be able to cater to
those that try to adopt Hibernate Tools part of the way through development, where some
annotations may already have errors in them.
Instead, it should be much more user-friendly to expand the session factory anyway, but
just not load those entities - perhaps even marking them with a little red 'X' to
indicate that the user needs to fix something in them.
--
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