From gunnar at hibernate.org  Wed Oct  1 03:54:19 2014
From: gunnar at hibernate.org (Gunnar Morling)
Date: Wed, 1 Oct 2014 09:54:19 +0200
Subject: [hibernate-dev] MongoDB object id support and restructured public
 API - Hibernate OGM 4.1.0.Beta7 is out
Message-ID: <CADGJaX-6Uqwyj_p3aL1_zzn99P8-GtUcUFKM4OTD=tF32-fkmw@mail.gmail.com>

Hi,

It?s my great pleasure to announce the release of Hibernate OGM 4.1.0.Beta7!

The release brings support for MongoDB?s object id, a clarification of what
are our public API/SPI packages as well as several bugfixes and many other
improvements. Check out the announcement post [1] for all the details.

--Gunnar

[1]
http://in.relation.to/Bloggers/MongoDBObjectIdSupportAndRestructuredPublicAPIHibernateOGM410Beta7IsOut

From ericjvandervelden at gmail.com  Fri Oct  3 11:00:11 2014
From: ericjvandervelden at gmail.com (Eric J. Van der Velden)
Date: Fri, 3 Oct 2014 17:00:11 +0200
Subject: [hibernate-dev] dehydrate knows acout the Hibernate mapping,
	disassemble does not.
Message-ID: <CAFxAhE81Qt_5Cr5giJrS7y7vkOnCieLhudbY_vo3QL3-SjVNGg@mail.gmail.com>

Hello,

I have to correct my code because I work with a second level cache in the
following case (1-N bidirectional).

Suppose we have a Container class type, with a Set<Item>, and an Item class
type. In the Hibernate mapping we make the Set non-inverse.

For persistence of the Item instances we only have to add them to the
Container instance's Set, and I do not have to set the Container reference
in the Item instance.

When an Item is inserted in the database table, the
Item-persister.dehydrate method skips the Container reference in the Item
instance, and takes the Long which is there because of
the  BackrefPropertyAccessor$BackrefGetter.getForInsert() method. This will
be the foreign key in the row.

The Item-persister.getPropertyInsertability()=[true,true,false,true] for
example, and the method  Item-persister.dehydrate knows about it: The false
means: skip the Container reference in the Item instance, and the llast
true means: take this number (instead).

My question is: Why does the Item-persister.disassemble not take into
account the Hibernate mapping? Because it does not, I have to make a
correction in my code to set the Container reference in the Item instances,
only for the second level cache.

Thanks.

From sanne at hibernate.org  Mon Oct  6 08:26:23 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Mon, 6 Oct 2014 13:26:23 +0100
Subject: [hibernate-dev] [Search] Internship next year
In-Reply-To: <CALt0+o8HnsVuVYTFN7aeRq7S4YRsJzdU-FuJKV7arriqidUwdg@mail.gmail.com>
References: <CALt0+o8HnsVuVYTFN7aeRq7S4YRsJzdU-FuJKV7arriqidUwdg@mail.gmail.com>
Message-ID: <CAFm4XO09iyC3BM4b+TowTfBv8KiZ+HWYyXRVpHu_f14O25HxnQ@mail.gmail.com>

Hi Guillaume,
[sorry I only saw this email now - cleaning up a mess]

That sounds great, and if you find one (or more) don't hesitate to get
our help. Unfortunately I don't know people in that area so I don't
think I can help finding one, but let me know if we can help with
mentions on twitter or blogs. Maybe Emmanuel could mention it on its
french radio show?

During summer time we also often get sponsored by Google via the
google summer of code; this year sadly I didn't ask for a Search
student as we didn't think to have appropriate time to mentor one, but
if you are interested in the mentor role I might be able to get you
that for next summer.

Cheers,
Sanne


On 21 August 2014 20:26, Guillaume Smet <guillaume.smet at gmail.com> wrote:
> Hi,
>
> Just a heads up: I'm going to propose an internship this year (scholar
> year more precisely) on Hibernate Search contribution.
>
> I'm not sure I'll find the good intern for this but that's the plan.
> The internship season usually starts in Feb/March in France so it's
> for early next year.
>
> The internship is located in Lyon, France and if you happen to meet a
> good student interested in it, I'll be glad to meet him.
>
> I usually am interested in final year student of French "Grandes
> Ecoles" as we name it here but brilliant persons in general are
> welcome :).
>
> I have a couple of subjects in mind (like finishing the work I started
> on plain text search) but I'm sure we'll be able to find good ideas to
> keep a person busy during several months!
>
> --
> Guillaume
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

From sanne at hibernate.org  Mon Oct  6 13:27:40 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Mon, 6 Oct 2014 18:27:40 +0100
Subject: [hibernate-dev] Signing up for JIRA
In-Reply-To: <CAFm4XO3p+T86LRWbcpjiAa7vHA1eXXmWB+oa=bRQHv3nJQuZfQ@mail.gmail.com>
References: <CADGJaX-RH4=nJ05Rd1UWEz0hfXO=q9x=q5LP6cP3NbfBXsq0kQ@mail.gmail.com>
	<CAFdSV9t=_rL2T_pFK48nWOnbu++xcDLJxgWQTUcNh-6itcA5qA@mail.gmail.com>
	<CAFdSV9uJN2LFEHuOub2aokP+r-2cm5aUA5zUD3ZZK1zo1fT8Lw@mail.gmail.com>
	<CADGJaX8TyXto4E-ys=ToVuu1ZAzM0RNnZqu=kGxC6Zk6PFyfNQ@mail.gmail.com>
	<CAFm4XO3p+T86LRWbcpjiAa7vHA1eXXmWB+oa=bRQHv3nJQuZfQ@mail.gmail.com>
Message-ID: <CAFm4XO1zZgQaPS+3qDPjNManL42oJYu7rXLA6AKAXTLutYkP+w@mail.gmail.com>

Hi all,
was there any improvement made on the JIRA setup? Today I'm told on
the forums that people can create a new account but aren't allowed to
create issues.

Sanne

On 17 June 2014 13:54, Sanne Grinovero <sanne at hibernate.org> wrote:
> On 11 June 2014 17:56, Gunnar Morling <gunnar at hibernate.org> wrote:
>> Ah, thanks for the clarification, Steve.
>>
>> "CAPTCHA control for the public signup" sounds like what we should have IMO.
>
> That's not stopping the bad guys on the forums.
> But the ones we use are extremely hard, so I guess it prevents
> well-intentioned people to create an account.
>
> What we want is openId connected to a different service; for example
> GitHub, and StackOverflow.. and if you don't have those and a
> reasonable score on SO, you're not welcome on JIRA :)

From hardy at hibernate.org  Mon Oct  6 14:00:33 2014
From: hardy at hibernate.org (Hardy Ferentschik)
Date: Mon, 6 Oct 2014 20:00:33 +0200
Subject: [hibernate-dev] Signing up for JIRA
In-Reply-To: <CAFm4XO1zZgQaPS+3qDPjNManL42oJYu7rXLA6AKAXTLutYkP+w@mail.gmail.com>
References: <CADGJaX-RH4=nJ05Rd1UWEz0hfXO=q9x=q5LP6cP3NbfBXsq0kQ@mail.gmail.com>
	<CAFdSV9t=_rL2T_pFK48nWOnbu++xcDLJxgWQTUcNh-6itcA5qA@mail.gmail.com>
	<CAFdSV9uJN2LFEHuOub2aokP+r-2cm5aUA5zUD3ZZK1zo1fT8Lw@mail.gmail.com>
	<CADGJaX8TyXto4E-ys=ToVuu1ZAzM0RNnZqu=kGxC6Zk6PFyfNQ@mail.gmail.com>
	<CAFm4XO3p+T86LRWbcpjiAa7vHA1eXXmWB+oa=bRQHv3nJQuZfQ@mail.gmail.com>
	<CAFm4XO1zZgQaPS+3qDPjNManL42oJYu7rXLA6AKAXTLutYkP+w@mail.gmail.com>
Message-ID: <20141006180033.GA24797@Sarmakand-2.local>

On Mon, Oct 06, 2014 at 06:27:40PM +0100, Sanne Grinovero wrote:

> was there any improvement made on the JIRA setup? Today I'm told on
> the forums that people can create a new account but aren't allowed to
> create issues.

I am not sure. I also had recently a case where someone said, he would not be
able to create an account/issue. By the time I was digging a bit deeper into it,
the guy had created an account and actually logged an issue. For all I can tell
it works now. Not sure where the reported "problems" are coming from.

-=Hardy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 496 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hibernate-dev/attachments/20141006/ee9c0027/attachment.bin 

From sanne at hibernate.org  Tue Oct  7 07:01:30 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Tue, 7 Oct 2014 12:01:30 +0100
Subject: [hibernate-dev] Signing up for JIRA
In-Reply-To: <20141006180033.GA24797@Sarmakand-2.local>
References: <CADGJaX-RH4=nJ05Rd1UWEz0hfXO=q9x=q5LP6cP3NbfBXsq0kQ@mail.gmail.com>
	<CAFdSV9t=_rL2T_pFK48nWOnbu++xcDLJxgWQTUcNh-6itcA5qA@mail.gmail.com>
	<CAFdSV9uJN2LFEHuOub2aokP+r-2cm5aUA5zUD3ZZK1zo1fT8Lw@mail.gmail.com>
	<CADGJaX8TyXto4E-ys=ToVuu1ZAzM0RNnZqu=kGxC6Zk6PFyfNQ@mail.gmail.com>
	<CAFm4XO3p+T86LRWbcpjiAa7vHA1eXXmWB+oa=bRQHv3nJQuZfQ@mail.gmail.com>
	<CAFm4XO1zZgQaPS+3qDPjNManL42oJYu7rXLA6AKAXTLutYkP+w@mail.gmail.com>
	<20141006180033.GA24797@Sarmakand-2.local>
Message-ID: <CAFm4XO0bkkOD=qM8aVd_kkEqH-5zps-kPNyzCopRWgaVn6yWKA@mail.gmail.com>

Looks like he tried again today, and now he could create the issue.

On 6 October 2014 19:00, Hardy Ferentschik <hardy at hibernate.org> wrote:
> On Mon, Oct 06, 2014 at 06:27:40PM +0100, Sanne Grinovero wrote:
>
>> was there any improvement made on the JIRA setup? Today I'm told on
>> the forums that people can create a new account but aren't allowed to
>> create issues.
>
> I am not sure. I also had recently a case where someone said, he would not be
> able to create an account/issue. By the time I was digging a bit deeper into it,
> the guy had created an account and actually logged an issue. For all I can tell
> it works now. Not sure where the reported "problems" are coming from.
>
> -=Hardy
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

From gunnar at hibernate.org  Tue Oct  7 07:23:14 2014
From: gunnar at hibernate.org (Gunnar Morling)
Date: Tue, 7 Oct 2014 13:23:14 +0200
Subject: [hibernate-dev] Signing up for JIRA
In-Reply-To: <CAFm4XO0bkkOD=qM8aVd_kkEqH-5zps-kPNyzCopRWgaVn6yWKA@mail.gmail.com>
References: <CADGJaX-RH4=nJ05Rd1UWEz0hfXO=q9x=q5LP6cP3NbfBXsq0kQ@mail.gmail.com>
	<CAFdSV9t=_rL2T_pFK48nWOnbu++xcDLJxgWQTUcNh-6itcA5qA@mail.gmail.com>
	<CAFdSV9uJN2LFEHuOub2aokP+r-2cm5aUA5zUD3ZZK1zo1fT8Lw@mail.gmail.com>
	<CADGJaX8TyXto4E-ys=ToVuu1ZAzM0RNnZqu=kGxC6Zk6PFyfNQ@mail.gmail.com>
	<CAFm4XO3p+T86LRWbcpjiAa7vHA1eXXmWB+oa=bRQHv3nJQuZfQ@mail.gmail.com>
	<CAFm4XO1zZgQaPS+3qDPjNManL42oJYu7rXLA6AKAXTLutYkP+w@mail.gmail.com>
	<20141006180033.GA24797@Sarmakand-2.local>
	<CAFm4XO0bkkOD=qM8aVd_kkEqH-5zps-kPNyzCopRWgaVn6yWKA@mail.gmail.com>
Message-ID: <CADGJaX9wjY6dqFGBULu0tZ=Bv=hqk3a1syFWjv32bNF7Gxf+0A@mail.gmail.com>

It's a known issue, it may take several minutes after account creation
before the rights required for opening issues etc. have been properly
propagated.

There is a related note on the home page on hibernate.atlassian.net, though
it may be worded a bit more explicitly, specifically mentioning the issue
of right propagation (/CC Emmanuel).

--Gunnar


2014-10-07 13:01 GMT+02:00 Sanne Grinovero <sanne at hibernate.org>:

> Looks like he tried again today, and now he could create the issue.
>
> On 6 October 2014 19:00, Hardy Ferentschik <hardy at hibernate.org> wrote:
> > On Mon, Oct 06, 2014 at 06:27:40PM +0100, Sanne Grinovero wrote:
> >
> >> was there any improvement made on the JIRA setup? Today I'm told on
> >> the forums that people can create a new account but aren't allowed to
> >> create issues.
> >
> > I am not sure. I also had recently a case where someone said, he would
> not be
> > able to create an account/issue. By the time I was digging a bit deeper
> into it,
> > the guy had created an account and actually logged an issue. For all I
> can tell
> > it works now. Not sure where the reported "problems" are coming from.
> >
> > -=Hardy
> >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From sanne at hibernate.org  Tue Oct  7 08:17:11 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Tue, 7 Oct 2014 13:17:11 +0100
Subject: [hibernate-dev] Signing up for JIRA
In-Reply-To: <CADGJaX9wjY6dqFGBULu0tZ=Bv=hqk3a1syFWjv32bNF7Gxf+0A@mail.gmail.com>
References: <CADGJaX-RH4=nJ05Rd1UWEz0hfXO=q9x=q5LP6cP3NbfBXsq0kQ@mail.gmail.com>
	<CAFdSV9t=_rL2T_pFK48nWOnbu++xcDLJxgWQTUcNh-6itcA5qA@mail.gmail.com>
	<CAFdSV9uJN2LFEHuOub2aokP+r-2cm5aUA5zUD3ZZK1zo1fT8Lw@mail.gmail.com>
	<CADGJaX8TyXto4E-ys=ToVuu1ZAzM0RNnZqu=kGxC6Zk6PFyfNQ@mail.gmail.com>
	<CAFm4XO3p+T86LRWbcpjiAa7vHA1eXXmWB+oa=bRQHv3nJQuZfQ@mail.gmail.com>
	<CAFm4XO1zZgQaPS+3qDPjNManL42oJYu7rXLA6AKAXTLutYkP+w@mail.gmail.com>
	<20141006180033.GA24797@Sarmakand-2.local>
	<CAFm4XO0bkkOD=qM8aVd_kkEqH-5zps-kPNyzCopRWgaVn6yWKA@mail.gmail.com>
	<CADGJaX9wjY6dqFGBULu0tZ=Bv=hqk3a1syFWjv32bNF7Gxf+0A@mail.gmail.com>
Message-ID: <CAFm4XO0DRDqFdz8_a+LiFtwwEJHKmY6nrqS9XbNuxE_EjvtQ9Q@mail.gmail.com>

Thanks Gunnar!

right sorry I totally forgot about that. I've added a banner which
will float on top of all pages, hopefully that will be more visible.

Sanne

On 7 October 2014 12:23, Gunnar Morling <gunnar at hibernate.org> wrote:
> It's a known issue, it may take several minutes after account creation
> before the rights required for opening issues etc. have been properly
> propagated.
>
> There is a related note on the home page on hibernate.atlassian.net, though
> it may be worded a bit more explicitly, specifically mentioning the issue of
> right propagation (/CC Emmanuel).
>
> --Gunnar
>
>
> 2014-10-07 13:01 GMT+02:00 Sanne Grinovero <sanne at hibernate.org>:
>>
>> Looks like he tried again today, and now he could create the issue.
>>
>> On 6 October 2014 19:00, Hardy Ferentschik <hardy at hibernate.org> wrote:
>> > On Mon, Oct 06, 2014 at 06:27:40PM +0100, Sanne Grinovero wrote:
>> >
>> >> was there any improvement made on the JIRA setup? Today I'm told on
>> >> the forums that people can create a new account but aren't allowed to
>> >> create issues.
>> >
>> > I am not sure. I also had recently a case where someone said, he would
>> > not be
>> > able to create an account/issue. By the time I was digging a bit deeper
>> > into it,
>> > the guy had created an account and actually logged an issue. For all I
>> > can tell
>> > it works now. Not sure where the reported "problems" are coming from.
>> >
>> > -=Hardy
>> >
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>

From sanne at hibernate.org  Tue Oct  7 13:26:45 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Tue, 7 Oct 2014 18:26:45 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
Message-ID: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>

Hi all,
I would love to publish the documentation the way it looks like from
the asciidoc rendering (before the transformations via docbook), as it
looks like much more readable.

But I'd like to keep our style and branding rather than the default
docbook template; did someone already experiment with that? Or could
anyone volunteer please as my design skills are better avoided :-)

Cheers,
Sanne

From guillaume.scheibel at gmail.com  Tue Oct  7 14:01:56 2014
From: guillaume.scheibel at gmail.com (Guillaume SCHEIBEL)
Date: Tue, 7 Oct 2014 19:01:56 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
Message-ID: <CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>

Hey,

I've spoken with Sanne and it can be done by using the asciidoctor
stylesheet-factory.
I'll try to create a first draft. Any specific requirements other than it
should look exactly the same ?

Cheers,
Guillaume

On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org> wrote:

> Hi all,
> I would love to publish the documentation the way it looks like from
> the asciidoc rendering (before the transformations via docbook), as it
> looks like much more readable.
>
> But I'd like to keep our style and branding rather than the default
> docbook template; did someone already experiment with that? Or could
> anyone volunteer please as my design skills are better avoided :-)
>
> Cheers,
> Sanne
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From steve at hibernate.org  Tue Oct  7 14:09:25 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Tue, 7 Oct 2014 13:09:25 -0500
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
Message-ID: <CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>

IMO, the most important thing is the banners.  In terms of most everything
else we generally run into disagreements (rendering back-ticked words,
e.g.).  I guess I see 2 options:
1) Start from the simplest.  Just account for the top banner (the images
mainly).  From there work on the individual pieces as (if) they come up.
2) Start with the assumption of making the asciidoc(tor) output look
*exactly* the same as the docbook output.

Personally I prefer #1 for quite a few reasons


On Tue, Oct 7, 2014 at 1:01 PM, Guillaume SCHEIBEL <
guillaume.scheibel at gmail.com> wrote:

> Hey,
>
> I've spoken with Sanne and it can be done by using the asciidoctor
> stylesheet-factory.
> I'll try to create a first draft. Any specific requirements other than it
> should look exactly the same ?
>
> Cheers,
> Guillaume
>
> On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org> wrote:
>
> > Hi all,
> > I would love to publish the documentation the way it looks like from
> > the asciidoc rendering (before the transformations via docbook), as it
> > looks like much more readable.
> >
> > But I'd like to keep our style and branding rather than the default
> > docbook template; did someone already experiment with that? Or could
> > anyone volunteer please as my design skills are better avoided :-)
> >
> > Cheers,
> > Sanne
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From guillaume.scheibel at gmail.com  Tue Oct  7 14:14:27 2014
From: guillaume.scheibel at gmail.com (Guillaume SCHEIBEL)
Date: Tue, 7 Oct 2014 19:14:27 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
Message-ID: <CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>

I agree with you Steve #1 is the best option.
Which asciidoctor theme do you think is the best to use as a "model" for
the Hibernate Style sheet (http://themes.asciidoctor.org/preview/) ?

On 7 October 2014 19:09, Steve Ebersole <steve at hibernate.org> wrote:

> IMO, the most important thing is the banners.  In terms of most everything
> else we generally run into disagreements (rendering back-ticked words,
> e.g.).  I guess I see 2 options:
> 1) Start from the simplest.  Just account for the top banner (the images
> mainly).  From there work on the individual pieces as (if) they come up.
> 2) Start with the assumption of making the asciidoc(tor) output look
> *exactly* the same as the docbook output.
>
> Personally I prefer #1 for quite a few reasons
>
>
> On Tue, Oct 7, 2014 at 1:01 PM, Guillaume SCHEIBEL <
> guillaume.scheibel at gmail.com> wrote:
>
>> Hey,
>>
>> I've spoken with Sanne and it can be done by using the asciidoctor
>> stylesheet-factory.
>> I'll try to create a first draft. Any specific requirements other than it
>> should look exactly the same ?
>>
>> Cheers,
>> Guillaume
>>
>> On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org> wrote:
>>
>> > Hi all,
>> > I would love to publish the documentation the way it looks like from
>> > the asciidoc rendering (before the transformations via docbook), as it
>> > looks like much more readable.
>> >
>> > But I'd like to keep our style and branding rather than the default
>> > docbook template; did someone already experiment with that? Or could
>> > anyone volunteer please as my design skills are better avoided :-)
>> >
>> > Cheers,
>> > Sanne
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> >
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
>

From guillaume.scheibel at gmail.com  Tue Oct  7 14:15:27 2014
From: guillaume.scheibel at gmail.com (Guillaume SCHEIBEL)
Date: Tue, 7 Oct 2014 19:15:27 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
	<CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
Message-ID: <CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>

I would go with Foundation but I'd like to have your opinion on that guys

On 7 October 2014 19:14, Guillaume SCHEIBEL <guillaume.scheibel at gmail.com>
wrote:

> I agree with you Steve #1 is the best option.
> Which asciidoctor theme do you think is the best to use as a "model" for
> the Hibernate Style sheet (http://themes.asciidoctor.org/preview/) ?
>
> On 7 October 2014 19:09, Steve Ebersole <steve at hibernate.org> wrote:
>
>> IMO, the most important thing is the banners.  In terms of most
>> everything else we generally run into disagreements (rendering back-ticked
>> words, e.g.).  I guess I see 2 options:
>> 1) Start from the simplest.  Just account for the top banner (the images
>> mainly).  From there work on the individual pieces as (if) they come up.
>> 2) Start with the assumption of making the asciidoc(tor) output look
>> *exactly* the same as the docbook output.
>>
>> Personally I prefer #1 for quite a few reasons
>>
>>
>> On Tue, Oct 7, 2014 at 1:01 PM, Guillaume SCHEIBEL <
>> guillaume.scheibel at gmail.com> wrote:
>>
>>> Hey,
>>>
>>> I've spoken with Sanne and it can be done by using the asciidoctor
>>> stylesheet-factory.
>>> I'll try to create a first draft. Any specific requirements other than it
>>> should look exactly the same ?
>>>
>>> Cheers,
>>> Guillaume
>>>
>>> On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org> wrote:
>>>
>>> > Hi all,
>>> > I would love to publish the documentation the way it looks like from
>>> > the asciidoc rendering (before the transformations via docbook), as it
>>> > looks like much more readable.
>>> >
>>> > But I'd like to keep our style and branding rather than the default
>>> > docbook template; did someone already experiment with that? Or could
>>> > anyone volunteer please as my design skills are better avoided :-)
>>> >
>>> > Cheers,
>>> > Sanne
>>> > _______________________________________________
>>> > hibernate-dev mailing list
>>> > hibernate-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>> >
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>
>>
>

From sanne at hibernate.org  Tue Oct  7 14:33:15 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Tue, 7 Oct 2014 19:33:15 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
	<CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
	<CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>
Message-ID: <CAFm4XO0T5CVQ9JqoP8n2ySRhSOX3BjQaP+O_cLvT7xfG78N1QA@mail.gmail.com>

I think I like the "asciidoctor" theme the best, particularly the
fonts, but I guess it's quite irrelevant considering the aim for
Steve's point 2#.

On 7 October 2014 19:15, Guillaume SCHEIBEL
<guillaume.scheibel at gmail.com> wrote:
> I would go with Foundation but I'd like to have your opinion on that guys
>
> On 7 October 2014 19:14, Guillaume SCHEIBEL <guillaume.scheibel at gmail.com>
> wrote:
>>
>> I agree with you Steve #1 is the best option.
>> Which asciidoctor theme do you think is the best to use as a "model" for
>> the Hibernate Style sheet (http://themes.asciidoctor.org/preview/) ?
>>
>> On 7 October 2014 19:09, Steve Ebersole <steve at hibernate.org> wrote:
>>>
>>> IMO, the most important thing is the banners.  In terms of most
>>> everything else we generally run into disagreements (rendering back-ticked
>>> words, e.g.).  I guess I see 2 options:
>>> 1) Start from the simplest.  Just account for the top banner (the images
>>> mainly).  From there work on the individual pieces as (if) they come up.
>>> 2) Start with the assumption of making the asciidoc(tor) output look
>>> *exactly* the same as the docbook output.
>>>
>>> Personally I prefer #1 for quite a few reasons
>>>
>>>
>>> On Tue, Oct 7, 2014 at 1:01 PM, Guillaume SCHEIBEL
>>> <guillaume.scheibel at gmail.com> wrote:
>>>>
>>>> Hey,
>>>>
>>>> I've spoken with Sanne and it can be done by using the asciidoctor
>>>> stylesheet-factory.
>>>> I'll try to create a first draft. Any specific requirements other than
>>>> it
>>>> should look exactly the same ?
>>>>
>>>> Cheers,
>>>> Guillaume
>>>>
>>>> On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org> wrote:
>>>>
>>>> > Hi all,
>>>> > I would love to publish the documentation the way it looks like from
>>>> > the asciidoc rendering (before the transformations via docbook), as it
>>>> > looks like much more readable.
>>>> >
>>>> > But I'd like to keep our style and branding rather than the default
>>>> > docbook template; did someone already experiment with that? Or could
>>>> > anyone volunteer please as my design skills are better avoided :-)
>>>> >
>>>> > Cheers,
>>>> > Sanne
>>>> > _______________________________________________
>>>> > hibernate-dev mailing list
>>>> > hibernate-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>> >
>>>> _______________________________________________
>>>> hibernate-dev mailing list
>>>> hibernate-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>>
>>
>

From steve at hibernate.org  Tue Oct  7 14:37:49 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Tue, 7 Oct 2014 13:37:49 -0500
Subject: [hibernate-dev] dehydrate knows acout the Hibernate mapping,
 disassemble does not.
In-Reply-To: <CAFxAhE81Qt_5Cr5giJrS7y7vkOnCieLhudbY_vo3QL3-SjVNGg@mail.gmail.com>
References: <CAFxAhE81Qt_5Cr5giJrS7y7vkOnCieLhudbY_vo3QL3-SjVNGg@mail.gmail.com>
Message-ID: <CAFdSV9vRe9g5esrDan7jqEVN1RS9NefEb9ZWOHuobjarE1fWhw@mail.gmail.com>

You are misusing the software.  It is fully expected that you manage both
sides of a bi-directional association in your code.  The fact that it
happens to work in one isolated case, I think, led you to believe that is
supported.  But it is not.

On Fri, Oct 3, 2014 at 10:00 AM, Eric J. Van der Velden <
ericjvandervelden at gmail.com> wrote:

> Hello,
>
> I have to correct my code because I work with a second level cache in the
> following case (1-N bidirectional).
>
> Suppose we have a Container class type, with a Set<Item>, and an Item class
> type. In the Hibernate mapping we make the Set non-inverse.
>
> For persistence of the Item instances we only have to add them to the
> Container instance's Set, and I do not have to set the Container reference
> in the Item instance.
>
> When an Item is inserted in the database table, the
> Item-persister.dehydrate method skips the Container reference in the Item
> instance, and takes the Long which is there because of
> the  BackrefPropertyAccessor$BackrefGetter.getForInsert() method. This will
> be the foreign key in the row.
>
> The Item-persister.getPropertyInsertability()=[true,true,false,true] for
> example, and the method  Item-persister.dehydrate knows about it: The false
> means: skip the Container reference in the Item instance, and the llast
> true means: take this number (instead).
>
> My question is: Why does the Item-persister.disassemble not take into
> account the Hibernate mapping? Because it does not, I have to make a
> correction in my code to set the Container reference in the Item instances,
> only for the second level cache.
>
> Thanks.
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From guillaume.scheibel at gmail.com  Wed Oct  8 14:09:08 2014
From: guillaume.scheibel at gmail.com (Guillaume SCHEIBEL)
Date: Wed, 8 Oct 2014 19:09:08 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAFm4XO0T5CVQ9JqoP8n2ySRhSOX3BjQaP+O_cLvT7xfG78N1QA@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
	<CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
	<CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>
	<CAFm4XO0T5CVQ9JqoP8n2ySRhSOX3BjQaP+O_cLvT7xfG78N1QA@mail.gmail.com>
Message-ID: <CAJoPwXcSvi__1ca_h2f7oUN1f064t7wQfD8b+AKTpo3XBepApA@mail.gmail.com>

Hi there,

Here [1] is the first draft of the HSearch documentation.
I've just worked on the background image (the gradient at the top) and the
title / banner.

Let me know your thoughts.


BTW, to generate the CSS file and build the documentation (HTML5 single
page) it takes:

real 0m1.584s
user 0m1.073s
sys 0m0.220s

So pretty fast ins't it.

Cheers
Guillaume

[1]
https://www.dropbox.com/s/tzp90mvtbpuirhg/hibernate%20search%20doc.zip?dl=0

On 7 October 2014 19:33, Sanne Grinovero <sanne at hibernate.org> wrote:

> I think I like the "asciidoctor" theme the best, particularly the
> fonts, but I guess it's quite irrelevant considering the aim for
> Steve's point 2#.
>
> On 7 October 2014 19:15, Guillaume SCHEIBEL
> <guillaume.scheibel at gmail.com> wrote:
> > I would go with Foundation but I'd like to have your opinion on that guys
> >
> > On 7 October 2014 19:14, Guillaume SCHEIBEL <
> guillaume.scheibel at gmail.com>
> > wrote:
> >>
> >> I agree with you Steve #1 is the best option.
> >> Which asciidoctor theme do you think is the best to use as a "model" for
> >> the Hibernate Style sheet (http://themes.asciidoctor.org/preview/) ?
> >>
> >> On 7 October 2014 19:09, Steve Ebersole <steve at hibernate.org> wrote:
> >>>
> >>> IMO, the most important thing is the banners.  In terms of most
> >>> everything else we generally run into disagreements (rendering
> back-ticked
> >>> words, e.g.).  I guess I see 2 options:
> >>> 1) Start from the simplest.  Just account for the top banner (the
> images
> >>> mainly).  From there work on the individual pieces as (if) they come
> up.
> >>> 2) Start with the assumption of making the asciidoc(tor) output look
> >>> *exactly* the same as the docbook output.
> >>>
> >>> Personally I prefer #1 for quite a few reasons
> >>>
> >>>
> >>> On Tue, Oct 7, 2014 at 1:01 PM, Guillaume SCHEIBEL
> >>> <guillaume.scheibel at gmail.com> wrote:
> >>>>
> >>>> Hey,
> >>>>
> >>>> I've spoken with Sanne and it can be done by using the asciidoctor
> >>>> stylesheet-factory.
> >>>> I'll try to create a first draft. Any specific requirements other than
> >>>> it
> >>>> should look exactly the same ?
> >>>>
> >>>> Cheers,
> >>>> Guillaume
> >>>>
> >>>> On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org> wrote:
> >>>>
> >>>> > Hi all,
> >>>> > I would love to publish the documentation the way it looks like from
> >>>> > the asciidoc rendering (before the transformations via docbook), as
> it
> >>>> > looks like much more readable.
> >>>> >
> >>>> > But I'd like to keep our style and branding rather than the default
> >>>> > docbook template; did someone already experiment with that? Or could
> >>>> > anyone volunteer please as my design skills are better avoided :-)
> >>>> >
> >>>> > Cheers,
> >>>> > Sanne
> >>>> > _______________________________________________
> >>>> > hibernate-dev mailing list
> >>>> > hibernate-dev at lists.jboss.org
> >>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>>> >
> >>>> _______________________________________________
> >>>> hibernate-dev mailing list
> >>>> hibernate-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>>
> >>>
> >>
> >
>

From sanne at hibernate.org  Thu Oct  9 07:01:22 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Thu, 9 Oct 2014 12:01:22 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAJoPwXcSvi__1ca_h2f7oUN1f064t7wQfD8b+AKTpo3XBepApA@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
	<CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
	<CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>
	<CAFm4XO0T5CVQ9JqoP8n2ySRhSOX3BjQaP+O_cLvT7xfG78N1QA@mail.gmail.com>
	<CAJoPwXcSvi__1ca_h2f7oUN1f064t7wQfD8b+AKTpo3XBepApA@mail.gmail.com>
Message-ID: <CAFm4XO2L+ypc7Juj5KO-z2x8_QY5FVWP7Y=cn1yAfq1iXtfQ9g@mail.gmail.com>

hi Guillaume, great progress!
In Google's Chrome it looks almost ok, not quite as the headers we
have on the docs published at [1] but I guess you can easily fix that.
On Firefox, it looks odd. There is something being repeated all over
along the whole document.. I hope you can see the same, or let me know
if I should send you a screenshot?

On the speed: I'm very interested what command you use as that would
be helpful when writing docs; but I see it didn't apply replacements
such as {hibernateVersion} and similar. Is that a tradeoff we have to
pay for quick previews, or can you trick it somehow?

thanks a lot for your help,
Sanne


On 8 October 2014 19:09, Guillaume SCHEIBEL
<guillaume.scheibel at gmail.com> wrote:
> Hi there,
>
> Here [1] is the first draft of the HSearch documentation.
> I've just worked on the background image (the gradient at the top) and the
> title / banner.
>
> Let me know your thoughts.
>
>
> BTW, to generate the CSS file and build the documentation (HTML5 single
> page) it takes:
>
> real 0m1.584s
> user 0m1.073s
> sys 0m0.220s
>
> So pretty fast ins't it.
>
> Cheers
> Guillaume
>
> [1]
> https://www.dropbox.com/s/tzp90mvtbpuirhg/hibernate%20search%20doc.zip?dl=0
>
> On 7 October 2014 19:33, Sanne Grinovero <sanne at hibernate.org> wrote:
>>
>> I think I like the "asciidoctor" theme the best, particularly the
>> fonts, but I guess it's quite irrelevant considering the aim for
>> Steve's point 2#.
>>
>> On 7 October 2014 19:15, Guillaume SCHEIBEL
>> <guillaume.scheibel at gmail.com> wrote:
>> > I would go with Foundation but I'd like to have your opinion on that
>> > guys
>> >
>> > On 7 October 2014 19:14, Guillaume SCHEIBEL
>> > <guillaume.scheibel at gmail.com>
>> > wrote:
>> >>
>> >> I agree with you Steve #1 is the best option.
>> >> Which asciidoctor theme do you think is the best to use as a "model"
>> >> for
>> >> the Hibernate Style sheet (http://themes.asciidoctor.org/preview/) ?
>> >>
>> >> On 7 October 2014 19:09, Steve Ebersole <steve at hibernate.org> wrote:
>> >>>
>> >>> IMO, the most important thing is the banners.  In terms of most
>> >>> everything else we generally run into disagreements (rendering
>> >>> back-ticked
>> >>> words, e.g.).  I guess I see 2 options:
>> >>> 1) Start from the simplest.  Just account for the top banner (the
>> >>> images
>> >>> mainly).  From there work on the individual pieces as (if) they come
>> >>> up.
>> >>> 2) Start with the assumption of making the asciidoc(tor) output look
>> >>> *exactly* the same as the docbook output.
>> >>>
>> >>> Personally I prefer #1 for quite a few reasons
>> >>>
>> >>>
>> >>> On Tue, Oct 7, 2014 at 1:01 PM, Guillaume SCHEIBEL
>> >>> <guillaume.scheibel at gmail.com> wrote:
>> >>>>
>> >>>> Hey,
>> >>>>
>> >>>> I've spoken with Sanne and it can be done by using the asciidoctor
>> >>>> stylesheet-factory.
>> >>>> I'll try to create a first draft. Any specific requirements other
>> >>>> than
>> >>>> it
>> >>>> should look exactly the same ?
>> >>>>
>> >>>> Cheers,
>> >>>> Guillaume
>> >>>>
>> >>>> On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org> wrote:
>> >>>>
>> >>>> > Hi all,
>> >>>> > I would love to publish the documentation the way it looks like
>> >>>> > from
>> >>>> > the asciidoc rendering (before the transformations via docbook), as
>> >>>> > it
>> >>>> > looks like much more readable.
>> >>>> >
>> >>>> > But I'd like to keep our style and branding rather than the default
>> >>>> > docbook template; did someone already experiment with that? Or
>> >>>> > could
>> >>>> > anyone volunteer please as my design skills are better avoided :-)
>> >>>> >
>> >>>> > Cheers,
>> >>>> > Sanne
>> >>>> > _______________________________________________
>> >>>> > hibernate-dev mailing list
>> >>>> > hibernate-dev at lists.jboss.org
>> >>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> >>>> >
>> >>>> _______________________________________________
>> >>>> hibernate-dev mailing list
>> >>>> hibernate-dev at lists.jboss.org
>> >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> >>>
>> >>>
>> >>
>> >
>
>

From guillaume.scheibel at gmail.com  Thu Oct  9 08:04:05 2014
From: guillaume.scheibel at gmail.com (Guillaume SCHEIBEL)
Date: Thu, 9 Oct 2014 13:04:05 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAFm4XO2L+ypc7Juj5KO-z2x8_QY5FVWP7Y=cn1yAfq1iXtfQ9g@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
	<CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
	<CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>
	<CAFm4XO0T5CVQ9JqoP8n2ySRhSOX3BjQaP+O_cLvT7xfG78N1QA@mail.gmail.com>
	<CAJoPwXcSvi__1ca_h2f7oUN1f064t7wQfD8b+AKTpo3XBepApA@mail.gmail.com>
	<CAFm4XO2L+ypc7Juj5KO-z2x8_QY5FVWP7Y=cn1yAfq1iXtfQ9g@mail.gmail.com>
Message-ID: <CAJoPwXe36cKGzkQMp4dPWJXZ1G59KmDX_r9xrprOHTH_J765ng@mail.gmail.com>

Hi Sanne,

I'll have a look on firefox as well and continue to work on the header.
About the command [1], I just recompile the stylesheets, copy it and run
the asciidoctor command.
In the current build, values for placeholders like {hibernateVersion} are
coming from the pom since I neither have used the pom file nor forced a
value (using -a parameter) you can still see them.

But when you are writing the documentation you don't (most of the time)
need to have all the placeholder values and for ones you do, you can force
a value (CLI parameter or just forcing them at the beginning of the doc).

I'll try the stylesheet with asciidoctor-pdf to see how it goes.

Cheers,
Guillaume

[1] https://gist.github.com/gscheibel/840f163c9d80eeab5a81

On 9 October 2014 12:01, Sanne Grinovero <sanne at hibernate.org> wrote:

> hi Guillaume, great progress!
> In Google's Chrome it looks almost ok, not quite as the headers we
> have on the docs published at [1] but I guess you can easily fix that.
> On Firefox, it looks odd. There is something being repeated all over
> along the whole document.. I hope you can see the same, or let me know
> if I should send you a screenshot?
>
> On the speed: I'm very interested what command you use as that would
> be helpful when writing docs; but I see it didn't apply replacements
> such as {hibernateVersion} and similar. Is that a tradeoff we have to
> pay for quick previews, or can you trick it somehow?
>
> thanks a lot for your help,
> Sanne
>
>
> On 8 October 2014 19:09, Guillaume SCHEIBEL
> <guillaume.scheibel at gmail.com> wrote:
> > Hi there,
> >
> > Here [1] is the first draft of the HSearch documentation.
> > I've just worked on the background image (the gradient at the top) and
> the
> > title / banner.
> >
> > Let me know your thoughts.
> >
> >
> > BTW, to generate the CSS file and build the documentation (HTML5 single
> > page) it takes:
> >
> > real 0m1.584s
> > user 0m1.073s
> > sys 0m0.220s
> >
> > So pretty fast ins't it.
> >
> > Cheers
> > Guillaume
> >
> > [1]
> >
> https://www.dropbox.com/s/tzp90mvtbpuirhg/hibernate%20search%20doc.zip?dl=0
> >
> > On 7 October 2014 19:33, Sanne Grinovero <sanne at hibernate.org> wrote:
> >>
> >> I think I like the "asciidoctor" theme the best, particularly the
> >> fonts, but I guess it's quite irrelevant considering the aim for
> >> Steve's point 2#.
> >>
> >> On 7 October 2014 19:15, Guillaume SCHEIBEL
> >> <guillaume.scheibel at gmail.com> wrote:
> >> > I would go with Foundation but I'd like to have your opinion on that
> >> > guys
> >> >
> >> > On 7 October 2014 19:14, Guillaume SCHEIBEL
> >> > <guillaume.scheibel at gmail.com>
> >> > wrote:
> >> >>
> >> >> I agree with you Steve #1 is the best option.
> >> >> Which asciidoctor theme do you think is the best to use as a "model"
> >> >> for
> >> >> the Hibernate Style sheet (http://themes.asciidoctor.org/preview/) ?
> >> >>
> >> >> On 7 October 2014 19:09, Steve Ebersole <steve at hibernate.org> wrote:
> >> >>>
> >> >>> IMO, the most important thing is the banners.  In terms of most
> >> >>> everything else we generally run into disagreements (rendering
> >> >>> back-ticked
> >> >>> words, e.g.).  I guess I see 2 options:
> >> >>> 1) Start from the simplest.  Just account for the top banner (the
> >> >>> images
> >> >>> mainly).  From there work on the individual pieces as (if) they come
> >> >>> up.
> >> >>> 2) Start with the assumption of making the asciidoc(tor) output look
> >> >>> *exactly* the same as the docbook output.
> >> >>>
> >> >>> Personally I prefer #1 for quite a few reasons
> >> >>>
> >> >>>
> >> >>> On Tue, Oct 7, 2014 at 1:01 PM, Guillaume SCHEIBEL
> >> >>> <guillaume.scheibel at gmail.com> wrote:
> >> >>>>
> >> >>>> Hey,
> >> >>>>
> >> >>>> I've spoken with Sanne and it can be done by using the asciidoctor
> >> >>>> stylesheet-factory.
> >> >>>> I'll try to create a first draft. Any specific requirements other
> >> >>>> than
> >> >>>> it
> >> >>>> should look exactly the same ?
> >> >>>>
> >> >>>> Cheers,
> >> >>>> Guillaume
> >> >>>>
> >> >>>> On 7 October 2014 18:26, Sanne Grinovero <sanne at hibernate.org>
> wrote:
> >> >>>>
> >> >>>> > Hi all,
> >> >>>> > I would love to publish the documentation the way it looks like
> >> >>>> > from
> >> >>>> > the asciidoc rendering (before the transformations via docbook),
> as
> >> >>>> > it
> >> >>>> > looks like much more readable.
> >> >>>> >
> >> >>>> > But I'd like to keep our style and branding rather than the
> default
> >> >>>> > docbook template; did someone already experiment with that? Or
> >> >>>> > could
> >> >>>> > anyone volunteer please as my design skills are better avoided
> :-)
> >> >>>> >
> >> >>>> > Cheers,
> >> >>>> > Sanne
> >> >>>> > _______________________________________________
> >> >>>> > hibernate-dev mailing list
> >> >>>> > hibernate-dev at lists.jboss.org
> >> >>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >> >>>> >
> >> >>>> _______________________________________________
> >> >>>> hibernate-dev mailing list
> >> >>>> hibernate-dev at lists.jboss.org
> >> >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >> >>>
> >> >>>
> >> >>
> >> >
> >
> >
>

From hardy at hibernate.org  Thu Oct  9 08:11:18 2014
From: hardy at hibernate.org (Hardy Ferentschik)
Date: Thu, 9 Oct 2014 14:11:18 +0200
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <CAFm4XO2L+ypc7Juj5KO-z2x8_QY5FVWP7Y=cn1yAfq1iXtfQ9g@mail.gmail.com>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
	<CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
	<CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>
	<CAFm4XO0T5CVQ9JqoP8n2ySRhSOX3BjQaP+O_cLvT7xfG78N1QA@mail.gmail.com>
	<CAJoPwXcSvi__1ca_h2f7oUN1f064t7wQfD8b+AKTpo3XBepApA@mail.gmail.com>
	<CAFm4XO2L+ypc7Juj5KO-z2x8_QY5FVWP7Y=cn1yAfq1iXtfQ9g@mail.gmail.com>
Message-ID: <DD1303F3-EF28-4433-BD70-BE071D42EA04@hibernate.org>


On 9 Jan 2014, at 13:01, Sanne Grinovero <sanne at hibernate.org> wrote:

> hi Guillaume, great progress!
> In Google's Chrome it looks almost ok, not quite as the headers we
> have on the docs published at [1] but I guess you can easily fix that.
> On Firefox, it looks odd. There is something being repeated all over
> along the whole document.. I hope you can see the same, or let me know
> if I should send you a screenshot?

For what it's worth, I can confirm this repetition of the background Sanne
describes.

On a tangent and related to style fixes. Not sure whether other projects already use Java 8 for
building, but there are yet again changes to the javadoc doclet output leading to
badly rendered output. We have this problem with Validator's docs [1] and there is a related
design issue [2]. I am wondering whether the design team could help to make sure that the
L&F of reference and java docs are matching. That said, afaict the issue has quite low priority for
them :-(

--Hardy


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/hibernate-dev/attachments/20141009/099a4523/attachment-0001.bin 

From guillaume.scheibel at gmail.com  Thu Oct  9 08:16:36 2014
From: guillaume.scheibel at gmail.com (Guillaume SCHEIBEL)
Date: Thu, 9 Oct 2014 13:16:36 +0100
Subject: [hibernate-dev] Publishing documentation as rendered by asciidoc
In-Reply-To: <DD1303F3-EF28-4433-BD70-BE071D42EA04@hibernate.org>
References: <CAFm4XO2k_L=Ev0hXoKm55Kh8d_FVQiyqL=81ZqJocoeWwTVnZQ@mail.gmail.com>
	<CAJoPwXfXsA-O6LEOq=aE2KDAJNY2o-arGd2T3Yer1LS76DfuSw@mail.gmail.com>
	<CAFdSV9tzDJUrDYn0cgnMrYwc4fCRYrnKJ1Ms0EPwwJs=0Ci-2Q@mail.gmail.com>
	<CAJoPwXdxWAiqZXTKS2Xh-qX9PazO-E-aMOmUD8H_7CawnzLoGA@mail.gmail.com>
	<CAJoPwXeRmBq8ru4fyOoDuzhYbjVLhHfjB7NbTda+EoVh4B_FDA@mail.gmail.com>
	<CAFm4XO0T5CVQ9JqoP8n2ySRhSOX3BjQaP+O_cLvT7xfG78N1QA@mail.gmail.com>
	<CAJoPwXcSvi__1ca_h2f7oUN1f064t7wQfD8b+AKTpo3XBepApA@mail.gmail.com>
	<CAFm4XO2L+ypc7Juj5KO-z2x8_QY5FVWP7Y=cn1yAfq1iXtfQ9g@mail.gmail.com>
	<DD1303F3-EF28-4433-BD70-BE071D42EA04@hibernate.org>
Message-ID: <CAJoPwXf-bD=-DLguvcbBFD_aZ6S970OY5Oi+n1Z+87E3f40b4w@mail.gmail.com>

I confirm the issue on firefox, it mixes background declaration so the
no-repeat I set is overwritten but not the background image.


On 9 October 2014 13:11, Hardy Ferentschik <hardy at hibernate.org> wrote:

>
> On 9 Jan 2014, at 13:01, Sanne Grinovero <sanne at hibernate.org> wrote:
>
> > hi Guillaume, great progress!
> > In Google's Chrome it looks almost ok, not quite as the headers we
> > have on the docs published at [1] but I guess you can easily fix that.
> > On Firefox, it looks odd. There is something being repeated all over
> > along the whole document.. I hope you can see the same, or let me know
> > if I should send you a screenshot?
>
> For what it's worth, I can confirm this repetition of the background Sanne
> describes.
>
> On a tangent and related to style fixes. Not sure whether other projects
> already use Java 8 for
> building, but there are yet again changes to the javadoc doclet output
> leading to
> badly rendered output. We have this problem with Validator's docs [1] and
> there is a related
> design issue [2]. I am wondering whether the design team could help to
> make sure that the
> L&F of reference and java docs are matching. That said, afaict the issue
> has quite low priority for
> them :-(
>
> --Hardy
>
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From sanne at hibernate.org  Sun Oct 12 18:19:03 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Sun, 12 Oct 2014 23:19:03 +0100
Subject: [hibernate-dev] WildFly deployments: how to access the (user app)
 deployment classloader from Hibernate code?
Message-ID: <CAFm4XO2AETu3wHXu-GKr7eML=wQ6DBDG9O6sKi+bUCv+0jn+uA@mail.gmail.com>

It looks like that when Hibernate Search is being bootstrapped in a
JPA deployment on WidFly the current context classloader was
overriden.
That's expected I guess, but it's of a type which surprised me:
 - org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader

while I really need to access the deployment classloader; on WildFly
this would be a ModularClassloader having a toString of the form:
  ModuleClassLoader for Module "deployment.DeploymentName:main" from
Service Module Loader

The ClassLoaderService itself is of no use in this case as it only
exposes the same aggregate ClassLoader which is loading Hibernate
Search, while I need to get fine-grained access to the ClassLoader
which is loading the user deployment.

There is no such problem when I start the Hibernate SessionFactory
directly (not in a container): in that case the Context Classloader
matches the system one so I don't think is being set by Hibernate ORM.

If such a semantics is needed in WildFly, could we then expose the
original TCCL via an accessor on ClassLoaderService ?

Thanks,
Sanne

From steve at hibernate.org  Mon Oct 13 14:48:12 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Mon, 13 Oct 2014 13:48:12 -0500
Subject: [hibernate-dev] IRC
Message-ID: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>

just a heads up that I have not been able to connect to freenode for quite
a few weeks now.  Still no idea what is up there.

From manderse at redhat.com  Mon Oct 13 15:34:12 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 13 Oct 2014 21:34:12 +0200
Subject: [hibernate-dev] IRC
In-Reply-To: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
References: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
Message-ID: <F42E094C-B91E-4636-BC4D-CBDB94BCEB76@redhat.com>

On 13 Oct 2014, at 20:48, Steve Ebersole wrote:

> just a heads up that I have not been able to connect to freenode for 
> quite
> a few weeks now.  Still no idea what is up there.

freenode moved to require SSL for some connections afaik. Use 6697 for 
port,
and they also changed hostsnames - thus use irc.freenode.org if you 
don't already

And finally the one that annoyed me in US last time I was there. AT&T 
customers
cannot connect unless using SASL (https://freenode.net/sasl/) - maybe 
they extended
that to other providers ?

just some ideas.

/max
http://about.me/maxandersen

From sanne at hibernate.org  Mon Oct 13 16:31:33 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Mon, 13 Oct 2014 21:31:33 +0100
Subject: [hibernate-dev] IRC
In-Reply-To: <F42E094C-B91E-4636-BC4D-CBDB94BCEB76@redhat.com>
References: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
	<F42E094C-B91E-4636-BC4D-CBDB94BCEB76@redhat.com>
Message-ID: <CAFm4XO3Kwvm97cK6mBDZ37fjzFVUBnB3tzJWD8E55TkROxpG_Q@mail.gmail.com>

I had trouble too after I changed passwords as recommended; I decided
to give client side certificates a go:
 https://freenode.net/certfp/

Works far better now and I have no longer clear text passwords; Also I
can finally have it connect to #hibernate-dev automatically as it
properly authenticates before trying to join.
Using Konversation.

Sanne

On 13 October 2014 20:34, Max Rydahl Andersen <manderse at redhat.com> wrote:
> On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
>
>> just a heads up that I have not been able to connect to freenode for
>> quite
>> a few weeks now.  Still no idea what is up there.
>
> freenode moved to require SSL for some connections afaik. Use 6697 for
> port,
> and they also changed hostsnames - thus use irc.freenode.org if you
> don't already
>
> And finally the one that annoyed me in US last time I was there. AT&T
> customers
> cannot connect unless using SASL (https://freenode.net/sasl/) - maybe
> they extended
> that to other providers ?
>
> just some ideas.
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

From smarlow at redhat.com  Mon Oct 13 19:04:59 2014
From: smarlow at redhat.com (Scott Marlow)
Date: Mon, 13 Oct 2014 19:04:59 -0400
Subject: [hibernate-dev] IRC
In-Reply-To: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
References: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
Message-ID: <543C5A9B.7080604@redhat.com>

I don't see how it could be related but a few weeks ago freenode 
recommended that everyone change their passwords.

On 10/13/2014 02:48 PM, Steve Ebersole wrote:
> just a heads up that I have not been able to connect to freenode for quite
> a few weeks now.  Still no idea what is up there.
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>


From guillaume.smet at gmail.com  Tue Oct 14 09:23:54 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Tue, 14 Oct 2014 15:23:54 +0200
Subject: [hibernate-dev] HHH-7610 Embedded: emptiness and dirtiness
Message-ID: <CALt0+o_tayrMBQSZAx6946=pS7mOx287zFm2jBBWDB1-sFxr+w@mail.gmail.com>

Hi all,

So, after a long time without any issue (rest assured we were busy
anyway!), we got around a new problem we would like to fix in ORM:
HHH-7610 .

It's a long standing complaint about the embedded and the fact that
empty components are returned from the ORM.

We had the "good" idea to fix it by overriding the getter to set the
value to an empty object if null and it's not really a good one: we do
a lot of unnecessary updates due to the fact that our entities are
considered dirty.

A coworker of mine (Laurent CCed) followed the instructions given by
Steve in HHH-7610 to implement a configuration setting to return an
empty component if all its properties is null:
see https://github.com/openwide-java/hibernate-orm/commit/a219fd38c0a80e6bf0a5de41f31e49ee83f00ccf
-> we think this one should be ready to commit. It's for 4.3.x.
-> using all the tests with this new setting enabled triggers a few
errors but, after carefully reviewing them, they are all expected due
to the nature of this change.

We are wondering if we shouldn't also change the isDirty/equals...
stuff to consider 2 components equals if one is null and the other has
all its properties null: it sounds kinda logical to us considering ORM
already automatically transforms one to the other if we save then get
the entity.

We wrote a few tests to demonstrate the issue and we would like to
know if you would consider this a good idea or not to fix this in both
cases (settings on or off):
https://github.com/openwide-java/hibernate-orm/commit/ee913e79633d3a5ac9c5affdcb58ab3af780f71a

Thanks for your advice.

-- 
Guillaume

From steve at hibernate.org  Tue Oct 14 11:48:17 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Tue, 14 Oct 2014 10:48:17 -0500
Subject: [hibernate-dev] IRC
In-Reply-To: <CAFm4XO3Kwvm97cK6mBDZ37fjzFVUBnB3tzJWD8E55TkROxpG_Q@mail.gmail.com>
References: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
	<F42E094C-B91E-4636-BC4D-CBDB94BCEB76@redhat.com>
	<CAFm4XO3Kwvm97cK6mBDZ37fjzFVUBnB3tzJWD8E55TkROxpG_Q@mail.gmail.com>
Message-ID: <CAFdSV9s4r-Gq4yCaVAimKg_zDLa9-sY_bDw506HRFg5cH1cbtQ@mail.gmail.com>

"works better" how?  You mean as in more stable?  I can connect now using
the info from Max (thanks Max!).  But I keep having "no response from
server" type connectivity problems.  Wondering if certs would help there.
I don't see how.



On Mon, Oct 13, 2014 at 3:31 PM, Sanne Grinovero <sanne at hibernate.org>
wrote:

> I had trouble too after I changed passwords as recommended; I decided
> to give client side certificates a go:
>  https://freenode.net/certfp/
>
> Works far better now and I have no longer clear text passwords; Also I
> can finally have it connect to #hibernate-dev automatically as it
> properly authenticates before trying to join.
> Using Konversation.
>
> Sanne
>
> On 13 October 2014 20:34, Max Rydahl Andersen <manderse at redhat.com> wrote:
> > On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
> >
> >> just a heads up that I have not been able to connect to freenode for
> >> quite
> >> a few weeks now.  Still no idea what is up there.
> >
> > freenode moved to require SSL for some connections afaik. Use 6697 for
> > port,
> > and they also changed hostsnames - thus use irc.freenode.org if you
> > don't already
> >
> > And finally the one that annoyed me in US last time I was there. AT&T
> > customers
> > cannot connect unless using SASL (https://freenode.net/sasl/) - maybe
> > they extended
> > that to other providers ?
> >
> > just some ideas.
> >
> > /max
> > http://about.me/maxandersen
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From sanne at hibernate.org  Tue Oct 14 12:54:05 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Tue, 14 Oct 2014 17:54:05 +0100
Subject: [hibernate-dev] IRC
In-Reply-To: <CAFdSV9s4r-Gq4yCaVAimKg_zDLa9-sY_bDw506HRFg5cH1cbtQ@mail.gmail.com>
References: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
	<F42E094C-B91E-4636-BC4D-CBDB94BCEB76@redhat.com>
	<CAFm4XO3Kwvm97cK6mBDZ37fjzFVUBnB3tzJWD8E55TkROxpG_Q@mail.gmail.com>
	<CAFdSV9s4r-Gq4yCaVAimKg_zDLa9-sY_bDw506HRFg5cH1cbtQ@mail.gmail.com>
Message-ID: <CAFm4XO1FyuoS582xFnPNfuSqt+_6Xs8wfv0K+i1tvWzTazvarA@mail.gmail.com>

On 14 October 2014 16:48, Steve Ebersole <steve at hibernate.org> wrote:
> "works better" how?  You mean as in more stable?  I can connect now using
> the info from Max (thanks Max!).  But I keep having "no response from
> server" type connectivity problems.  Wondering if certs would help there.  I
> don't see how.

Yes I have the impression that it's more stable, but have no facts backing that.

The main reason for me to like certs is not stability though, but it's
the "login first" semantic, as I'm otherwise kicked out of
#hibernate-dev.

Sanne

>
>
>
> On Mon, Oct 13, 2014 at 3:31 PM, Sanne Grinovero <sanne at hibernate.org>
> wrote:
>>
>> I had trouble too after I changed passwords as recommended; I decided
>> to give client side certificates a go:
>>  https://freenode.net/certfp/
>>
>> Works far better now and I have no longer clear text passwords; Also I
>> can finally have it connect to #hibernate-dev automatically as it
>> properly authenticates before trying to join.
>> Using Konversation.
>>
>> Sanne
>>
>> On 13 October 2014 20:34, Max Rydahl Andersen <manderse at redhat.com> wrote:
>> > On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
>> >
>> >> just a heads up that I have not been able to connect to freenode for
>> >> quite
>> >> a few weeks now.  Still no idea what is up there.
>> >
>> > freenode moved to require SSL for some connections afaik. Use 6697 for
>> > port,
>> > and they also changed hostsnames - thus use irc.freenode.org if you
>> > don't already
>> >
>> > And finally the one that annoyed me in US last time I was there. AT&T
>> > customers
>> > cannot connect unless using SASL (https://freenode.net/sasl/) - maybe
>> > they extended
>> > that to other providers ?
>> >
>> > just some ideas.
>> >
>> > /max
>> > http://about.me/maxandersen
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>

From thomas.jones-low at foundationdb.com  Tue Oct 14 16:27:58 2014
From: thomas.jones-low at foundationdb.com (Thomas Jones-Low)
Date: Tue, 14 Oct 2014 16:27:58 -0400
Subject: [hibernate-dev] IRC
In-Reply-To: <543C5A9B.7080604@redhat.com>
References: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
	<543C5A9B.7080604@redhat.com>
Message-ID: <543D874E.8050709@foundationdb.com>

	Found this link on Hacker News:
https://www.nccgroup.com/en/blog/2014/10/analysis-of-the-linux-backdoor-used-in-freenode-irc-network-compromise/

	Apparently they were hacked pretty badly.

On 10/13/14, 7:04 PM, Scott Marlow wrote:
> I don't see how it could be related but a few weeks ago freenode
> recommended that everyone change their passwords.
>
> On 10/13/2014 02:48 PM, Steve Ebersole wrote:
>> just a heads up that I have not been able to connect to freenode for quite
>> a few weeks now.  Still no idea what is up there.
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>


From steve at hibernate.org  Wed Oct 15 14:50:48 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Wed, 15 Oct 2014 13:50:48 -0500
Subject: [hibernate-dev] IRC
In-Reply-To: <543D874E.8050709@foundationdb.com>
References: <CAFdSV9uA_qmQxDfkqn3UdF6u7aq9_t+T_ew+WUbhUKaSx2XrBw@mail.gmail.com>
	<543C5A9B.7080604@redhat.com> <543D874E.8050709@foundationdb.com>
Message-ID: <CAFdSV9s+T7nOVV+YmEvgagi3kVdzwX97-N+b+MbsX3QKnqZEpw@mail.gmail.com>

Interesting.  I think I may have found a big culprit.  It seems that Fedora
likes to enable IPv6 on connections by default.  I disabled IPv6 support
and some "unrelated" browsing problems I have been having were cleared up.
I'll have to see if that helps with IRC.

On Tue, Oct 14, 2014 at 3:27 PM, Thomas Jones-Low <
thomas.jones-low at foundationdb.com> wrote:

>         Found this link on Hacker News:
>
> https://www.nccgroup.com/en/blog/2014/10/analysis-of-the-linux-backdoor-used-in-freenode-irc-network-compromise/
>
>         Apparently they were hacked pretty badly.
>
> On 10/13/14, 7:04 PM, Scott Marlow wrote:
> > I don't see how it could be related but a few weeks ago freenode
> > recommended that everyone change their passwords.
> >
> > On 10/13/2014 02:48 PM, Steve Ebersole wrote:
> >> just a heads up that I have not been able to connect to freenode for
> quite
> >> a few weeks now.  Still no idea what is up there.
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>
> >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From emmanuel at hibernate.org  Thu Oct 16 07:25:02 2014
From: emmanuel at hibernate.org (Emmanuel Bernard)
Date: Thu, 16 Oct 2014 13:25:02 +0200
Subject: [hibernate-dev] Analysis of hibernate-release-4.3.6 dependency
	on JDK-Internal APIs
In-Reply-To: <5437AE47.6080506@oracle.com>
References: <5411AE44.7000102@oracle.com> <5437AE47.6080506@oracle.com>
Message-ID: <8A4A6591-7965-41F7-B330-9B04E527E69A@hibernate.org>

Hi,

Three of these errors are related to Infinispan which you have already contacted.
Two are related to dom4j which we use for XML parsing. While I think our next gen version will no longer use dom4j, we don?t plan on moving away from dom4j for the older and current releases. So I am not sure why you guys are removing org.relaxng form the JDK but if you do then we won?t be able to have Hibernate ORM running on JDK 9.

Emmanuel

On 10 Oct 2014, at 12:00, Rory O'Donnell Oracle, Dublin Ireland <rory.odonnell at oracle.com> wrote:

> Hi Sanne,
> 
> Did you have time to review the report, any feedback ?
> 
> Rgds,Rory
> 
> On 11/09/2014 15:14, Rory O'Donnell Oracle, Dublin Ireland wrote:
>> Hi Sanne,
>> 
>> As part of the preparations for JDK 9, Oracle?s engineers have been analyzing open source projects like yours to understand usage.
>> One area of concern involves identifying compatibility problems, such as reliance on JDK-internal APIs.
>> 
>> Our engineers have already prepared guidance on migrating some of the more common usage patterns of JDK-internal APIs to supported public interfaces. The list is on the OpenJDK wiki [0], along with instructions on how to run the jdeps analysis tool yourself .
>> 
>> As part of the ongoing development of JDK 9, I would like to encourage migration from JDK-internal APIs towards the supported Java APIs. I have prepared a report for your project release hibernate-release-4.3.6 based on the jdeps output.
>> 
>> The report is attached to this e-mail.
>> 
>> For anything where your migration path is unclear, I would appreciate comments on the JDK-internal API usage patterns in the attached jdeps report, (if any) - in particular comments elaborating on the rationale for them - either to me or on the adoption-discuss [1] mailing list at OpenJDK.
>> 
>> Finding suitable replacements for unsupported interfaces is not always straightforward, which is why I am reaching out to you early in the JDK 9 development cycle so you can give feedback about new APIs that may be needed to facilitate this exercise.
>> 
>> Thank you in advance for any efforts and feedback helping us make JDK 9 better,
>> Rgds,Rory
>> 
>> [0] https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
>> [1] http://mail.openjdk.java.net/mailman/listinfo/adoption-discuss
>> 
> 
> -- 
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland
> 
> 
> 
> 



From steve at hibernate.org  Thu Oct 16 09:11:22 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Thu, 16 Oct 2014 08:11:22 -0500
Subject: [hibernate-dev] Analysis of hibernate-release-4.3.6 dependency
 on JDK-Internal APIs
In-Reply-To: <8A4A6591-7965-41F7-B330-9B04E527E69A@hibernate.org>
References: <5411AE44.7000102@oracle.com> <5437AE47.6080506@oracle.com>
	<8A4A6591-7965-41F7-B330-9B04E527E69A@hibernate.org>
Message-ID: <CAFdSV9s8qL7XLPu1e9NKNFuDH8tzdzhRW-RnNS=ENT4P4JqSfg@mail.gmail.com>

Correct.  Starting in 5.0 we are using a combo of jaxb + stax for XML
parsing, instead of dom4j.  At the moment we have no concrete plans to do
any 4.x release with that approach, although it is one of the items we want
to discuss when we get together in a few weeks: specifically a possible
4.4/4.5 release with a *limited* subset of concepts/code ported from 5.0
back to the 4.x codebase.

On Thu, Oct 16, 2014 at 6:25 AM, Emmanuel Bernard <emmanuel at hibernate.org>
wrote:

> Hi,
>
> Three of these errors are related to Infinispan which you have already
> contacted.
> Two are related to dom4j which we use for XML parsing. While I think our
> next gen version will no longer use dom4j, we don?t plan on moving away
> from dom4j for the older and current releases. So I am not sure why you
> guys are removing org.relaxng form the JDK but if you do then we won?t be
> able to have Hibernate ORM running on JDK 9.
>
> Emmanuel
>
> On 10 Oct 2014, at 12:00, Rory O'Donnell Oracle, Dublin Ireland <
> rory.odonnell at oracle.com> wrote:
>
> > Hi Sanne,
> >
> > Did you have time to review the report, any feedback ?
> >
> > Rgds,Rory
> >
> > On 11/09/2014 15:14, Rory O'Donnell Oracle, Dublin Ireland wrote:
> >> Hi Sanne,
> >>
> >> As part of the preparations for JDK 9, Oracle?s engineers have been
> analyzing open source projects like yours to understand usage.
> >> One area of concern involves identifying compatibility problems, such
> as reliance on JDK-internal APIs.
> >>
> >> Our engineers have already prepared guidance on migrating some of the
> more common usage patterns of JDK-internal APIs to supported public
> interfaces. The list is on the OpenJDK wiki [0], along with instructions on
> how to run the jdeps analysis tool yourself .
> >>
> >> As part of the ongoing development of JDK 9, I would like to encourage
> migration from JDK-internal APIs towards the supported Java APIs. I have
> prepared a report for your project release hibernate-release-4.3.6 based on
> the jdeps output.
> >>
> >> The report is attached to this e-mail.
> >>
> >> For anything where your migration path is unclear, I would appreciate
> comments on the JDK-internal API usage patterns in the attached jdeps
> report, (if any) - in particular comments elaborating on the rationale for
> them - either to me or on the adoption-discuss [1] mailing list at OpenJDK.
> >>
> >> Finding suitable replacements for unsupported interfaces is not always
> straightforward, which is why I am reaching out to you early in the JDK 9
> development cycle so you can give feedback about new APIs that may be
> needed to facilitate this exercise.
> >>
> >> Thank you in advance for any efforts and feedback helping us make JDK 9
> better,
> >> Rgds,Rory
> >>
> >> [0]
> https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
> >> [1] http://mail.openjdk.java.net/mailman/listinfo/adoption-discuss
> >>
> >
> > --
> > Rgds,Rory O'Donnell
> > Quality Engineering Manager
> > Oracle EMEA , Dublin, Ireland
> >
> >
> >
> >
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From guillaume.smet at gmail.com  Mon Oct 20 05:08:57 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Mon, 20 Oct 2014 11:08:57 +0200
Subject: [hibernate-dev] HHH-7610 Embedded: emptiness and dirtiness
In-Reply-To: <CALt0+o_tayrMBQSZAx6946=pS7mOx287zFm2jBBWDB1-sFxr+w@mail.gmail.com>
References: <CALt0+o_tayrMBQSZAx6946=pS7mOx287zFm2jBBWDB1-sFxr+w@mail.gmail.com>
Message-ID: <CALt0+o9UJqpRJAa1+zZWoGSeXhGrbw89XBDsHE2E0yZx9ekc+w@mail.gmail.com>

Hi!

Any interest in us pursuing this?

We are obviously committed to update the documentation once we have
validated it's the way to go.

Thanks for your feedback.

On Tue, Oct 14, 2014 at 3:23 PM, Guillaume Smet
<guillaume.smet at gmail.com> wrote:
> Hi all,
>
> So, after a long time without any issue (rest assured we were busy
> anyway!), we got around a new problem we would like to fix in ORM:
> HHH-7610 .
>
> It's a long standing complaint about the embedded and the fact that
> empty components are returned from the ORM.
>
> We had the "good" idea to fix it by overriding the getter to set the
> value to an empty object if null and it's not really a good one: we do
> a lot of unnecessary updates due to the fact that our entities are
> considered dirty.
>
> A coworker of mine (Laurent CCed) followed the instructions given by
> Steve in HHH-7610 to implement a configuration setting to return an
> empty component if all its properties is null:
> see https://github.com/openwide-java/hibernate-orm/commit/a219fd38c0a80e6bf0a5de41f31e49ee83f00ccf
> -> we think this one should be ready to commit. It's for 4.3.x.
> -> using all the tests with this new setting enabled triggers a few
> errors but, after carefully reviewing them, they are all expected due
> to the nature of this change.
>
> We are wondering if we shouldn't also change the isDirty/equals...
> stuff to consider 2 components equals if one is null and the other has
> all its properties null: it sounds kinda logical to us considering ORM
> already automatically transforms one to the other if we save then get
> the entity.
>
> We wrote a few tests to demonstrate the issue and we would like to
> know if you would consider this a good idea or not to fix this in both
> cases (settings on or off):
> https://github.com/openwide-java/hibernate-orm/commit/ee913e79633d3a5ac9c5affdcb58ab3af780f71a
>
> Thanks for your advice.
>
> --
> Guillaume

From sanne at hibernate.org  Mon Oct 20 08:38:21 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Mon, 20 Oct 2014 13:38:21 +0100
Subject: [hibernate-dev] Improving performance of index-writing for
	Hibernate Search
Message-ID: <CAFm4XO1_x1i164onGviovQwFeHC6AQMe8Rvuio6aYj6DmxcazA@mail.gmail.com>

Hi all,
after some performance tests on Infinispan we concluded that the way
Hibernate Search writes to the index is not as efficient as we'd like
to.

While these results came from extensive Infinispan testing, it's
actually highlighting a performance issue which isn't strictly related
to Infinispan storage, and could affect any kind of index storage
which we support.
Surprisingly this wasn't too bad for normal disk based FSDirectory,
especially as we expect users to got for the NRT backend, but as you
might know an NRT backend is not suited for clustered deployments (be
it using a master/slave approach or the Infinispan index, or other
more experimental shared index strategies like NFS based sharing).

So, while NRT performs great, the "normal" backend actually doesn't
perform very well because of the high frequency of commits.


Surprisingly even an ASYNC backend does the same amount of commits, so
enabling the async workers of Hibernate Search would decouple the
latency of the main thread from the speed of the backend, but if you
have a sustained amount of writes the overall throughput that the
backend is able to deliver would not change.

A much better design is to allow the ASYNC backends to _not_ flush at
each commit, but to flush periodically. The overall throughput
increase is estimated to be 2 to 3 orders of magnitude, details
depending on the kind of storage you're having.
This idea is being proposed as:
 - https://hibernate.atlassian.net/browse/HSEARCH-1693

Gustavo sent a first pull request for this already, some preliminary
results can be found on the pull request description:
 https://github.com/hibernate/hibernate-search/pull/681

Note that his tests focus on Infinispan storage but the code is
unrelated to Infinispan and will benefit all users independently from
the storage technology.
This patch will expose a new configuration property which will allow
users to specify how often they need the indexes to be committed; in
other words, you'll be able to specify that Async is acceptable for
your application, but as long as the "staleness" of your index doesn't
exceed a set threshold of time.

Now the best part of this, is that we can also propose a solution for
the SYNC backends which require an illusion of transactional
behaviour. Essentially we're aiming at implementing a synchronous
backend which has performance close to the capabilities of NRT, but
without the drawbacks so that it can safely be used on shared indexes.

This ideas is a bit more complex to implement, I've attempted to describe it on:
 https://hibernate.atlassian.net/browse/HSEARCH-1699

Sanne

From emmanuel at hibernate.org  Mon Oct 20 13:21:27 2014
From: emmanuel at hibernate.org (Emmanuel Bernard)
Date: Mon, 20 Oct 2014 19:21:27 +0200
Subject: [hibernate-dev] [OGM] Removing row keys from associations
In-Reply-To: <CADGJaX-YfkRYbGhuG34=sJE7bNgwiX-hGmrA5wNZ+FheJ+8oyA@mail.gmail.com>
References: <CADGJaX-9DTLTWhJYOU5bBEkTSiV-EGNDKJmX=dycD-0nHmyTiQ@mail.gmail.com>
	<20140929161638.GA51558@hibernate.org>
	<CADGJaX-YfkRYbGhuG34=sJE7bNgwiX-hGmrA5wNZ+FheJ+8oyA@mail.gmail.com>
Message-ID: <A1778BC0-6F29-4E5C-ACE1-DB9FF3C3D295@hibernate.org>

Sorry I read too fast. Indeed if you are working from the representation in memory and not considering what happened in the backend, I don?t think it should happen or as you say something is fishy (like multi-thread abuse).

On 30 Sep 2014, at 09:10, Gunnar Morling <gunnar at hibernate.org> wrote:

> Thanks for coming back on this :)
> 
> 2014-09-29 18:16 GMT+02:00 Emmanuel Bernard <emmanuel at hibernate.org>:
> I think that can happen due to the weak transactional guarantees the
> underlying backend provides.
> Why do you ask? (that is if you remember as this email is quite old -
> nothing like being stuck on a place for 12 hours to catch up ;) ).
> 
> I'm not entirely sure anymore why I asked :) Maybe I considered to guard against it using an assertion.
> 
> Does it really depend on the capabilities of the store, though? Between loading an Association and removing a RowKey from it, all is in our control (and all in one thread). So if we invoke Association#remove() for a RowKey which isn't present in the loaded Association object, it still seems fishy to me.
> 
> Note that's different from trying to remove an association row in the store actually, there it may be gone already of course.
> 
> On Wed 2014-08-27 22:40, Gunnar Morling wrote:
> > Hi Emmanuel,
> >
> > Is there any legitimate case where Association#remove(RowKey) is invoked
> > for a key which is not present in that specific association instance? Or
> > would this indicate some programming error?
> >
> > Thanks,
> >
> > --Gunnar
> 


From ulrich.kitzinger at muenchen.de  Tue Oct 21 02:51:09 2014
From: ulrich.kitzinger at muenchen.de (Ulrich Kitzinger)
Date: Tue, 21 Oct 2014 08:51:09 +0200
Subject: [hibernate-dev] Bug/patch in Hibernate Envers
Message-ID: <5446025D.7030005@muenchen.de>

Hello,

we are developing a database application with Hibernate. For legal
grounds, we have to assure that we are able backtrace certain actions
our users made (here we're using envers).

Now we think we detected a bug in envers regarding an audited relation
with an additional @where clause, as described in
https://hibernate.atlassian.net/browse/HHH-9432.

I submitted a patch for the bug, see
https://github.com/hibernate/hibernate-orm/pull/824. As this problem
really hurts us, we would be glad to get any feedback whether the patch
is fine or not.
-- 

Yours

Ulrich Kitzinger

From sanne at hibernate.org  Tue Oct 21 07:13:34 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Tue, 21 Oct 2014 12:13:34 +0100
Subject: [hibernate-dev] Tests on JDK 9,
	and other updates on ci.hibernate.org
In-Reply-To: <CAFm4XO1Z=jOMwNoZjDUeD7+MBg8MFHxnBXZ-oKgVKN2C2=ooyg@mail.gmail.com>
References: <CAFm4XO3K2Egz+=MG8kZATt=1VH9ed5mbwKjsqcor=AOAzPojLw@mail.gmail.com>
	<20140908112540.GA13087@hibernate.org>
	<CAFm4XO2ZfxVsRQuWEU-Vmhu8nN637wionDfAxUarw-DZvi9EUQ@mail.gmail.com>
	<20140908115737.GD13087@hibernate.org>
	<CAFm4XO0T=-MFbmvjDHp8NnyOGcXr3DfMZmNqasnzXjg4oeM1jw@mail.gmail.com>
	<20140908141540.GA43072@Sarmakand-2.local>
	<CAFm4XO1Z=jOMwNoZjDUeD7+MBg8MFHxnBXZ-oKgVKN2C2=ooyg@mail.gmail.com>
Message-ID: <CAFm4XO0e+8CgkiUUeO8W+qKjZqY+dE=2X0rLziYVoaifHmP6yQ@mail.gmail.com>

All,
I've updated the JDK versions on ci.hibernate.org to include

# Early Access build for JDK 9 b35 <https://jdk9.java.net/download/>
   summary of changes: http://www.java.net/download/jdk9/changes/jdk9-b35.html
   name on CI: Preview-JDK9

# Early Access build for JDK 8u40 b10 <http://jdk8.java.net/download.html>
   summary of changes:
http://www.java.net/download/jdk8u40/changes/jdk8u40-b10.html
   name on CI: Oracle JDK 8

But I still need your help to setup the project to actually use these
JDK's. I've setup Hibernate Search, I am hoping you could all take
ownership of one project you're most involved with and set it up as
well.

I still didn't disable asciidoctor on Hibernate Search, which fails
the documentation build, but besides that at least I know the tests
work fine.

Thanks,
Sanne

On 8 September 2014 23:57, Sanne Grinovero <sanne at hibernate.org> wrote:
> On 8 September 2014 15:15, Hardy Ferentschik <hardy at hibernate.org> wrote:
>> On Mon, Sep 08, 2014 at 01:06:16PM +0100, Sanne Grinovero wrote:
>>
>>> I have no strong preference, just preferring to keep it on by default
>>> as it generally runs quickly enough;
>>
>> +1 for keeping things running per default (and it is a strong preference ;-))
>>
>>> But obviously we need a switch to turn it off for such cases as the
>>> JDK not being compatible.
>>
>> Do we right now? Can we not just wait a bit to things how things are shaping up?
>> I get the point of being pro-active, but do we need a Java 9 build right now?
>> I'll let the asciisoc and JRuby guys chew a little bit on this and see what
>> they come up with.
>
> "Right now" can be flexible of course, but the JDK will come sooner
> than usual. Having these tasks running doesn't necessarily imply that
> our stuff will work fine but it means we'll have the knowledge to be
> able to make informed decisions at lowest overhead (the earlier the
> better).
>
> I'd like us to be pro-active in terms of "our stuff will work on
> Java9" but I don't want to spend cycles on debugging stuff on behalf
> of asciidoc or JRuby to work on JDK9 too, so realistically we should
> disable these and let other deal with it at their own pace.
>
> Not least, we're engaged in a promise to the OpenJDK team to test
> these builds, in exchange we get full attention to bug reports:
>  - https://wiki.openjdk.java.net/display/Adoption/Quality+Out+Reach
>
> Sanne

From hardy at hibernate.org  Thu Oct 23 06:20:51 2014
From: hardy at hibernate.org (Hardy Ferentschik)
Date: Thu, 23 Oct 2014 12:20:51 +0200
Subject: [hibernate-dev] Hibernate Validator 5.2.0.Alpha1 with Java 8
 support and a 5.1 maintenance release
Message-ID: <20141023102051.GB2474@sarmakand.lan>

Two new Hibernate Validator releases! All the juicy details on in.relation.to - http://in.relation.to/34906.lace

Enjoy,
Hardy

From adriano.nego at gmail.com  Thu Oct 23 11:28:31 2014
From: adriano.nego at gmail.com (Adriano Santos)
Date: Thu, 23 Oct 2014 12:28:31 -0300
Subject: [hibernate-dev] Get JSON value from Postgres
Message-ID: <CAODxFaHwgMLFXyiVUykoRt3vTDQqk_8bKiReiPzsLHWAC30ZzA@mail.gmail.com>

Hi, everyone.

 I'm trying to get a JSON value from Postgres DB, but I'm receiving this
error:

DefaultLoadEventListener:160 - Error performing load command
org.hibernate.PropertyAccessException: could not set a field value by
reflection setter of DTO.Processo._tramites
at
org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:151)

I saw that Hipernate don?t have a JSON Type yet, so I build a type for this.

I did a ?My UserType? (StringJsonUserType implements UserType) and
JsonPostgreSQLDialect (extends PostgresPlusDialect). I insert data , but
when I try to get some value, i got this error return.

 I using Hibernat version 3.5.6.final and postgresql-9.3-1102-jdbc.

Anybody have some idea about whats happen and can I workaround this problem?

Best regards.



-- 

Adriano Ara?jo Santos


*"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
original."*

From sanne at hibernate.org  Thu Oct 23 12:12:11 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Thu, 23 Oct 2014 17:12:11 +0100
Subject: [hibernate-dev] Get JSON value from Postgres
In-Reply-To: <CAODxFaHwgMLFXyiVUykoRt3vTDQqk_8bKiReiPzsLHWAC30ZzA@mail.gmail.com>
References: <CAODxFaHwgMLFXyiVUykoRt3vTDQqk_8bKiReiPzsLHWAC30ZzA@mail.gmail.com>
Message-ID: <CAFm4XO2F=Q7X2JGymuoABjdw+fQYer0OhojvAY=-G6oa3UpEUQ@mail.gmail.com>

Hi Adriano,
that version is very old, it's going to be unlikely to find someone
able to help you. But it looks like a very interesting feature :-)

If you could change your code and testing to use latest master from
github, or the latest stable version 4.3, then someone on this list
might volunteer to help you include the new JSON Type into the
Hibernate codebase, if you agree with that.

Sanne

On 23 October 2014 16:28, Adriano Santos <adriano.nego at gmail.com> wrote:
> Hi, everyone.
>
>  I'm trying to get a JSON value from Postgres DB, but I'm receiving this
> error:
>
> DefaultLoadEventListener:160 - Error performing load command
> org.hibernate.PropertyAccessException: could not set a field value by
> reflection setter of DTO.Processo._tramites
> at
> org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:151)
>
> I saw that Hipernate don?t have a JSON Type yet, so I build a type for this.
>
> I did a ?My UserType? (StringJsonUserType implements UserType) and
> JsonPostgreSQLDialect (extends PostgresPlusDialect). I insert data , but
> when I try to get some value, i got this error return.
>
>  I using Hibernat version 3.5.6.final and postgresql-9.3-1102-jdbc.
>
> Anybody have some idea about whats happen and can I workaround this problem?
>
> Best regards.
>
>
>
> --
>
> Adriano Ara?jo Santos
>
>
> *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
> original."*
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev


From adriano.nego at gmail.com  Thu Oct 23 14:58:23 2014
From: adriano.nego at gmail.com (Adriano Santos)
Date: Thu, 23 Oct 2014 15:58:23 -0300
Subject: [hibernate-dev] Get JSON value from Postgres
In-Reply-To: <CAFm4XO2F=Q7X2JGymuoABjdw+fQYer0OhojvAY=-G6oa3UpEUQ@mail.gmail.com>
References: <CAODxFaHwgMLFXyiVUykoRt3vTDQqk_8bKiReiPzsLHWAC30ZzA@mail.gmail.com>
	<CAFm4XO2F=Q7X2JGymuoABjdw+fQYer0OhojvAY=-G6oa3UpEUQ@mail.gmail.com>
Message-ID: <CAODxFaEpGvjDJP6CiYj2q11-ftaKS7i6FWuOeemRtrhEjFGJ_Q@mail.gmail.com>

Hi, Sanne.

 Thanks for your support. So... Which is the version do you indicates? I'm
using the Maven Repository and the last establish version is 3.5.6-Final.
I'm using (without the dependencies):

  - hibernate-annotations
  - hibernate-core
  - hibernate-entitymanager

Ths for all.


On Thu, Oct 23, 2014 at 1:12 PM, Sanne Grinovero <sanne at hibernate.org>
wrote:

> Hi Adriano,
> that version is very old, it's going to be unlikely to find someone
> able to help you. But it looks like a very interesting feature :-)
>
> If you could change your code and testing to use latest master from
> github, or the latest stable version 4.3, then someone on this list
> might volunteer to help you include the new JSON Type into the
> Hibernate codebase, if you agree with that.
>
> Sanne
>
> On 23 October 2014 16:28, Adriano Santos <adriano.nego at gmail.com> wrote:
> > Hi, everyone.
> >
> >  I'm trying to get a JSON value from Postgres DB, but I'm receiving this
> > error:
> >
> > DefaultLoadEventListener:160 - Error performing load command
> > org.hibernate.PropertyAccessException: could not set a field value by
> > reflection setter of DTO.Processo._tramites
> > at
> >
> org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:151)
> >
> > I saw that Hipernate don?t have a JSON Type yet, so I build a type for
> this.
> >
> > I did a ?My UserType? (StringJsonUserType implements UserType) and
> > JsonPostgreSQLDialect (extends PostgresPlusDialect). I insert data , but
> > when I try to get some value, i got this error return.
> >
> >  I using Hibernat version 3.5.6.final and postgresql-9.3-1102-jdbc.
> >
> > Anybody have some idea about whats happen and can I workaround this
> problem?
> >
> > Best regards.
> >
> >
> >
> > --
> >
> > Adriano Ara?jo Santos
> >
> >
> > *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
> > original."*
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>



-- 

Adriano Ara?jo Santos


*"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
original."*

From gunnar at hibernate.org  Thu Oct 23 16:13:02 2014
From: gunnar at hibernate.org (Gunnar Morling)
Date: Thu, 23 Oct 2014 22:13:02 +0200
Subject: [hibernate-dev] Get JSON value from Postgres
In-Reply-To: <CAODxFaEpGvjDJP6CiYj2q11-ftaKS7i6FWuOeemRtrhEjFGJ_Q@mail.gmail.com>
References: <CAODxFaHwgMLFXyiVUykoRt3vTDQqk_8bKiReiPzsLHWAC30ZzA@mail.gmail.com>
	<CAFm4XO2F=Q7X2JGymuoABjdw+fQYer0OhojvAY=-G6oa3UpEUQ@mail.gmail.com>
	<CAODxFaEpGvjDJP6CiYj2q11-ftaKS7i6FWuOeemRtrhEjFGJ_Q@mail.gmail.com>
Message-ID: <CADGJaX-2JFXe2ARgdP8Q3wEnt0AoQTrJO8C6fTkx6+TKtXQMUA@mail.gmail.com>

Hi,

The current version is 4.3.6.Final:
http://search.maven.org/#search|ga|1|g%3A%22org.hibernate%22%20AND%20v%3A%224.3.6.Final%22

Note that hibernate-annotations has been merged into hibernate-core as of
3.6.

Hth,

--Gunnar


2014-10-23 20:58 GMT+02:00 Adriano Santos <adriano.nego at gmail.com>:

> Hi, Sanne.
>
>  Thanks for your support. So... Which is the version do you indicates? I'm
> using the Maven Repository and the last establish version is 3.5.6-Final.
> I'm using (without the dependencies):
>
>   - hibernate-annotations
>   - hibernate-core
>   - hibernate-entitymanager
>
> Ths for all.
>
>
> On Thu, Oct 23, 2014 at 1:12 PM, Sanne Grinovero <sanne at hibernate.org>
> wrote:
>
> > Hi Adriano,
> > that version is very old, it's going to be unlikely to find someone
> > able to help you. But it looks like a very interesting feature :-)
> >
> > If you could change your code and testing to use latest master from
> > github, or the latest stable version 4.3, then someone on this list
> > might volunteer to help you include the new JSON Type into the
> > Hibernate codebase, if you agree with that.
> >
> > Sanne
> >
> > On 23 October 2014 16:28, Adriano Santos <adriano.nego at gmail.com> wrote:
> > > Hi, everyone.
> > >
> > >  I'm trying to get a JSON value from Postgres DB, but I'm receiving
> this
> > > error:
> > >
> > > DefaultLoadEventListener:160 - Error performing load command
> > > org.hibernate.PropertyAccessException: could not set a field value by
> > > reflection setter of DTO.Processo._tramites
> > > at
> > >
> >
> org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:151)
> > >
> > > I saw that Hipernate don?t have a JSON Type yet, so I build a type for
> > this.
> > >
> > > I did a ?My UserType? (StringJsonUserType implements UserType) and
> > > JsonPostgreSQLDialect (extends PostgresPlusDialect). I insert data ,
> but
> > > when I try to get some value, i got this error return.
> > >
> > >  I using Hibernat version 3.5.6.final and postgresql-9.3-1102-jdbc.
> > >
> > > Anybody have some idea about whats happen and can I workaround this
> > problem?
> > >
> > > Best regards.
> > >
> > >
> > >
> > > --
> > >
> > > Adriano Ara?jo Santos
> > >
> > >
> > > *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
> > > original."*
> > > _______________________________________________
> > > hibernate-dev mailing list
> > > hibernate-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
>
>
>
> --
>
> Adriano Ara?jo Santos
>
>
> *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
> original."*
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From adriano.nego at gmail.com  Thu Oct 23 16:53:30 2014
From: adriano.nego at gmail.com (Adriano Santos)
Date: Thu, 23 Oct 2014 17:53:30 -0300
Subject: [hibernate-dev] Get JSON value from Postgres
In-Reply-To: <CADGJaX-2JFXe2ARgdP8Q3wEnt0AoQTrJO8C6fTkx6+TKtXQMUA@mail.gmail.com>
References: <CAODxFaHwgMLFXyiVUykoRt3vTDQqk_8bKiReiPzsLHWAC30ZzA@mail.gmail.com>
	<CAFm4XO2F=Q7X2JGymuoABjdw+fQYer0OhojvAY=-G6oa3UpEUQ@mail.gmail.com>
	<CAODxFaEpGvjDJP6CiYj2q11-ftaKS7i6FWuOeemRtrhEjFGJ_Q@mail.gmail.com>
	<CADGJaX-2JFXe2ARgdP8Q3wEnt0AoQTrJO8C6fTkx6+TKtXQMUA@mail.gmail.com>
Message-ID: <CAODxFaE6WdL44bd_mLu_zMhFggDTMkH2q=pywgCaBdJv0+zAOQ@mail.gmail.com>

Hi, Gunnar.

 I updated my POM.XML with:

<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.16</version>
</dependency>
<dependency>
        <groupId>org.hibernate</groupId>
        <artifactId>hibernate-annotations</artifactId>
        <version>3.5.6-Final</version>
    </dependency>
    <dependency>
  <groupId>org.codehaus.jackson</groupId>
  <artifactId>jackson-mapper-asl</artifactId>
  <version>1.9.13</version>
</dependency>
    <dependency>
        <groupId>org.hibernate</groupId>
        <artifactId>hibernate-core</artifactId>
        <version>4.3.6.Final</version>
    </dependency>
    <dependency>
        <groupId>javassist</groupId>
        <artifactId>javassist</artifactId>
        <version>3.12.1.GA</version>
    </dependency>

    <dependency>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-log4j12</artifactId>
        <version>1.5.8</version>
    </dependency>

  <dependency>
<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>9.3-1102-jdbc41</version>
</dependency>


And I try to run my sample and I received this message error:
 Initial SessionFactory creation failed.java.lang.NoClassDefFoundError:
org/hibernate/util/DTDEntityResolver


On Thu, Oct 23, 2014 at 5:13 PM, Gunnar Morling <gunnar at hibernate.org>
wrote:

> Hi,
>
> The current version is 4.3.6.Final:
> http://search.maven.org/#search|ga|1|g%3A%22org.hibernate%22%20AND%20v%3A%224.3.6.Final%22
> <http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.hibernate%22%20AND%20v%3A%224.3.6.Final%22>
>
> Note that hibernate-annotations has been merged into hibernate-core as of
> 3.6.
>
> Hth,
>
> --Gunnar
>
>
> 2014-10-23 20:58 GMT+02:00 Adriano Santos <adriano.nego at gmail.com>:
>
>> Hi, Sanne.
>>
>>  Thanks for your support. So... Which is the version do you indicates? I'm
>> using the Maven Repository and the last establish version is 3.5.6-Final.
>> I'm using (without the dependencies):
>>
>>   - hibernate-annotations
>>   - hibernate-core
>>   - hibernate-entitymanager
>>
>> Ths for all.
>>
>>
>> On Thu, Oct 23, 2014 at 1:12 PM, Sanne Grinovero <sanne at hibernate.org>
>> wrote:
>>
>> > Hi Adriano,
>> > that version is very old, it's going to be unlikely to find someone
>> > able to help you. But it looks like a very interesting feature :-)
>> >
>> > If you could change your code and testing to use latest master from
>> > github, or the latest stable version 4.3, then someone on this list
>> > might volunteer to help you include the new JSON Type into the
>> > Hibernate codebase, if you agree with that.
>> >
>> > Sanne
>> >
>> > On 23 October 2014 16:28, Adriano Santos <adriano.nego at gmail.com>
>> wrote:
>> > > Hi, everyone.
>> > >
>> > >  I'm trying to get a JSON value from Postgres DB, but I'm receiving
>> this
>> > > error:
>> > >
>> > > DefaultLoadEventListener:160 - Error performing load command
>> > > org.hibernate.PropertyAccessException: could not set a field value by
>> > > reflection setter of DTO.Processo._tramites
>> > > at
>> > >
>> >
>> org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:151)
>> > >
>> > > I saw that Hipernate don?t have a JSON Type yet, so I build a type for
>> > this.
>> > >
>> > > I did a ?My UserType? (StringJsonUserType implements UserType) and
>> > > JsonPostgreSQLDialect (extends PostgresPlusDialect). I insert data ,
>> but
>> > > when I try to get some value, i got this error return.
>> > >
>> > >  I using Hibernat version 3.5.6.final and postgresql-9.3-1102-jdbc.
>> > >
>> > > Anybody have some idea about whats happen and can I workaround this
>> > problem?
>> > >
>> > > Best regards.
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > > Adriano Ara?jo Santos
>> > >
>> > >
>> > > *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
>> > > original."*
>> > > _______________________________________________
>> > > hibernate-dev mailing list
>> > > hibernate-dev at lists.jboss.org
>> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> >
>>
>>
>>
>> --
>>
>> Adriano Ara?jo Santos
>>
>>
>> *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
>> original."*
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
>


-- 

Adriano Ara?jo Santos


*"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
original."*

From steve at hibernate.org  Fri Oct 24 09:08:11 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Fri, 24 Oct 2014 08:08:11 -0500
Subject: [hibernate-dev] HHH-7610 Embedded: emptiness and dirtiness
In-Reply-To: <CALt0+o9UJqpRJAa1+zZWoGSeXhGrbw89XBDsHE2E0yZx9ekc+w@mail.gmail.com>
References: <CALt0+o_tayrMBQSZAx6946=pS7mOx287zFm2jBBWDB1-sFxr+w@mail.gmail.com>
	<CALt0+o9UJqpRJAa1+zZWoGSeXhGrbw89XBDsHE2E0yZx9ekc+w@mail.gmail.com>
Message-ID: <CAFdSV9ukurNLdy82eE+rzgSb+DU41ufE-M7Yuqf7vew27ErEWA@mail.gmail.com>

Hi Guillaume,

In general, yes, there is interest in this.  I think quite a few folks have
asked for it, so certainly it would be nice to make it an option.  We've
all just been busy lately.

As to your specific question, yes I think what you propose makes sense.
Namely, if this setting is enabled, I think it is reasonable to treat a
null component reference and an empty component reference as equivalent.

You are probably aware, but I just wanted to caution you that this solution
as-is makes a not-necessarily-true assumption that this
"hibernate.create_empty_composites.enabled" setting is set when the
Component is created.  This is a general design problem with complete
open-ended-ness of the Configuration object.  There really is not a way
around that in the 4.x code base as it currently sits.  Just pointing out
that this solution is dependent on order of calls to the Configuration
object.

Also, a minor point, but the if-statement to
set ComponentMetamodel#createEmptyCompositesEnabled should be simplified.
I added a line note to commit.

On Mon, Oct 20, 2014 at 4:08 AM, Guillaume Smet <guillaume.smet at gmail.com>
wrote:

> Hi!
>
> Any interest in us pursuing this?
>
> We are obviously committed to update the documentation once we have
> validated it's the way to go.
>
> Thanks for your feedback.
>
> On Tue, Oct 14, 2014 at 3:23 PM, Guillaume Smet
> <guillaume.smet at gmail.com> wrote:
> > Hi all,
> >
> > So, after a long time without any issue (rest assured we were busy
> > anyway!), we got around a new problem we would like to fix in ORM:
> > HHH-7610 .
> >
> > It's a long standing complaint about the embedded and the fact that
> > empty components are returned from the ORM.
> >
> > We had the "good" idea to fix it by overriding the getter to set the
> > value to an empty object if null and it's not really a good one: we do
> > a lot of unnecessary updates due to the fact that our entities are
> > considered dirty.
> >
> > A coworker of mine (Laurent CCed) followed the instructions given by
> > Steve in HHH-7610 to implement a configuration setting to return an
> > empty component if all its properties is null:
> > see
> https://github.com/openwide-java/hibernate-orm/commit/a219fd38c0a80e6bf0a5de41f31e49ee83f00ccf
> > -> we think this one should be ready to commit. It's for 4.3.x.
> > -> using all the tests with this new setting enabled triggers a few
> > errors but, after carefully reviewing them, they are all expected due
> > to the nature of this change.
> >
> > We are wondering if we shouldn't also change the isDirty/equals...
> > stuff to consider 2 components equals if one is null and the other has
> > all its properties null: it sounds kinda logical to us considering ORM
> > already automatically transforms one to the other if we save then get
> > the entity.
> >
> > We wrote a few tests to demonstrate the issue and we would like to
> > know if you would consider this a good idea or not to fix this in both
> > cases (settings on or off):
> >
> https://github.com/openwide-java/hibernate-orm/commit/ee913e79633d3a5ac9c5affdcb58ab3af780f71a
> >
> > Thanks for your advice.
> >
> > --
> > Guillaume
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From guillaume.smet at gmail.com  Fri Oct 24 10:14:26 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Fri, 24 Oct 2014 16:14:26 +0200
Subject: [hibernate-dev] HHH-7610 Embedded: emptiness and dirtiness
In-Reply-To: <CAFdSV9ukurNLdy82eE+rzgSb+DU41ufE-M7Yuqf7vew27ErEWA@mail.gmail.com>
References: <CALt0+o_tayrMBQSZAx6946=pS7mOx287zFm2jBBWDB1-sFxr+w@mail.gmail.com>
	<CALt0+o9UJqpRJAa1+zZWoGSeXhGrbw89XBDsHE2E0yZx9ekc+w@mail.gmail.com>
	<CAFdSV9ukurNLdy82eE+rzgSb+DU41ufE-M7Yuqf7vew27ErEWA@mail.gmail.com>
Message-ID: <CALt0+o9RBHxiQW6URtgv7C5VBm1gjmUb8VhR5gE+ijpBSSSo7w@mail.gmail.com>

Hi Steve,

On Fri, Oct 24, 2014 at 3:08 PM, Steve Ebersole <steve at hibernate.org> wrote:
> As to your specific question, yes I think what you propose makes sense.
> Namely, if this setting is enabled, I think it is reasonable to treat a null
> component reference and an empty component reference as equivalent.

Thanks for your feedback!

Isn't it even more reasonable to treat null and empty as equivalent in
the current behavior?

Currently, we have:
Entity with empty embedded -> save + get -> Entity with null
so we are considering that empty embedded and null are the exact same things.

If you set again the embedded to an empty one for various reasons,
it's going to be considered dirty again which is IMHO wrong.

I won't argue a lot about this as we will run all our applications
with this setting enabled but I think it will be a performance
improvement to fix this in the other case too.

Note that I'm not very familiar with these things so I might have
missed an obvious point.

We are going to fix the things you commented on Github, work on the
documentation and wait for your feedback on this specific point before
going further on this particular issue.

It would be nice to have it in the next 4.3.x release as we have an
application which is particularly affected by this issue.

-- 
Guillaume

From steve at hibernate.org  Fri Oct 24 10:16:58 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Fri, 24 Oct 2014 09:16:58 -0500
Subject: [hibernate-dev] Get JSON value from Postgres
In-Reply-To: <CAODxFaE6WdL44bd_mLu_zMhFggDTMkH2q=pywgCaBdJv0+zAOQ@mail.gmail.com>
References: <CAODxFaHwgMLFXyiVUykoRt3vTDQqk_8bKiReiPzsLHWAC30ZzA@mail.gmail.com>
	<CAFm4XO2F=Q7X2JGymuoABjdw+fQYer0OhojvAY=-G6oa3UpEUQ@mail.gmail.com>
	<CAODxFaEpGvjDJP6CiYj2q11-ftaKS7i6FWuOeemRtrhEjFGJ_Q@mail.gmail.com>
	<CADGJaX-2JFXe2ARgdP8Q3wEnt0AoQTrJO8C6fTkx6+TKtXQMUA@mail.gmail.com>
	<CAODxFaE6WdL44bd_mLu_zMhFggDTMkH2q=pywgCaBdJv0+zAOQ@mail.gmail.com>
Message-ID: <CAFdSV9sLk5AcB0gAbM+7OP03G-XAO9W0G8x02s+ezO7jr3UXuQ@mail.gmail.com>

The first thing you'll probably need to do is to do a clean build of your
project.  More than likely you are using classes/interfaces that are
removed, refactored and/or moved.  3.5.6 to 4.3 is a big jump; the move to
4.0 can be especially disruptive (
https://developer.jboss.org/wiki/HibernateCoreMigrationGuide40).

A fresh compile will show you those problems better.

Anyway, DTDEntityResolver has moved packaging as part of the initial OSGi
efforts to org.hibernate.internal.util.xml.DTDEntityResolver

On Thu, Oct 23, 2014 at 3:53 PM, Adriano Santos <adriano.nego at gmail.com>
wrote:

> Hi, Gunnar.
>
>  I updated my POM.XML with:
>
> <dependencies>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.16</version>
> </dependency>
> <dependency>
>         <groupId>org.hibernate</groupId>
>         <artifactId>hibernate-annotations</artifactId>
>         <version>3.5.6-Final</version>
>     </dependency>
>     <dependency>
>   <groupId>org.codehaus.jackson</groupId>
>   <artifactId>jackson-mapper-asl</artifactId>
>   <version>1.9.13</version>
> </dependency>
>     <dependency>
>         <groupId>org.hibernate</groupId>
>         <artifactId>hibernate-core</artifactId>
>         <version>4.3.6.Final</version>
>     </dependency>
>     <dependency>
>         <groupId>javassist</groupId>
>         <artifactId>javassist</artifactId>
>         <version>3.12.1.GA</version>
>     </dependency>
>
>     <dependency>
>         <groupId>org.slf4j</groupId>
>         <artifactId>slf4j-log4j12</artifactId>
>         <version>1.5.8</version>
>     </dependency>
>
>   <dependency>
> <groupId>org.postgresql</groupId>
> <artifactId>postgresql</artifactId>
> <version>9.3-1102-jdbc41</version>
> </dependency>
>
>
> And I try to run my sample and I received this message error:
>  Initial SessionFactory creation failed.java.lang.NoClassDefFoundError:
> org/hibernate/util/DTDEntityResolver
>
>
> On Thu, Oct 23, 2014 at 5:13 PM, Gunnar Morling <gunnar at hibernate.org>
> wrote:
>
> > Hi,
> >
> > The current version is 4.3.6.Final:
> >
> http://search.maven.org/#search|ga|1|g%3A%22org.hibernate%22%20AND%20v%3A%224.3.6.Final%22
> > <
> http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.hibernate%22%20AND%20v%3A%224.3.6.Final%22
> >
> >
> > Note that hibernate-annotations has been merged into hibernate-core as of
> > 3.6.
> >
> > Hth,
> >
> > --Gunnar
> >
> >
> > 2014-10-23 20:58 GMT+02:00 Adriano Santos <adriano.nego at gmail.com>:
> >
> >> Hi, Sanne.
> >>
> >>  Thanks for your support. So... Which is the version do you indicates?
> I'm
> >> using the Maven Repository and the last establish version is
> 3.5.6-Final.
> >> I'm using (without the dependencies):
> >>
> >>   - hibernate-annotations
> >>   - hibernate-core
> >>   - hibernate-entitymanager
> >>
> >> Ths for all.
> >>
> >>
> >> On Thu, Oct 23, 2014 at 1:12 PM, Sanne Grinovero <sanne at hibernate.org>
> >> wrote:
> >>
> >> > Hi Adriano,
> >> > that version is very old, it's going to be unlikely to find someone
> >> > able to help you. But it looks like a very interesting feature :-)
> >> >
> >> > If you could change your code and testing to use latest master from
> >> > github, or the latest stable version 4.3, then someone on this list
> >> > might volunteer to help you include the new JSON Type into the
> >> > Hibernate codebase, if you agree with that.
> >> >
> >> > Sanne
> >> >
> >> > On 23 October 2014 16:28, Adriano Santos <adriano.nego at gmail.com>
> >> wrote:
> >> > > Hi, everyone.
> >> > >
> >> > >  I'm trying to get a JSON value from Postgres DB, but I'm receiving
> >> this
> >> > > error:
> >> > >
> >> > > DefaultLoadEventListener:160 - Error performing load command
> >> > > org.hibernate.PropertyAccessException: could not set a field value
> by
> >> > > reflection setter of DTO.Processo._tramites
> >> > > at
> >> > >
> >> >
> >>
> org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:151)
> >> > >
> >> > > I saw that Hipernate don?t have a JSON Type yet, so I build a type
> for
> >> > this.
> >> > >
> >> > > I did a ?My UserType? (StringJsonUserType implements UserType) and
> >> > > JsonPostgreSQLDialect (extends PostgresPlusDialect). I insert data ,
> >> but
> >> > > when I try to get some value, i got this error return.
> >> > >
> >> > >  I using Hibernat version 3.5.6.final and postgresql-9.3-1102-jdbc.
> >> > >
> >> > > Anybody have some idea about whats happen and can I workaround this
> >> > problem?
> >> > >
> >> > > Best regards.
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > >
> >> > > Adriano Ara?jo Santos
> >> > >
> >> > >
> >> > > *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
> >> > > original."*
> >> > > _______________________________________________
> >> > > hibernate-dev mailing list
> >> > > hibernate-dev at lists.jboss.org
> >> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Adriano Ara?jo Santos
> >>
> >>
> >> *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
> >> original."*
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>
> >
> >
>
>
> --
>
> Adriano Ara?jo Santos
>
>
> *"A mente que se abre a uma nova id?ia jamais voltar? ao seu tamanho
> original."*
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From steve at hibernate.org  Fri Oct 24 10:30:15 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Fri, 24 Oct 2014 09:30:15 -0500
Subject: [hibernate-dev] HHH-7610 Embedded: emptiness and dirtiness
In-Reply-To: <CALt0+o9RBHxiQW6URtgv7C5VBm1gjmUb8VhR5gE+ijpBSSSo7w@mail.gmail.com>
References: <CALt0+o_tayrMBQSZAx6946=pS7mOx287zFm2jBBWDB1-sFxr+w@mail.gmail.com>
	<CALt0+o9UJqpRJAa1+zZWoGSeXhGrbw89XBDsHE2E0yZx9ekc+w@mail.gmail.com>
	<CAFdSV9ukurNLdy82eE+rzgSb+DU41ufE-M7Yuqf7vew27ErEWA@mail.gmail.com>
	<CALt0+o9RBHxiQW6URtgv7C5VBm1gjmUb8VhR5gE+ijpBSSSo7w@mail.gmail.com>
Message-ID: <CAFdSV9sSmoSaTNCz_kBQ8VfKxvmPd1urTYU1G30y=er6N0oVgQ@mail.gmail.com>

I personally do not think it is correct to change the existing behavior
here, but I do not have a strong feeling for it.  I just believe that you
don't change historical behaviors that work as designed except as protected
by the setting to enable the new feature or improvement.

I really do not get the performance point you are making.  You mean because
of potential "extra" updates?  Well, again that is the design, and from
that perspective the app is misusing Hibernate.  Whether the design is
"correct" and whether the code properly works according to the design are 2
totally different discussions.

As for 4.3.x, for me that again goes back to this not being a bug.  4.3 is
a maintenance branch now, meaning it should only include bug fixes in any
releases.  So IMO this should not be part of the 4.3 branch.  I do want to
have a discussion about possibly doing another 4.x release as a sort of
incremental stepping stone to the 5.0 work on master.  The plan is to have
that discussion next week, since quite a few of us will be meeting face to
face.  I can see this being a part of that new branch if we end up doing it.


On Fri, Oct 24, 2014 at 9:14 AM, Guillaume Smet <guillaume.smet at gmail.com>
wrote:

> Hi Steve,
>
> On Fri, Oct 24, 2014 at 3:08 PM, Steve Ebersole <steve at hibernate.org>
> wrote:
> > As to your specific question, yes I think what you propose makes sense.
> > Namely, if this setting is enabled, I think it is reasonable to treat a
> null
> > component reference and an empty component reference as equivalent.
>
> Thanks for your feedback!
>
> Isn't it even more reasonable to treat null and empty as equivalent in
> the current behavior?
>
> Currently, we have:
> Entity with empty embedded -> save + get -> Entity with null
> so we are considering that empty embedded and null are the exact same
> things.
>
> If you set again the embedded to an empty one for various reasons,
> it's going to be considered dirty again which is IMHO wrong.
>
> I won't argue a lot about this as we will run all our applications
> with this setting enabled but I think it will be a performance
> improvement to fix this in the other case too.
>




>
> Note that I'm not very familiar with these things so I might have
> missed an obvious point.
>
> We are going to fix the things you commented on Github, work on the
> documentation and wait for your feedback on this specific point before
> going further on this particular issue.
>
> It would be nice to have it in the next 4.3.x release as we have an
> application which is particularly affected by this issue.
>
> --
> Guillaume
>

From guillaume.smet at gmail.com  Fri Oct 24 12:38:30 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Fri, 24 Oct 2014 18:38:30 +0200
Subject: [hibernate-dev] HHH-7610 Embedded: emptiness and dirtiness
In-Reply-To: <CAFdSV9sSmoSaTNCz_kBQ8VfKxvmPd1urTYU1G30y=er6N0oVgQ@mail.gmail.com>
References: <CALt0+o_tayrMBQSZAx6946=pS7mOx287zFm2jBBWDB1-sFxr+w@mail.gmail.com>
	<CALt0+o9UJqpRJAa1+zZWoGSeXhGrbw89XBDsHE2E0yZx9ekc+w@mail.gmail.com>
	<CAFdSV9ukurNLdy82eE+rzgSb+DU41ufE-M7Yuqf7vew27ErEWA@mail.gmail.com>
	<CALt0+o9RBHxiQW6URtgv7C5VBm1gjmUb8VhR5gE+ijpBSSSo7w@mail.gmail.com>
	<CAFdSV9sSmoSaTNCz_kBQ8VfKxvmPd1urTYU1G30y=er6N0oVgQ@mail.gmail.com>
Message-ID: <CALt0+o9eMaJJNA2K4Xepx77d4ptSryhFx=G63PW9xjL06e53Hg@mail.gmail.com>

On Fri, Oct 24, 2014 at 4:30 PM, Steve Ebersole <steve at hibernate.org> wrote:
> As for 4.3.x, for me that again goes back to this not being a bug.  4.3 is a
> maintenance branch now, meaning it should only include bug fixes in any
> releases.  So IMO this should not be part of the 4.3 branch.  I do want to
> have a discussion about possibly doing another 4.x release as a sort of
> incremental stepping stone to the 5.0 work on master.  The plan is to have
> that discussion next week, since quite a few of us will be meeting face to
> face.  I can see this being a part of that new branch if we end up doing it.

I kinda agree with you on the 4.3.x part even if it doesn't meet my
business requirements but I agree this is my problem!

But... I can't see the consistency of the current behavior:
- if your embedded is empty, you get null from the ORM when you save and get it
- but hey null and empty embedded are not the same so I will save your
entity again if you set it to an empty embedded

So my point is:
1/ I agree that changing the fact that Hibernate returns empty
components instead of null needs a configuration thingy in the 4.x
branch; I would personnally like it to be the default in 5.x;
2/ but the 2nd statement above should really be changed IMHO to be
consistent with the 1st one.

Anyway we'll try to come up with a sensible patch in the next few days
and we then will be able to decide what to do with it!

-- 
Guillaume

From steve at hibernate.org  Wed Oct 29 05:13:01 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Wed, 29 Oct 2014 04:13:01 -0500
Subject: [hibernate-dev] ORM master
Message-ID: <CAFdSV9t1oz+sBhqRFz8rDgVvQ=M2tFX1UCF10XSSQVuAGwfbNA@mail.gmail.com>

Per the face to face discussion yesterday (I'll send out more details
later) I am working on branching master off to a new "metamodel" dev branch
and priming a "new master" from 4.3 (the basic idea being to start work on
a more targeted 5.0).

Part of this is of course a massive change to the state of master upstream.
If anyone needs me to wait before starting this please let me know
immediately.  Thanks.

From steve at hibernate.org  Wed Oct 29 06:22:37 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Wed, 29 Oct 2014 05:22:37 -0500
Subject: [hibernate-dev] ORM master
In-Reply-To: <CAFdSV9t1oz+sBhqRFz8rDgVvQ=M2tFX1UCF10XSSQVuAGwfbNA@mail.gmail.com>
References: <CAFdSV9t1oz+sBhqRFz8rDgVvQ=M2tFX1UCF10XSSQVuAGwfbNA@mail.gmail.com>
Message-ID: <CAFdSV9uWYCY2gG+PhfH65tqp63JbcBiCEprrOcaRKHyaJFLebQ@mail.gmail.com>

I just noticed that the old metamodel branch was still around upstream.  So
far I have:

1) moved upstream/metamodel -> upstream/metamodel-old
2) deleted upstream/metamodel
3) moved upstream/master -> upstream/metamodel

I'll wait a few minutes still before deleting master and re-priming it from
4.3


On Wed, Oct 29, 2014 at 4:13 AM, Steve Ebersole <steve at hibernate.org> wrote:

> Per the face to face discussion yesterday (I'll send out more details
> later) I am working on branching master off to a new "metamodel" dev branch
> and priming a "new master" from 4.3 (the basic idea being to start work on
> a more targeted 5.0).
>
> Part of this is of course a massive change to the state of master
> upstream. If anyone needs me to wait before starting this please let me
> know immediately.  Thanks.
>

From steve at hibernate.org  Wed Oct 29 07:00:02 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Wed, 29 Oct 2014 06:00:02 -0500
Subject: [hibernate-dev] ORM master
In-Reply-To: <CAFdSV9uWYCY2gG+PhfH65tqp63JbcBiCEprrOcaRKHyaJFLebQ@mail.gmail.com>
References: <CAFdSV9t1oz+sBhqRFz8rDgVvQ=M2tFX1UCF10XSSQVuAGwfbNA@mail.gmail.com>
	<CAFdSV9uWYCY2gG+PhfH65tqp63JbcBiCEprrOcaRKHyaJFLebQ@mail.gmail.com>
Message-ID: <CAFdSV9vE3k0v99NeS4PT_+=4ypSf4ko6FM981Bag=0aq1yc=jw@mail.gmail.com>

Ok, all done now.  So at this point:

1) upstream/metamodel-old is the "metamodel" code as of the point before
when we merged it to master
2) upstream/metamodel is the current state of metamodel work
3) upstream/master is currently the same as 4.3.  It is the base from which
I will start the discussed simplified 5.0 development



On Wed, Oct 29, 2014 at 5:22 AM, Steve Ebersole <steve at hibernate.org> wrote:

> I just noticed that the old metamodel branch was still around upstream.
> So far I have:
>
> 1) moved upstream/metamodel -> upstream/metamodel-old
> 2) deleted upstream/metamodel
> 3) moved upstream/master -> upstream/metamodel
>
> I'll wait a few minutes still before deleting master and re-priming it
> from 4.3
>
>
> On Wed, Oct 29, 2014 at 4:13 AM, Steve Ebersole <steve at hibernate.org>
> wrote:
>
>> Per the face to face discussion yesterday (I'll send out more details
>> later) I am working on branching master off to a new "metamodel" dev branch
>> and priming a "new master" from 4.3 (the basic idea being to start work on
>> a more targeted 5.0).
>>
>> Part of this is of course a massive change to the state of master
>> upstream. If anyone needs me to wait before starting this please let me
>> know immediately.  Thanks.
>>
>
>

From steve at hibernate.org  Wed Oct 29 07:00:38 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Wed, 29 Oct 2014 06:00:38 -0500
Subject: [hibernate-dev] ORM master
In-Reply-To: <CAFdSV9vE3k0v99NeS4PT_+=4ypSf4ko6FM981Bag=0aq1yc=jw@mail.gmail.com>
References: <CAFdSV9t1oz+sBhqRFz8rDgVvQ=M2tFX1UCF10XSSQVuAGwfbNA@mail.gmail.com>
	<CAFdSV9uWYCY2gG+PhfH65tqp63JbcBiCEprrOcaRKHyaJFLebQ@mail.gmail.com>
	<CAFdSV9vE3k0v99NeS4PT_+=4ypSf4ko6FM981Bag=0aq1yc=jw@mail.gmail.com>
Message-ID: <CAFdSV9uP_OL2z34Jr9sbXdQH1PC=zdbW+4JJjawDjBdm9uNCWw@mail.gmail.com>

FYI, does anyone need metamodel-old anymore?  Can I just delete that one
upstream?

On Wed, Oct 29, 2014 at 6:00 AM, Steve Ebersole <steve at hibernate.org> wrote:

> Ok, all done now.  So at this point:
>
> 1) upstream/metamodel-old is the "metamodel" code as of the point before
> when we merged it to master
> 2) upstream/metamodel is the current state of metamodel work
> 3) upstream/master is currently the same as 4.3.  It is the base from
> which I will start the discussed simplified 5.0 development
>
>
>
> On Wed, Oct 29, 2014 at 5:22 AM, Steve Ebersole <steve at hibernate.org>
> wrote:
>
>> I just noticed that the old metamodel branch was still around upstream.
>> So far I have:
>>
>> 1) moved upstream/metamodel -> upstream/metamodel-old
>> 2) deleted upstream/metamodel
>> 3) moved upstream/master -> upstream/metamodel
>>
>> I'll wait a few minutes still before deleting master and re-priming it
>> from 4.3
>>
>>
>> On Wed, Oct 29, 2014 at 4:13 AM, Steve Ebersole <steve at hibernate.org>
>> wrote:
>>
>>> Per the face to face discussion yesterday (I'll send out more details
>>> later) I am working on branching master off to a new "metamodel" dev branch
>>> and priming a "new master" from 4.3 (the basic idea being to start work on
>>> a more targeted 5.0).
>>>
>>> Part of this is of course a massive change to the state of master
>>> upstream. If anyone needs me to wait before starting this please let me
>>> know immediately.  Thanks.
>>>
>>
>>
>

From gbadner at redhat.com  Thu Oct 30 07:12:27 2014
From: gbadner at redhat.com (Gail Badner)
Date: Thu, 30 Oct 2014 07:12:27 -0400 (EDT)
Subject: [hibernate-dev] Preparing to release 4.3.7 and 4.2.16
Message-ID: <488095557.2736203.1414667547526.JavaMail.zimbra@redhat.com>

Please do not push anything to 4.2 and 4.3 branches until they are released.
Thanks,
Gail

From guillaume.smet at gmail.com  Thu Oct 30 09:44:14 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Thu, 30 Oct 2014 14:44:14 +0100
Subject: [hibernate-dev] Native query and auto-flush
Message-ID: <CALt0+o-9=Zs2mRTA6HyD=wE4TqBa9mDD7xr+UigJi-ZrbSkAUw@mail.gmail.com>

Hi!

Starting with HHH-8487, when we execute a native query, an auto-flush
is executed (and might be limited with addSynchronizedEntityClass and
allegates).

While I understand the rationale of this change, we are having a few
issues with this when the transaction opened is read-only which is the
case for all our read-only queries: Hibernate tries to flush the dirty
entities in a read-only transaction and fails.

The heart of the issue here is that we have dirty entities which
shouldn't be dirty (see my post on embedded and dirtiness) but I'm
wondering if it's a behavior which was missed by this patch or
something intentional. So I thought I might as well report it.

-- 
Guillaume

From guillaume.smet at gmail.com  Thu Oct 30 09:44:37 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Thu, 30 Oct 2014 14:44:37 +0100
Subject: [hibernate-dev] Search - HSEARCH-1580 - Dependency graph
In-Reply-To: <CALt0+o8bU+JrDid+EGNhSqoNN=0sYozwffuM8yh2BiLcGMNoyw@mail.gmail.com>
References: <CALt0+o8dXJYwKfk8mGwS=9-3bmn1CWvbaV6j771PyYnYcLCUTw@mail.gmail.com>
	<68C8A0F4-69D1-4C07-B8B7-147813F3EC51@hibernate.org>
	<CALt0+o9kxATDTPBe7ROT-1=k7pZay_vaBj4_gOmxLQ=H6iTRPw@mail.gmail.com>
	<CALt0+o-MKSacsh9=sHaV0aQRRCkPqVdhKSiBiLoECdq9JhpiTw@mail.gmail.com>
	<CAFm4XO1NSh3wJafeU9gWV-eVw6zs5XataU4Y1BGxWF+eSkuizA@mail.gmail.com>
	<CALt0+o9GZmG7DyVAHpYJH92WfNBxat_8GPvX1mHS1fpdrmKumQ@mail.gmail.com>
	<CAFm4XO1LKAX-Dw0a5_cM12LXnQ6fjDMnoOu1K5iiRXkUgVLNtg@mail.gmail.com>
	<CALt0+o8bU+JrDid+EGNhSqoNN=0sYozwffuM8yh2BiLcGMNoyw@mail.gmail.com>
Message-ID: <CALt0+o84aqyLvP_0eq8swgidrFhEoMTvr=Y6V5YpL+Tis6CVHA@mail.gmail.com>

Hi Sanne,

On Fri, Aug 22, 2014 at 11:25 PM, Guillaume Smet
<guillaume.smet at gmail.com> wrote:
> We'll have the bandwidth starting from september 15th so if we have a
> release then, we'll start playing with 5.

If a new alpha of 5 can be released soon with the above fix, we will
be able to start using it in our in progress apps to provide feedback
on real apps.

Thanks!

-- 
Guillaume

From steve at hibernate.org  Thu Oct 30 09:56:03 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Thu, 30 Oct 2014 08:56:03 -0500
Subject: [hibernate-dev] Native query and auto-flush
In-Reply-To: <CALt0+o-9=Zs2mRTA6HyD=wE4TqBa9mDD7xr+UigJi-ZrbSkAUw@mail.gmail.com>
References: <CALt0+o-9=Zs2mRTA6HyD=wE4TqBa9mDD7xr+UigJi-ZrbSkAUw@mail.gmail.com>
Message-ID: <CAFdSV9vCZXbAFOdqx0G7O0DDDaO11NTn4vccE6sNmTrx6gF0ig@mail.gmail.com>

Personally having entities dirtied as part of a read-only
transaction sounds like an application bug to me.  We could try to detect a
read-only transaction state (not sure how we'd do that across all cases)
and circumvent the flush there, but that would add unnecessary overhead to
applications that do the right thing.

On Thu, Oct 30, 2014 at 8:44 AM, Guillaume Smet <guillaume.smet at gmail.com>
wrote:

> Hi!
>
> Starting with HHH-8487, when we execute a native query, an auto-flush
> is executed (and might be limited with addSynchronizedEntityClass and
> allegates).
>
> While I understand the rationale of this change, we are having a few
> issues with this when the transaction opened is read-only which is the
> case for all our read-only queries: Hibernate tries to flush the dirty
> entities in a read-only transaction and fails.
>
> The heart of the issue here is that we have dirty entities which
> shouldn't be dirty (see my post on embedded and dirtiness) but I'm
> wondering if it's a behavior which was missed by this patch or
> something intentional. So I thought I might as well report it.
>
> --
> Guillaume
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

From guillaume.smet at gmail.com  Thu Oct 30 10:51:22 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Thu, 30 Oct 2014 15:51:22 +0100
Subject: [hibernate-dev] Native query and auto-flush
In-Reply-To: <CAFdSV9vCZXbAFOdqx0G7O0DDDaO11NTn4vccE6sNmTrx6gF0ig@mail.gmail.com>
References: <CALt0+o-9=Zs2mRTA6HyD=wE4TqBa9mDD7xr+UigJi-ZrbSkAUw@mail.gmail.com>
	<CAFdSV9vCZXbAFOdqx0G7O0DDDaO11NTn4vccE6sNmTrx6gF0ig@mail.gmail.com>
Message-ID: <CALt0+o9=-342Mvfuv2J7Rqup=zNTN+vEX7HDuMnaCXbmpj3Tyg@mail.gmail.com>

On Thu, Oct 30, 2014 at 2:56 PM, Steve Ebersole <steve at hibernate.org> wrote:
> Personally having entities dirtied as part of a read-only transaction sounds
> like an application bug to me.  We could try to detect a read-only
> transaction state (not sure how we'd do that across all cases) and
> circumvent the flush there, but that would add unnecessary overhead to
> applications that do the right thing.

They aren't dirtied as part of the read-only transaction per se but I
agree with you it's more an application bug (it's due to the way we're
dealing with empty embedded).

Just wanted to report it in case it was easy and free to test the
transaction status!

From steve at hibernate.org  Thu Oct 30 11:44:23 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Thu, 30 Oct 2014 10:44:23 -0500
Subject: [hibernate-dev] Hibernate ORM master - 5.0
Message-ID: <CAFdSV9t+yvsyAsnY9+rUw=x=t8xX2wVAeMErADqQ8ao_SPbbaQ@mail.gmail.com>

It was decided that the massive work for 5.0 including metamodel and all
the other changes was just taking too long, and that we'd split that work
up into a number of intermediate versions.  I wanted to highlight the
proposed breakdown and solidify the roadmaps.  The preliminary breakdown is
as follows:


   - 5.0
      - Java 6 or 7 (?)
      - EE 7 (JPA 2.1)
      - Wildfly 9
      - Timeline : Spring 2015
      - Required development
         - Transition to new bootstrapping APIs
         - MetadataSources, contributors, builders, etc for building
            SessionFactory
            - Keep Configuration as a migration aid, but align its
            processing and assumptions to follow new APIs
            - New naming strategy approach (implicit and physical split)
         - Pick "important" features from  metamodel work based on new
         bootstrapping API
            - automatic quoting of identifiers that are keywords
            - ???
         - Performance improvements
         - Cachng SPI changes based on feedback from Ehcahce and Infinispan
            - EntityKey proposal
            - Explore unifying entry keys for actual cache provider, cache
            SPI (CacheKey) and persistence-context (EntityKey)
            - Infinispan improvements, especially in local mode.  Will
            require integrating a new Infinispan version and possible
changes to
            hibernate-infinispan
            - ???
         - OGM integration
            - "after persisters built" hook
               - others?
            - Java 8 type support
            - Date/Time
            - Optional
         - Java 9 type support
            - Money/Currency
         - Optional development (as time, resources allow)
         - Discriminator based multitenancy
         - JAXB instead of dom4j.
         - extended orm.xml xsd, deprecating hbm.xml format
         - Jandex usage
         - JdbcSession
         - Hibernate Spatial integration (depends on level of dependence on
         metamodel)
      - 5.1
      - Java 6 or 7 (?)
      - EE 7 (JPA 2.1)
      - Widfly 9, or 10
      - Timeline : TBD (Fall 2016?)
      - Required development
         - slips from 5.0
         - new HQL parser
            - Antlr 3 or 4?
            - unified SQL generation? or limit to HQL parsing?
         - Optional development (as time, resources allow)
         - extend JPA criteria API with support for constructs from
         Hibernate's legacy criteria API
         - extend JPA criteria API with fluent support
      - Possibly - Override EAGER fetching with LAZY (fetch profiles, HQL,
      etc)
   - 5.2
      - (if needed)
      - Java 6 or 7 (?)
      - EE 7 (JPA 2.1)
      - Widfly 9, or 10
      - Required development
         - splits from 5.1
      - 6.0
      - SE and EE support levels TBD, but at least SE 8
      - Required development
         - metamodel


One additional consideration... I have been told (have not verified the
details yet myself) that Hibernate ORM will currently not run in Java 8 at
least in part because dom4j will not work in Java 8 (maybe just the version
we use?  again, have not verified details yet).  If running 5.x versions of
Hibernate in Java 8 is important to anyone, we might need to increase the
priority of moving to JAXB over dom4j.

From steve at hibernate.org  Thu Oct 30 11:45:56 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Thu, 30 Oct 2014 10:45:56 -0500
Subject: [hibernate-dev] Native query and auto-flush
In-Reply-To: <CALt0+o9=-342Mvfuv2J7Rqup=zNTN+vEX7HDuMnaCXbmpj3Tyg@mail.gmail.com>
References: <CALt0+o-9=Zs2mRTA6HyD=wE4TqBa9mDD7xr+UigJi-ZrbSkAUw@mail.gmail.com>
	<CAFdSV9vCZXbAFOdqx0G7O0DDDaO11NTn4vccE6sNmTrx6gF0ig@mail.gmail.com>
	<CALt0+o9=-342Mvfuv2J7Rqup=zNTN+vEX7HDuMnaCXbmpj3Tyg@mail.gmail.com>
Message-ID: <CAFdSV9tTFbtogTybWx2FK7_KSBsN7ce0aVx4p1cKmmL6QJs8jQ@mail.gmail.com>

Guillaume, it depends unfortunately.  In distributed cases, checking the
status of a transaction could mean remote calls.  That's why I was saying
I'd rather not have the unnecessary overhead if not needed.

On Thu, Oct 30, 2014 at 9:51 AM, Guillaume Smet <guillaume.smet at gmail.com>
wrote:

> On Thu, Oct 30, 2014 at 2:56 PM, Steve Ebersole <steve at hibernate.org>
> wrote:
> > Personally having entities dirtied as part of a read-only transaction
> sounds
> > like an application bug to me.  We could try to detect a read-only
> > transaction state (not sure how we'd do that across all cases) and
> > circumvent the flush there, but that would add unnecessary overhead to
> > applications that do the right thing.
>
> They aren't dirtied as part of the read-only transaction per se but I
> agree with you it's more an application bug (it's due to the way we're
> dealing with empty embedded).
>
> Just wanted to report it in case it was easy and free to test the
> transaction status!
>

From sanne at hibernate.org  Thu Oct 30 11:48:44 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Thu, 30 Oct 2014 16:48:44 +0100
Subject: [hibernate-dev] Search - HSEARCH-1580 - Dependency graph
In-Reply-To: <CALt0+o84aqyLvP_0eq8swgidrFhEoMTvr=Y6V5YpL+Tis6CVHA@mail.gmail.com>
References: <CALt0+o8dXJYwKfk8mGwS=9-3bmn1CWvbaV6j771PyYnYcLCUTw@mail.gmail.com>
	<68C8A0F4-69D1-4C07-B8B7-147813F3EC51@hibernate.org>
	<CALt0+o9kxATDTPBe7ROT-1=k7pZay_vaBj4_gOmxLQ=H6iTRPw@mail.gmail.com>
	<CALt0+o-MKSacsh9=sHaV0aQRRCkPqVdhKSiBiLoECdq9JhpiTw@mail.gmail.com>
	<CAFm4XO1NSh3wJafeU9gWV-eVw6zs5XataU4Y1BGxWF+eSkuizA@mail.gmail.com>
	<CALt0+o9GZmG7DyVAHpYJH92WfNBxat_8GPvX1mHS1fpdrmKumQ@mail.gmail.com>
	<CAFm4XO1LKAX-Dw0a5_cM12LXnQ6fjDMnoOu1K5iiRXkUgVLNtg@mail.gmail.com>
	<CALt0+o8bU+JrDid+EGNhSqoNN=0sYozwffuM8yh2BiLcGMNoyw@mail.gmail.com>
	<CALt0+o84aqyLvP_0eq8swgidrFhEoMTvr=Y6V5YpL+Tis6CVHA@mail.gmail.com>
Message-ID: <CAFm4XO0s4_QMKMYu_TEzsQUpncKOseCnb8kSB-Cxqni1kghazA@mail.gmail.com>

Hi Guillaume,
excellent!

I think 5.0.0.Alpha7 already includes your fix, but we're releasing
Beta1 in one or two days.
We didn't do Beta releases so far as we where hoping to make some more
API changes in the 5.0 sprint but we just decided (we're having a face
to face meeting this week) to scrap that and aim at a quicker release
plan, so we soon plan to go for CR releases. So I think it's quite
stable already, but your feedback would be very timely to validate
that.

Sanne

On 30 October 2014 14:44, Guillaume Smet <guillaume.smet at gmail.com> wrote:
> Hi Sanne,
>
> On Fri, Aug 22, 2014 at 11:25 PM, Guillaume Smet
> <guillaume.smet at gmail.com> wrote:
>> We'll have the bandwidth starting from september 15th so if we have a
>> release then, we'll start playing with 5.
>
> If a new alpha of 5 can be released soon with the above fix, we will
> be able to start using it in our in progress apps to provide feedback
> on real apps.
>
> Thanks!
>
> --
> Guillaume

From davide at hibernate.org  Thu Oct 30 14:26:48 2014
From: davide at hibernate.org (Davide D'Alto)
Date: Thu, 30 Oct 2014 19:26:48 +0100
Subject: [hibernate-dev] Hibernate OGM 4.1.0.Beta8 is out: Optimistic
	locking and performance improvement
Message-ID: <CANoTJYM8atD-D6iYYSJzfFD19aV-mMS-QOgXBg8nE4Q9HrSDVg@mail.gmail.com>

We are getting closer to a final release and this version is mainly about
improving general performance and reducing the amount of round trips to the
datastore.

We also added optimistic locking support for datastores which provide
atomic find-and-update operations.

You can read more about it in the blog post:
http://in.relation.to/Bloggers/HibernateOGM410Beta8IsOutOptimisticLockingAndPerformanceImprovement

Cheers,
Davide

From golovnin at gmx.net  Thu Oct 30 18:05:48 2014
From: golovnin at gmx.net (Andrej Golovnin)
Date: Thu, 30 Oct 2014 23:05:48 +0100
Subject: [hibernate-dev] Closed pull requests
Message-ID: <84D5AADC-23D4-4377-AED7-1EB88869FF30@gmx.net>

Hello Steve,

you have closed my pull requests and
pull requests from others too without any comment.

Should we create a new pull requests for the "new master" branch?
Or should we just forget all the time and the work we have invested
to create those pull requests and stop submitting any new pull requests
in the future?

Best regards,
Andrej Golovnin

From gbadner at redhat.com  Thu Oct 30 18:38:49 2014
From: gbadner at redhat.com (Gail Badner)
Date: Thu, 30 Oct 2014 18:38:49 -0400 (EDT)
Subject: [hibernate-dev] Hibernate ORM 4.3.7.Final and 4.2.16.Final Released
In-Reply-To: <535526383.3181554.1414708602278.JavaMail.zimbra@redhat.com>
Message-ID: <2000580524.3181989.1414708729309.JavaMail.zimbra@redhat.com>

I've finished with the releases, including uploading everthing. I'm having trouble setting up the weblog entry in in.relation.to for some reason. I'll blog about the releases tomorrow.
Regards,
Gail

From steve at hibernate.org  Thu Oct 30 18:43:53 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Thu, 30 Oct 2014 17:43:53 -0500
Subject: [hibernate-dev] Closed pull requests
In-Reply-To: <E1036AAB-B803-422A-9E87-89D70071CE46@gmx.net>
References: <84D5AADC-23D4-4377-AED7-1EB88869FF30@gmx.net>
	<CAFdSV9tM+O-v3R2JBEUa_-TQ=5ieWYrU6232uWBFPFYWrVj=7Q@mail.gmail.com>
	<E1036AAB-B803-422A-9E87-89D70071CE46@gmx.net>
Message-ID: <CAFdSV9sdS1qpPAivmbkrPL0hkrqOS+Q=NQBQLn818yu_Du9+2w@mail.gmail.com>

Well telling me/us which PRs got closed would be a good first step :)

Overall, checking that the PR still applies is a good idea too.

On Thu, Oct 30, 2014 at 5:34 PM, Andrej Golovnin <golovnin at gmx.net> wrote:

>
> > On 30.10.2014, at 23:15, Steve Ebersole <steve at hibernate.org> wrote:
> >
> > Well maybe rather than being hurt and sensitive maybe just understand
> that it was not intentional.  GitHub automatically closed them.  It was
> simply a mistake.
> >
> > Or be sensitive and threatening about it.  Whichever you think helps you
> best ;)
>
> This does not answer my 1. question. :-) What is the best way to proceed?
> Are you going to reopen the pull requests or should we create new requests?
>
> I think, that at least one of my patches must be modified to be applied to
> the "new master".
>
> Any clear small guide, what we (contributors) should do to reopen the pull
> requests
> or a small info that you will care about the closed pull requests
> and we should sit down, relax and wait until you are done, would be really
> helpful.
>
> >
> > On Oct 30, 2014 11:05 PM, "Andrej Golovnin" <golovnin at gmx.net> wrote:
> > Hello Steve,
> >
> > you have closed my pull requests and
> > pull requests from others too without any comment.
> >
> > Should we create a new pull requests for the "new master" branch?
> > Or should we just forget all the time and the work we have invested
> > to create those pull requests and stop submitting any new pull requests
> > in the future?
> >
> > Best regards,
> > Andrej Golovnin
>
>

From golovnin at gmx.net  Fri Oct 31 01:39:57 2014
From: golovnin at gmx.net (Andrej Golovnin)
Date: Fri, 31 Oct 2014 06:39:57 +0100
Subject: [hibernate-dev] Closed pull requests
In-Reply-To: <CAFdSV9sdS1qpPAivmbkrPL0hkrqOS+Q=NQBQLn818yu_Du9+2w@mail.gmail.com>
References: <84D5AADC-23D4-4377-AED7-1EB88869FF30@gmx.net>
	<CAFdSV9tM+O-v3R2JBEUa_-TQ=5ieWYrU6232uWBFPFYWrVj=7Q@mail.gmail.com>
	<E1036AAB-B803-422A-9E87-89D70071CE46@gmx.net>
	<CAFdSV9sdS1qpPAivmbkrPL0hkrqOS+Q=NQBQLn818yu_Du9+2w@mail.gmail.com>
Message-ID: <7B4B4720-5C93-43C7-BDD8-F515CAA1A4F6@gmx.net>


> On 30.10.2014, at 23:43, Steve Ebersole <steve at hibernate.org> wrote:
> 
> Well telling me/us which PRs got closed would be a good first step :)

Here are mines:

https://github.com/hibernate/hibernate-orm/pull/779
https://github.com/hibernate/hibernate-orm/pull/782
https://github.com/hibernate/hibernate-orm/pull/777

> 
> Overall, checking that the PR still applies is a good idea too.

I'll do that on the weekend.

> 
> On Thu, Oct 30, 2014 at 5:34 PM, Andrej Golovnin <golovnin at gmx.net> wrote:
> 
> > On 30.10.2014, at 23:15, Steve Ebersole <steve at hibernate.org> wrote:
> >
> > Well maybe rather than being hurt and sensitive maybe just understand that it was not intentional.  GitHub automatically closed them.  It was simply a mistake.
> >
> > Or be sensitive and threatening about it.  Whichever you think helps you best ;)
> 
> This does not answer my 1. question. :-) What is the best way to proceed?
> Are you going to reopen the pull requests or should we create new requests?
> 
> I think, that at least one of my patches must be modified to be applied to the "new master".
> 
> Any clear small guide, what we (contributors) should do to reopen the pull requests
> or a small info that you will care about the closed pull requests
> and we should sit down, relax and wait until you are done, would be really helpful.
> 
> >
> > On Oct 30, 2014 11:05 PM, "Andrej Golovnin" <golovnin at gmx.net> wrote:
> > Hello Steve,
> >
> > you have closed my pull requests and
> > pull requests from others too without any comment.
> >
> > Should we create a new pull requests for the "new master" branch?
> > Or should we just forget all the time and the work we have invested
> > to create those pull requests and stop submitting any new pull requests
> > in the future?
> >
> > Best regards,
> > Andrej Golovnin
> 
> 



From golovnin at gmx.net  Fri Oct 31 03:11:03 2014
From: golovnin at gmx.net (Andrej Golovnin)
Date: Fri, 31 Oct 2014 08:11:03 +0100
Subject: [hibernate-dev] Closed pull requests
In-Reply-To: <7B4B4720-5C93-43C7-BDD8-F515CAA1A4F6@gmx.net>
References: <84D5AADC-23D4-4377-AED7-1EB88869FF30@gmx.net>
	<CAFdSV9tM+O-v3R2JBEUa_-TQ=5ieWYrU6232uWBFPFYWrVj=7Q@mail.gmail.com>
	<E1036AAB-B803-422A-9E87-89D70071CE46@gmx.net>
	<CAFdSV9sdS1qpPAivmbkrPL0hkrqOS+Q=NQBQLn818yu_Du9+2w@mail.gmail.com>,
	<7B4B4720-5C93-43C7-BDD8-F515CAA1A4F6@gmx.net>
Message-ID: <trinity-05f1e404-af05-4120-8524-076545bd3351-1414739463038@3capp-gmx-bs59>


> Here are mines:

I mean from me. I should not write emails early in the morning. I was still asleep. :-)

> https://github.com/hibernate/hibernate-orm/pull/779
> https://github.com/hibernate/hibernate-orm/pull/782
> https://github.com/hibernate/hibernate-orm/pull/777

> >
> > Overall, checking that the PR still applies is a good idea too.

> I'll do that on the weekend.


From steve at hibernate.org  Fri Oct 31 03:48:01 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Fri, 31 Oct 2014 02:48:01 -0500
Subject: [hibernate-dev] Closed pull requests
In-Reply-To: <trinity-05f1e404-af05-4120-8524-076545bd3351-1414739463038@3capp-gmx-bs59>
References: <84D5AADC-23D4-4377-AED7-1EB88869FF30@gmx.net>
	<CAFdSV9tM+O-v3R2JBEUa_-TQ=5ieWYrU6232uWBFPFYWrVj=7Q@mail.gmail.com>
	<E1036AAB-B803-422A-9E87-89D70071CE46@gmx.net>
	<CAFdSV9sdS1qpPAivmbkrPL0hkrqOS+Q=NQBQLn818yu_Du9+2w@mail.gmail.com>
	<7B4B4720-5C93-43C7-BDD8-F515CAA1A4F6@gmx.net>
	<trinity-05f1e404-af05-4120-8524-076545bd3351-1414739463038@3capp-gmx-bs59>
Message-ID: <CAFdSV9va1KmNFrx5S7v15F3oFR2_GMFim7acst8B0c8RhNrS7A@mail.gmail.com>

I knew what you meant.  I already re-opened those earlier

On Fri, Oct 31, 2014 at 2:11 AM, Andrej Golovnin <golovnin at gmx.net> wrote:

>
> > Here are mines:
>
> I mean from me. I should not write emails early in the morning. I was
> still asleep. :-)
>
> > https://github.com/hibernate/hibernate-orm/pull/779
> > https://github.com/hibernate/hibernate-orm/pull/782
> > https://github.com/hibernate/hibernate-orm/pull/777
>
> > >
> > > Overall, checking that the PR still applies is a good idea too.
>
> > I'll do that on the weekend.
>
>

From m.schipperheyn at gmail.com  Fri Oct 31 07:23:26 2014
From: m.schipperheyn at gmail.com (Marc Schipperheyn)
Date: Fri, 31 Oct 2014 12:23:26 +0100
Subject: [hibernate-dev] hibernate-dev Digest, Vol 100, Issue 8
In-Reply-To: <mailman.8737.1414734004.2753.hibernate-dev@lists.jboss.org>
References: <mailman.8737.1414734004.2753.hibernate-dev@lists.jboss.org>
Message-ID: <CAGvEgx4ejUwtYZzphD7YbAzQOx2KJWB9q=fLwZis7RMR55CTSg@mail.gmail.com>

I'm disappointed to see Spring 2015 on HSEARCH 5.0. Especially given how
long Lucene 4 has been in the field (October 2012). HSEARCH seemed to be at
a standstill for most of this year.

I would prefer to cut down on features to see it sooner, but I guess that's
not an option anymore. Also, I would say the risk is Lucene will run out of
4.x-es and move on to 5.x

Cheers,
Marc

From steve at hibernate.org  Fri Oct 31 07:25:11 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Fri, 31 Oct 2014 06:25:11 -0500
Subject: [hibernate-dev] Hibernate ORM master - 5.0
In-Reply-To: <CAFdSV9t+yvsyAsnY9+rUw=x=t8xX2wVAeMErADqQ8ao_SPbbaQ@mail.gmail.com>
References: <CAFdSV9t+yvsyAsnY9+rUw=x=t8xX2wVAeMErADqQ8ao_SPbbaQ@mail.gmail.com>
Message-ID: <CAFdSV9ta0-JE5PdVjO0XduX0mr=CPmtBBAf1CpDyj0q-Y8s8hA@mail.gmail.com>

One other thing I just realized wrt 5.0.  Currently moving to Jandex is
marked as an optional task.  However, part of the code Jandex is replacing
is that old hibernate-commons-annotations stuff.
 hibernate-commons-annotations suffers from a number of problems that we
maybe should consider increasing the priority of this task as well.  Most
problematic is the fact that it uses TCCL-based classloading.

On Thu, Oct 30, 2014 at 10:44 AM, Steve Ebersole <steve at hibernate.org>
wrote:

> It was decided that the massive work for 5.0 including metamodel and all
> the other changes was just taking too long, and that we'd split that work
> up into a number of intermediate versions.  I wanted to highlight the
> proposed breakdown and solidify the roadmaps.  The preliminary breakdown is
> as follows:
>
>
>    - 5.0
>       - Java 6 or 7 (?)
>       - EE 7 (JPA 2.1)
>       - Wildfly 9
>       - Timeline : Spring 2015
>       - Required development
>          - Transition to new bootstrapping APIs
>          - MetadataSources, contributors, builders, etc for building
>             SessionFactory
>             - Keep Configuration as a migration aid, but align its
>             processing and assumptions to follow new APIs
>             - New naming strategy approach (implicit and physical split)
>          - Pick "important" features from  metamodel work based on new
>          bootstrapping API
>             - automatic quoting of identifiers that are keywords
>             - ???
>          - Performance improvements
>          - Cachng SPI changes based on feedback from Ehcahce and
>             Infinispan
>             - EntityKey proposal
>             - Explore unifying entry keys for actual cache provider,
>             cache SPI (CacheKey) and persistence-context (EntityKey)
>             - Infinispan improvements, especially in local mode.  Will
>             require integrating a new Infinispan version and possible changes to
>             hibernate-infinispan
>             - ???
>          - OGM integration
>             - "after persisters built" hook
>                - others?
>             - Java 8 type support
>             - Date/Time
>             - Optional
>          - Java 9 type support
>             - Money/Currency
>          - Optional development (as time, resources allow)
>          - Discriminator based multitenancy
>          - JAXB instead of dom4j.
>          - extended orm.xml xsd, deprecating hbm.xml format
>          - Jandex usage
>          - JdbcSession
>          - Hibernate Spatial integration (depends on level of dependence
>          on metamodel)
>       - 5.1
>       - Java 6 or 7 (?)
>       - EE 7 (JPA 2.1)
>       - Widfly 9, or 10
>       - Timeline : TBD (Fall 2016?)
>       - Required development
>          - slips from 5.0
>          - new HQL parser
>             - Antlr 3 or 4?
>             - unified SQL generation? or limit to HQL parsing?
>          - Optional development (as time, resources allow)
>          - extend JPA criteria API with support for constructs from
>          Hibernate's legacy criteria API
>          - extend JPA criteria API with fluent support
>       - Possibly - Override EAGER fetching with LAZY (fetch profiles,
>       HQL, etc)
>    - 5.2
>       - (if needed)
>       - Java 6 or 7 (?)
>       - EE 7 (JPA 2.1)
>       - Widfly 9, or 10
>       - Required development
>          - splits from 5.1
>       - 6.0
>       - SE and EE support levels TBD, but at least SE 8
>       - Required development
>          - metamodel
>
>
> One additional consideration... I have been told (have not verified the
> details yet myself) that Hibernate ORM will currently not run in Java 8 at
> least in part because dom4j will not work in Java 8 (maybe just the version
> we use?  again, have not verified details yet).  If running 5.x versions of
> Hibernate in Java 8 is important to anyone, we might need to increase the
> priority of moving to JAXB over dom4j.
>
>

From sanne at hibernate.org  Fri Oct 31 09:59:52 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Fri, 31 Oct 2014 14:59:52 +0100
Subject: [hibernate-dev] hibernate-dev Digest, Vol 100, Issue 8
In-Reply-To: <CAGvEgx4ejUwtYZzphD7YbAzQOx2KJWB9q=fLwZis7RMR55CTSg@mail.gmail.com>
References: <mailman.8737.1414734004.2753.hibernate-dev@lists.jboss.org>
	<CAGvEgx4ejUwtYZzphD7YbAzQOx2KJWB9q=fLwZis7RMR55CTSg@mail.gmail.com>
Message-ID: <CAFm4XO2CMNehAqC3pqi3b72g2tHZ1EZA=1x7Y-DeDCyiDMDtVw@mail.gmail.com>

Hi Marc,
what does it mean Spring 2015 ? Is that a release of the Spring project?
We plan to release Hibernate Search 5 by December, we can finally
commit on a date as all blockers have been resolved (finally), so now
we're in polishing and testing fase, back into time-boxing mode.

-- Sanne

On 31 October 2014 12:23, Marc Schipperheyn <m.schipperheyn at gmail.com> wrote:
> I'm disappointed to see Spring 2015 on HSEARCH 5.0. Especially given how
> long Lucene 4 has been in the field (October 2012). HSEARCH seemed to be at
> a standstill for most of this year.
>
> I would prefer to cut down on features to see it sooner, but I guess that's
> not an option anymore. Also, I would say the risk is Lucene will run out of
> 4.x-es and move on to 5.x
>
> Cheers,
> Marc
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

From guillaume.smet at gmail.com  Fri Oct 31 11:51:32 2014
From: guillaume.smet at gmail.com (Guillaume Smet)
Date: Fri, 31 Oct 2014 16:51:32 +0100
Subject: [hibernate-dev] hibernate-dev Digest, Vol 100, Issue 8
In-Reply-To: <CAFm4XO2CMNehAqC3pqi3b72g2tHZ1EZA=1x7Y-DeDCyiDMDtVw@mail.gmail.com>
References: <mailman.8737.1414734004.2753.hibernate-dev@lists.jboss.org>
	<CAGvEgx4ejUwtYZzphD7YbAzQOx2KJWB9q=fLwZis7RMR55CTSg@mail.gmail.com>
	<CAFm4XO2CMNehAqC3pqi3b72g2tHZ1EZA=1x7Y-DeDCyiDMDtVw@mail.gmail.com>
Message-ID: <CALt0+o85u9KCE69cTZQ=zh=d9GL8OruZOXVoEg9dfbwUJnhE0w@mail.gmail.com>

Hi Sanne,

I think Marc was confused by Steve's email.

Steve is talking about ORM 5, not Search 5.

-- 
Guillaume


On Fri, Oct 31, 2014 at 2:59 PM, Sanne Grinovero <sanne at hibernate.org> wrote:
> Hi Marc,
> what does it mean Spring 2015 ? Is that a release of the Spring project?
> We plan to release Hibernate Search 5 by December, we can finally
> commit on a date as all blockers have been resolved (finally), so now
> we're in polishing and testing fase, back into time-boxing mode.
>
> -- Sanne
>
> On 31 October 2014 12:23, Marc Schipperheyn <m.schipperheyn at gmail.com> wrote:
>> I'm disappointed to see Spring 2015 on HSEARCH 5.0. Especially given how
>> long Lucene 4 has been in the field (October 2012). HSEARCH seemed to be at
>> a standstill for most of this year.
>>
>> I would prefer to cut down on features to see it sooner, but I guess that's
>> not an option anymore. Also, I would say the risk is Lucene will run out of
>> 4.x-es and move on to 5.x
>>
>> Cheers,
>> Marc
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

From steve at hibernate.org  Fri Oct 31 12:16:09 2014
From: steve at hibernate.org (Steve Ebersole)
Date: Fri, 31 Oct 2014 11:16:09 -0500
Subject: [hibernate-dev] Antlr 4 PoC
Message-ID: <CAFdSV9sZs3kbmzppkC=0Txo73K4SrE1w5=QCaYngoXpBgBf+Yg@mail.gmail.com>

I started working on a proof-of-concept for using Antlr 4 for query parsing
in Hibernate.  It is very rudimentary at this point.  It is pushed to
GitHub here: https://github.com/sebersole/hibernate-antlr4-poc

This is mean as an attempt to determine whether/how Antlr 4 could/would
work for our needs.  Because Antlr 4 was such a big deviation from versions
2 and 3 we need to see how we can map many of the paradigms and patterns we
use in our existing parsers.

From m.schipperheyn at gmail.com  Fri Oct 31 12:29:55 2014
From: m.schipperheyn at gmail.com (Marc Schipperheyn)
Date: Fri, 31 Oct 2014 14:29:55 -0200
Subject: [hibernate-dev] hibernate-dev Digest, Vol 100, Issue 8
In-Reply-To: <CALt0+o85u9KCE69cTZQ=zh=d9GL8OruZOXVoEg9dfbwUJnhE0w@mail.gmail.com>
References: <mailman.8737.1414734004.2753.hibernate-dev@lists.jboss.org>
	<CAGvEgx4ejUwtYZzphD7YbAzQOx2KJWB9q=fLwZis7RMR55CTSg@mail.gmail.com>
	<CAFm4XO2CMNehAqC3pqi3b72g2tHZ1EZA=1x7Y-DeDCyiDMDtVw@mail.gmail.com>
	<CALt0+o85u9KCE69cTZQ=zh=d9GL8OruZOXVoEg9dfbwUJnhE0w@mail.gmail.com>
Message-ID: <CAGvEgx4wKc-NbbxO-dfgRfk+ua1vPZcGD=hzcSrfUegg2eBJNQ@mail.gmail.com>

Yeah, apologies.

From sanne at hibernate.org  Fri Oct 31 12:35:52 2014
From: sanne at hibernate.org (Sanne Grinovero)
Date: Fri, 31 Oct 2014 17:35:52 +0100
Subject: [hibernate-dev] hibernate-dev Digest, Vol 100, Issue 8
In-Reply-To: <CAGvEgx4wKc-NbbxO-dfgRfk+ua1vPZcGD=hzcSrfUegg2eBJNQ@mail.gmail.com>
References: <mailman.8737.1414734004.2753.hibernate-dev@lists.jboss.org>
	<CAGvEgx4ejUwtYZzphD7YbAzQOx2KJWB9q=fLwZis7RMR55CTSg@mail.gmail.com>
	<CAFm4XO2CMNehAqC3pqi3b72g2tHZ1EZA=1x7Y-DeDCyiDMDtVw@mail.gmail.com>
	<CALt0+o85u9KCE69cTZQ=zh=d9GL8OruZOXVoEg9dfbwUJnhE0w@mail.gmail.com>
	<CAGvEgx4wKc-NbbxO-dfgRfk+ua1vPZcGD=hzcSrfUegg2eBJNQ@mail.gmail.com>
Message-ID: <CAFm4XO3pA+TxVA84KEXLXAE9xiEyaRDuFoxDD9vrBRXOnJr0Ew@mail.gmail.com>

No worries!
Thanks

On 31 October 2014 17:29, Marc Schipperheyn <m.schipperheyn at gmail.com> wrote:
> Yeah, apologies.
>