Re: [hibernate-dev] AS7 use of the "hibernate.ejb.resource_scanner" property to override the default org.hibernate.ejb.packaging.Scanner...
Hi,
as mentioned in the discussion on IRC I am definitely for a move to jandex.
In fact the current metamodel code I am implementing uses jandex.
Personally I did initially not think about the possibility to share the
jandex
index between AS7 and Hibernate, but it sounds of course like a good idea.
Unfortunately, I don't know so much about the integration layer between AS
and Hibernate, so if we definitely have to summarize/discuss.
One question which comes to my mind is how XML configuration fits into the
picture
here? Sharing a pure annotation repository/inde does not seem to be
enough!?
--Hardy
On Sun, 27 Mar 2011 19:36:43 +0200, Scott Marlow <smarlow(a)redhat.com>
wrote:
We just discussed Hibernate 4.0 annotation scanning the other day and
I
wanted to add to the conversation (which was about using
https://github.com/jbossas/jandex).
As a workaround for https://issues.jboss.org/browse/JBAS-9141, I'll
request a merge of the following change. This is about AS7 setting the
"hibernate.ejb.resource_scanner" property to
org.jboss.as.jpa.hibernate.HibernateAnnotationScanner (which implements
the org.hibernate.ejb.packaging.Scanner interface).
If we move away from supporting the current Scanner interface in
Hibernate 4.0, we should discuss the impact on the AS7 scanner
implementation.
The HibernateAnnotationScanner class is in this commit (with other
changes that go with it):
https://github.com/scottmarlow/jboss-as/commit/5aaaa630f38d89d3bbbe832cac...
Scott
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev