Hi,
Is there a way for services (living in the SF-scoped registry) to get
notified when the session factory has been set up and perform some action
using that completely initialized factory?
Upon invocation of initiateService() of SessionFactoryServiceInitiator
implementations, the passed factory
Hi,
not sure whether this could work in your use case, but in Search we use a
SessionFactoryObserver.
We register the observer in Integrator#integrate with the
SessionFactoryImplementor.
Once the SessionFactory is completely build you get a callback into
SessionFactoryObserver#sessionFactoryCre
2014/2/11 Hardy Ferentschik
> Hi,
>
> not sure whether this could work in your use case, but in Search we use a
> SessionFactoryObserver.
> We register the observer in Integrator#integrate with the
> SessionFactoryImplementor.
> Once the SessionFactory is completely build you get a callback into
> Yes, that helps indeed. Implementing my validation routine in such an
observer works. I guess if needed, I even could implement support for the
suggested service contract in OGM with help of an observer.
In OGM, we used to have a SessionFactoryObserver but we removed it in favor
of the SessionFa
> a) it adds many empty packages which seem user-exposed but actually
aren't (org.hibernate.ogm.logging, org.hibernate.ogm.logging.
mongodb) and b) it makes it cumbersome to structure impl-internal stuff
into sub-packages (have a look at the CouchDB module [1] to see what I
mean).
I think I've mis
2014/2/11 Davide D'Alto
> > Yes, that helps indeed. Implementing my validation routine in such an
> observer works. I guess if needed, I even could implement support for the
> suggested service contract in OGM with help of an observer.
>
> In OGM, we used to have a SessionFactoryObserver but we r
> I can "inject" the SF into a DatastoreProvider by having it implement
said StartStoppable contract. But as pointed out before the SF is not yet
completely initialized at this point. So I e.g. can't access the entity
persisters.
Isn't the SessionFactory already created by the time
StartStoppable#
No, at least not in the case of DatastoreProvider.
I think it depends on the specific service and when it is requested for the
first time. DatastoreProvider is retrieved for the first time while the SF
initialization is still in progress (via entity persister -> grid dialect
-> datastore provider)
I think if you need to make sure the SessionFactory is fully initialised,
you’ll need an observer.
On 11 Jan 2014, at 12:55, Gunnar Morling wrote:
> No, at least not in the case of DatastoreProvider.
>
> I think it depends on the specific service and when it is requested for the
> first time.
Discussed Jandex and ClassMate usage, integration of BV into the new 5.0
code. Also discussed possible expansion of Jandex as a full "offline
reflection library", which I started discussing with Jason; he is on board
in principal.
[11:38] Minutes:
http://transcripts.jboss.org/meeting/irc.freeno
Hi,
I've a Groovy project where I use RESTEasy with CDI (Weld) and deploy to
embedded Jetty. What I can't seem to get working is bean validation. The
documentation says that adding 'resteasy-validator-provider-11' along with
hibernate validator dependencies (hibernate-validator,
hibernate-validator
11 matches
Mail list logo
