On 03/27/2011 01:36 PM, Scott Marlow wrote:
> We just discussed Hibernate 4.0 annotation scanning the other day and I
> wanted to add to the conversation (which was about using
I mean, possibly using jandex... ;-)
> https://github.com/jbossas/jandex).
>
> As a workaround for https://issues.jboss
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 se
Btw, org.hibernate.cfg.search.HibernateSearchEventListenerRegister is
deprecated saying that "as of release 3.4.0.CR2, replaced by Hibernate
Search's {@link
org.hibernate.search.cfg.EventListenerRegister#enableHibernateSearch(EventListeners,
Properties)}". Just be aware that that signature wi
HHH-5562 is done, which introduces a locator/discovery means for integrating
with Hibernate. Specifically it introduces the (alternate name suggestions
welcome, i am indifferent to this one) org.hibernate.impl.Integrator
interface.
It does discovery based on a classpath lookup for a well-defin
OK, now that we have been doing this for a few months and have some actual
experience, I wanted to circle back and talk about this notion of splitting up
packages to denote api/spi/internal intent.
Not so much "should we do it". I think we absolutely should to help do osgi
stuff a little lat
