Hello, i was wondering is it OGM stable enough and will it support
cassandra soon ? Saw on github that you are working on it.. thanks.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Depends what you call soon and if you want to contribute :)
But generally, I don't see it ready before a month or two at least.
On 16 mars 2012, at 12:40, Теодор Димов wrote:
> Hello, i was wondering is it OGM stable enough and will it support
> cassandra soon ? Saw on github that you are working
Hi Hardy, Gunnar and all,
I am thinking that we should get the ball rolling on an implementation of
Hibernate Validator that supports Bean Validation 1.1.0.Alpha1 so that we can
gather feedback.
When do you think we can get an HV Alpha supporting the changes? What about a
month?
Emmanuel
_
In case anyone is interested:
https://hibernate.onjira.com/browse/HHH-6823
https://hibernate.onjira.com/browse/HHH-5951
On Thu 15 Mar 2012 03:21:56 PM CDT, Steve Ebersole wrote:
> I like #2 as well. There is already a JIRA for that. In addition there
> is also a JIRA for adding some auto-detect
Yes that covers it all.
By the way these are perfect issues for somebody wanting to step up but not
knowning the Hibernate code base. This is quite isolated.
On 16 mars 2012, at 13:56, Steve Ebersole wrote:
> In case anyone is interested:
>
> https://hibernate.onjira.com/browse/HHH-6823
> https
Hi,
On Mar 16, 2012, at 1:29 PM, Emmanuel Bernard wrote:
> I am thinking that we should get the ball rolling on an implementation of
> Hibernate Validator that supports Bean Validation 1.1.0.Alpha1 so that we can
> gather feedback.
the biggest problem is that we really want HV 4.3 being comple
Reference https://hibernate.onjira.com/browse/HHH-7020 and
https://hibernate.onjira.com/browse/HHH-7090...
Essentially, having 2 sessions share a JDBC connection is currently
broken. Adam, Lukasz and I discussed this on the mailing list a few
months ago and Shawn has been helping me investigat
Good point. I added that flag to the JIRAs
On Fri 16 Mar 2012 08:06:53 AM CDT, Emmanuel Bernard wrote:
> Yes that covers it all.
> By the way these are perfect issues for somebody wanting to step up but not
> knowning the Hibernate code base. This is quite isolated.
>
> On 16 mars 2012, at 13:56
On 16 mars 2012, at 14:17, Hardy Ferentschik wrote:
> We can also try to get a HV 4.3 out asap just focusing on what's really
> required. Once it is out we start with HV 5 directly.
I'm for that option personally.
___
hibernate-dev mailing list
hiber
I was just thinking about this related eg discussion
http://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2011-10/message/3
from last fall and wonder if the default could be something like:
if attempt to use jndi naming and lookup
TransactionSynchronizationRegistry works, use the TSR
Unfortunately JtaPlatform covers more than just sync registration...
On Fri 16 Mar 2012 09:43:45 AM CDT, Scott Marlow wrote:
> I was just thinking about this related eg discussion
> http://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2011-10/message/3
>
> from last fall and wonder i
Yes, but I wonder if we could squash down what we require to what
http://docs.oracle.com/javaee/5/api/javax/transaction/TransactionSynchronizationRegistry.html
offers.
We aren't the only persistence provider still using the Transaction
Manager directly either. I still like my original proposa
On Mar 14, 2012, at 7:52 PM, Scott Marlow wrote:
> On 03/14/2012 02:13 PM, Manik Surtani wrote:
>>
>> On 6 Mar 2012, at 14:45, Scott Marlow wrote:
>>
- Medium term:
Have a way to pass in marshalling configurations per cache manager and
per-cache (or an abstraction of
Am 16.03.2012 15:08 schrieb "Emmanuel Bernard" :
>
>
> On 16 mars 2012, at 14:17, Hardy Ferentschik wrote:
>
> > We can also try to get a HV 4.3 out asap just focusing on what's really
required. Once it is out we start with HV 5 directly.
>
> I'm for that option personally.
>
+1
That's also my pr
Well we could with some caveats.
1) If using a TSR-backed JtaPlatform no features leveraging
suspend/resume would be available; this includes (limited to?)
org.hibernate.engine.transaction.internal.jta.JtaIsolationDelegate
2) Infinispan has its notion of a "TransactionManagerLookup", and
hibe
I lean towards the proper fix as I think in its current state the
connection() and transactionContext() are not usable at all (especially
with the connection leaks). In a perfect world it would have been
caught prior to 4 release but that horse has left the barn.
The SPIs like you said are new to
> We could get away with them sharing a JdbcCoordinator as well, but that
> opens up (slight) potential concurrency issues if the 2 sessions are
> used concurrently.
The question really is about the use cases. Are connections supposed to be used
concurrently anyway?
I think they are usually
17 matches
Mail list logo
