Some related jiras (all fixed on 4.0 only):
HHH-6543 - JBoss AS7 transaction manager jndi lookup is wrong.
HHH-6564 - JBoss AS6 and earlier transaction manager jndi lookup is wrong.
On 08/22/2011 05:31 PM, Sanne Grinovero wrote:
> Hi all,
> I've just found this forum post mentioning the need fo
Hi all,
I've just found this forum post mentioning the need for a new lookup
strategy in AS7:
https://forum.hibernate.org/viewtopic.php?f=1&t=1012256
Should we add such a TransactionManagerLookup in next release of Hibernate core?
Sanne
___
hibernate-de
Hi,
I was the poster on the forum that triggered this conversation. Sanne
suggested I jump onto the dev mailing list for this and future suggestions, so
here I am. I'm a developer in the San Francisco bay area. I've been using
hibernate search for about a year on a project I've been working
We forgot to log the IRC meeting today. We did not really have a meeting
as such, but we briefly
discussed the database testing matrix (a way to test against multiple
databases using our gradle build).
If you are interested read on:
stliu: hardy, and for the matrix testing, i'm planning separ
On Fri, 19 Aug 2011 18:50:34 +0200, Emmanuel Bernard
wrote:
> There are unforeseen consequences to making Avro an optional dependency.
> By doing that, I must make the SerializerProvider build process lazy or
> tolerant at Runtime if Avro is not here.
> The problem with this approach is that
On Mon, 22 Aug 2011 14:26:35 +0200, Emmanuel Bernard
wrote:
>
> On 22 août 2011, at 14:07, Hardy Ferentschik wrote:
>
>> Not sure if I like the surrogate Document idea. Maybe we can get rid of
>> exposing any type
>> of "Document". The bridge could just return a Field(able).
>
> You can't do th
On 22 août 2011, at 14:07, Hardy Ferentschik wrote:
> Not sure if I like the surrogate Document idea. Maybe we can get rid of
> exposing any type
> of "Document". The bridge could just return a Field(able).
You can't do that. At least you need a (conceptual) Set.
__
On Fri, 19 Aug 2011 18:50:34 +0200, Emmanuel Bernard
wrote:
> There are unforeseen consequences to making Avro an optional dependency.
> By doing that, I must make the SerializerProvider build process lazy or
> tolerant at Runtime if Avro is not here.
> The problem with this approach is that
On Mon, 22 Aug 2011 13:20:43 +0200, Sanne Grinovero
wrote:
> 2011/8/22 Emmanuel Bernard :
>> That's an interesting idea.
>> It has some limitations like the inability to cover class level bridges
>> but that might not be too bad.
>
> Right. I think we should support entities having class leve
I will not be able to make the meeting today
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On Mon, 22 Aug 2011 12:58:00 +0200, Sanne Grinovero
wrote:
> 2011/8/19 Hardy Ferentschik :
>> Hi,
>>
>> I am not sure I understand the suggested path parameter. Taking the
>> example from the forum:
>>
>>
>> class A{
>>@IndexEmbedded(
>>paths={"d.one", "d.two"}
>> )
>>privat
2011/8/22 Emmanuel Bernard :
> That's an interesting idea.
> It has some limitations like the inability to cover class level bridges but
> that might not be too bad.
Right. I think we should support entities having class level bridges
as @IndexedEmbedded, by prefixing whatever they want to add to
2011/8/19 Hardy Ferentschik :
> Hi,
>
> I am not sure I understand the suggested path parameter. Taking the
> example from the forum:
>
>
> class A{
> @IndexEmbedded(
> paths={"d.one", "d.two"}
> )
> private C see;
> }
>
> class B{
> @IndexEmbedded(
> paths={"foo", "d.two
That's an interesting idea.
It has some limitations like the inability to cover class level bridges but
that might not be too bad.
On 19 août 2011, at 11:07, Sanne Grinovero wrote:
> Hi all,
> I just noticed this proposal on the forum:
> https://forum.hibernate.org/viewtopic.php?f=9&t=1012303
14 matches
Mail list logo