On Mar 23, 2009, at 09:31, Steve Ebersole wrote:
1) If commons-annotations *does not* rely on hibernate-core in any way
then I'm fine to break it it back out if that makes sense. However
y'all need to be *extremely* careful about this and making sure about
compatibility. The whole idea about
This list is not for support, it's for the development of Hibernate.
You can take your question to the forums or raise a JIRA if you think
you've found a bug.
Best,
Chris
Yan Falken wrote:
ok - I think it should support multiple works as there is no way to
control clients to do just one oper
ok - I think it should support multiple works as there is no way to
control clients to do just one operation type - and I think
therefore it can be considered as a bug ... please can someone from HS
team look at it and clarify ASAP?
thanks
YF
On Mon, Mar 23, 2009 at 02:00:50PM +0100, Yan Falken
1) If commons-annotations *does not* rely on hibernate-core in any way
then I'm fine to break it it back out if that makes sense. However
y'all need to be *extremely* careful about this and making sure about
compatibility. The whole idea about moving these things back together
was to make the com
Hi,
I have the following problem with indexing in transaction with hibernate
search: in case the transaction is opened and I want to perform multiple
work types - only one type is actually performed after the commit and the
others are
ignored; example:
TransactionManager tm = new DummyTransact
Hi there,
I would like to start a discussion around a few 'management' questions.
1. What shall we do with commons-annotations? commons-annotations became a
module of Core (core/trunk/commons-annotations) when we moved
Annotations
and EntityManager into Core. Emmanuel, raised the questio
