[Hibernate-JIRA] Created: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them
4:36 a.m.
"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
4:49 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-893?page=co...
]
Max Rydahl Andersen commented on HBX-893:
-----------------------------------------
set hibernate.query.startup_check to false to avoid this (i'll keep this bug open to
make it an automatic option)
The problem is that there are no way for us to build a sessionfactory (to execute queries)
if there are errors in the mappings.....
"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
3:19 p.m.
New subject: [Hibernate-JIRA] Commented: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-893?page=co...
]
Joseph Marques commented on HBX-893:
------------------------------------
Just to make sure we're on the same page...I received the "Can't create
session factory" when the JPQL in one of my @NamedQuery annotation was incorrect. In
THIS case, I think you should be able to gracefully mark the class because the @NamedQuery
doesn't affect the mapping - it simplies relies on it.
If there is a larger problem, such as errors in the mappings like you mentioned, then
that's certainly bound to cause more issues in general. However, perhaps you can
still try to recover from this. You can start scanning from the problematic entity and
find the connected component it is a part of. A connected component is essentially
anything that that entity can traverse to by following its valid mappings. because not
all domain models are a single connected component.
Then, you can "disable" all of these connected entities - in other words,
don't even try to load them in the session factory proper. However, you could still
show them in the session factory portion of the Hibernate Configuration view as
"greyed out" entities. This lets the user know which connected component has an
error in it, and you can STILL try to color the entity that started the mapping cascade
failure red.
"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
3:52 p.m.
New subject: [Hibernate-JIRA] Commented: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them
[
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
10:18 a.m.
New subject: [Hibernate-JIRA] Resolved: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-893?page=co...
]
Max Rydahl Andersen resolved HBX-893.
-------------------------------------
Resolution: Won't Fix
this is a duplicate of other issues and a current Won't fix since it would require a
massive work to allow us to read incomplete mappings.
"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
Issue Type: Bug
Affects 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
10:20 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-893?page=co...
]
Max Rydahl Andersen commented on HBX-893:
-----------------------------------------
note we have added various error catching code that should make it less
"intrusive"
"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
Issue Type: Bug
Affects 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
5789
days inactive
6518
days old
hibernate-issues@lists.jboss.org
5 comments
2 participants
participants (2)
-
Joseph Marques (JIRA) -
Max Rydahl Andersen (JIRA)