On 11 Jan 2013, at 19:25, Scott Marlow wrote:
> On 12/11/2013 11:44 AM, Gunnar Morling wrote:
>> Ales,
>>
>> Can you confirm that some static method is involved here (which was the
>> case for HV-818)? I can't see one on your Email class but maybe there is
>> one on AbstractEntity?
>>
>> If so
On 12/11/2013 11:44 AM, Gunnar Morling wrote:
> Ales,
>
> Can you confirm that some static method is involved here (which was the
> case for HV-818)? I can't see one on your Email class but maybe there is
> one on AbstractEntity?
>
> If so, I think releasing a 5.0.2.Final would make sense, containi
I think Gunnar forgot to include Ales in the previous mail (unless he is on
hibernate-dev).
Anyways, just a few comments.
On 11 Jan 2013, at 17:44, Gunnar Morling wrote:
> Can you confirm that some static method is involved here (which was the
> case for HV-818)? I can't see one on your Email
Thanks for the feedback Guillaume,
I probably missed how critical this bug is, I definitely want 4.4 to
be "fully functional", so +1 to release another 4.4.x when this is
fixed.
Regarding Search 4.5: it's only compatible with ORM 4.3, we
specifically branched because it was too tricky to keep com
> Our question is, should now that we have the Option API and with it
store-specific DatastoreConfiguration types, the previously used
Environment interfaces be removed and their constants moved to the
corresponding DatastoreConfiguration type?
Yes, +1
On Wed, Dec 11, 2013 at 5:08 PM, Gunnar Mo
Hi,
Davide brought up an interesting issue while reviewing a PR around the OGM
backend for CouchDB [1].
This PR makes use of the new Option API and allows to configure
CouchDB-specific settings in a safe way. For that purpose each dialect
needs to provide a sub-class of DatastoreConfiguration whi
Ales,
Can you confirm that some static method is involved here (which was the
case for HV-818)? I can't see one on your Email class but maybe there is
one on AbstractEntity?
If so, I think releasing a 5.0.2.Final would make sense, containing the
following three issues:
* HV-818 (this issue)
* HV
Hi Sanne,
On Wed, Dec 11, 2013 at 3:23 PM, Sanne Grinovero wrote:
>> Yes - https://github.com/hibernate/hibernate-search/pull/523 (HSEARCH-1442)
>> I’ll need to confirm the fix and we should give the reporters a chance to
>> verify against
>> a snapshot. If the fix looks good we should add it t
On 11 December 2013 14:16, Hardy Ferentschik wrote:
>
> On 11 Jan 2013, at 13:51, Sanne Grinovero wrote:
>
>> We need to align the 4.5 branch to latest ORM 4.3.
>>
>> Considering the main theme for 4.5 is to keep up with JPA 2.1 and
>> latest WildFly, the branch is technically ready for a release
On 11 Jan 2013, at 13:51, Sanne Grinovero wrote:
> We need to align the 4.5 branch to latest ORM 4.3.
>
> Considering the main theme for 4.5 is to keep up with JPA 2.1 and
> latest WildFly, the branch is technically ready for a release.
+1 We should release asap
> Anything else that you would
On 12/11/2013 07:40 AM, Emmanuel Bernard wrote:
> https://hibernate.atlassian.net/browse/HV-818
>
> I am a bit uncertain of the case and frequency when that happens. If
> WildFly does plan to stay on the 5.0.x series, we probably want to fix
> it in a 5.0.2. Same for the classloader leak I imagine.
We need to align the 4.5 branch to latest ORM 4.3.
Considering the main theme for 4.5 is to keep up with JPA 2.1 and
latest WildFly, the branch is technically ready for a release.
Anything else that you would like to see fixed in this branch?
I have no problem in postponing the release to tomorr
https://hibernate.atlassian.net/browse/HV-818
I am a bit uncertain of the case and frequency when that happens. If
WildFly does plan to stay on the 5.0.x series, we probably want to fix
it in a 5.0.2. Same for the classloader leak I imagine.
Emmanuel
On Wed 2013-12-11 11:23, Ales Justin wrote:
>
Hi Ales,
Agreed, that doesn't look right. At this location the array should always
have one or two elements, I can't say right now what could cause the array
to be empty there.
I just put your Email class into a test project of mine but couldn't
reproduce the error (maybe something is special abo
resolvedSubType =
{com.fasterxml.classmate.types.ResolvedObjectType@11177}"com.moody.lw.server.domain.Email"
memberResolver = {com.fasterxml.classmate.MemberResolver@11583}
typeWithMembers = {com.fasterxml.classmate.ResolvedTypeWithMembers@11584}
resolvedMethods = {com.fasterxml.classmate.members.
@Hardy, Emmanuel: https://gist.github.com/alesj/7908062
Imo, any AIOOBE is a bug.
-Ales
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
16 matches
Mail list logo
