not sure why...
but I have added the generated-src into classpath, it still throws class not
found error (TestLogger_$logger class)
by enabling org.jboss.logging.Messages#GENERATE_PROXIES (-DJ=true) it works
---
Strong Liu
http://hibernate.org
http://github.com/stliu
_
Maybe, in our case we just wanted a session outside of the main one that
could still see the uncommitted (but flushed) data but could apply
alternate filtering and also avoid an infinite flush loop in some cases.
The key is that we might be looking at some newly inserted/updated
records and don't w
> The solution is essentially a recursive flush. There is obviously a danger
> there and we would certainly want to depth-limit this.
>
> What do y'all think about getting this into 4.0?
I can only say that I encountered the problem twice as a Hibernate user so the
feature would be very welco
Actually, i wonder now if allowing just the connection to be shared makes any
sense. Maybe it needs to always be the transaction context in those cases?
On Friday, April 01, 2011, at 11:11 am, Steve Ebersole wrote:
> Shawn, you would use:
> session.sessionWithOptions().connection().openSession(
Yes Hibernate Search at least needs to be notified to be closed, it
has helper threads which need to be shutdown, and many resources to be
closed.
nice name :)
2011/4/1 Steve Ebersole :
> Silly name aside, do we need an option to allow callback to Integrators when
> the SessionFactory closes?
>
>
I *believe* so
On Friday, April 01, 2011, at 11:18 am, Sanne Grinovero wrote:
> 2011/4/1 Steve Ebersole :
> > Shawn, you would use:
> > session.sessionWithOptions().connection().openSession()
> >
> > That connection() call says "use the connection from the underlying
> > session in the new sessio
2011/4/1 Steve Ebersole :
> Shawn, you would use:
> session.sessionWithOptions().connection().openSession()
>
> That connection() call says "use the connection from the underlying session in
> the new session". Although I think you are really more looking for:
> session.sessionWithOptions().transa
Silly name aside, do we need an option to allow callback to Integrators when
the SessionFactory closes?
---
Steve Ebersole
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibern
Shawn, you would use:
session.sessionWithOptions().connection().openSession()
That connection() call says "use the connection from the underlying session in
the new session". Although I think you are really more looking for:
session.sessionWithOptions().transactionContext().openSession()
saying
Steve,
Saw this yesterday. Looks like I'll be able to remove my patch that is
currently allowing me to inject my session factory into session obtained
from a getCurrentSession() call which makes me very happy. I'll dig up
the JIRA so you guys can kill it.
One question though, with the session.s
We can do it either way. Of the ones I converted to using Integrators, search
and envers both have "skip" settings defined.
search: hibernate.search.autoregister_listeners
envers: hibernate.listeners.envers.autoRegister
(should really standardize these names)
I guess it really depends on the in
You would use java.sql.DatabaseMetaData which is exactly what Hibernate is
using to detemine the dialect to use.
And this is not a help forum, this is a mailing list to discuss the
development of Hibernate.
On Friday, April 01, 2011, at 10:12 am, Tom Muldoon wrote:
> I currently do not specify
Currently, if a callback (jpa-style, Lifecycle, Listener) called during during
a flush results in an action (as in ActionQueue) being added, that action is
ignored until the next flush cycle.
I thought we discussed (in st louis) adding a feature to allow those actions
to be caught up in the ori
I currently do not specify the hibernate.dialect in my configuration (which
means Hibernate must be determining the dialect based upon my url, right?) but
even if I did, I don't know how to get the property value at runtime. Whatever
the case, what's the best way to determine the underlying data
RE: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2860
This dealt with cleaning up all the overloaded openSession methods from
SessionFactory and SessionFactoryImplementor.
The new main method for obtaining a Session is SessionFactory.withOptions()
which returns a org.hibernate.
15 matches
Mail list logo
