2014-03-29 17:40 GMT+01:00 Steve Ebersole :
> To wrap this up..
>
> The most important part for me is being able to identify the point between
> the "attribute base" and the "attribute path". If we just use a separate
> delimiter there, that's enough for me. Since one of us has a preference
> fo
+1
One potential issue coming to mind is that this will require Hibernate OGM
users to work with Java 7 as well (at least when using queries via
Hibernate Search).
When discussing the issue (for OGM) last time, we decided to stick to Java
6 to ease OGM experiments of existing Hibernate ORM users.
Since Hibernate OGM is now an implementation of JPA 2.1, doesn't it
already require Java 7?
You could also decide to use Java7 for the build but not necessarily
make use of Java7 features, as Search is an optional dependency. (but
I also don't see a problem on moving).
I would like to encourage O
2014-03-20 23:05 GMT+01:00 Emmanuel Bernard :
> I took some more time to think about our conversation from 2 IRC meeting
> ago
> about offering the ability to carry session bound state not related to
> ORM per se.
> Below is a sum and a potential solution.
> If you are short on time, read Goals, t
2014-03-31 12:08 GMT+02:00 Sanne Grinovero :
> Since Hibernate OGM is now an implementation of JPA 2.1, doesn't it
> already require Java 7?
>
Good point; Not sure whether JPA 2.1 per-se really requires Java 7, but I
understand as an implementation we'd be "allowed" to require Java 7 as per
the s
The thing is, the map approach had a big -1 from Steve hanging on its head :)
> On 31 mars 2014, at 12:07, Gunnar Morling wrote:
>
>
>
>
> 2014-03-20 23:05 GMT+01:00 Emmanuel Bernard :
>> I took some more time to think about our conversation from 2 IRC meeting ago
>> about offering the abilit
Btw to answer your concern about the event listeners and the use of instance
of, we could imagine an API like getListenerOfType(Class) on the
SessionEventListenerManager. Because one key thing that this approach solves
and that the map approach does not is the actual event listener callback
cap
2014-03-31 14:31 GMT+02:00 Emmanuel Bernard :
> The thing is, the map approach had a big -1 from Steve hanging on its head
> :)
>
Yes, I know :)
But when the map initialization is done lazily as suggested, would there
really be any problem with that? SessionImpl would have a null reference to
th
2014-03-31 14:35 GMT+02:00 Emmanuel Bernard :
> Btw to answer your concern about the event listeners and the use of
> instance of, we could imagine an API like getListenerOfType(Class) on the
> SessionEventListenerManager.
>
Hum, couldn't there be several instances of the same listener type, e.g.
So why is #nv (or ::nv) any different than #to (::to) or #hell (::hell)?
In other words, if you agree that this or that is delimiter to use for
attributes, why is it different at the start of a path versus within a
path? `to` is still a method right? `hell` is still a method...
On Mon, Mar 31,
On Mon, Mar 31, 2014 at 7:48 AM, Gunnar Morling wrote:
> 2014-03-31 14:35 GMT+02:00 Emmanuel Bernard :
>
> > Btw to answer your concern about the event listeners and the use of
> > instance of, we could imagine an API like getListenerOfType(Class) on the
> > SessionEventListenerManager.
> >
>
> Hu
Wasn't just me that said -1...
My concerns are 2-fold:
1) You want ORM to manage and expose "state storage" on Session even though
it does not use it.
2) You want to store state in there that isnt even Session-scoped. Rather
you have state that is scoped to a flush cycle, or to a transaction, etc
http://lists.jboss.org/pipermail/hibernate-dev/2013-February/009426.html
On Mon, Mar 31, 2014 at 5:16 AM, Gunnar Morling wrote:
> 2014-03-31 12:08 GMT+02:00 Sanne Grinovero :
>
> > Since Hibernate OGM is now an implementation of JPA 2.1, doesn't it
> > already require Java 7?
> >
>
> Good point;
Guillaume, I corrected java-formatting.xml on
https://community.jboss.org/wiki/ContributingToHibernateUsingEclipse. Thanks
for pointing that out.
Brett Meyer
Red Hat, Hibernate ORM
- Original Message -
From: "Guillaume Smet"
To: "Hibernate"
Sent: Friday, March 28, 2014 9:55:18 AM
Sub
Do we want to put these in git?
On Mon, Mar 31, 2014 at 9:48 AM, Brett Meyer wrote:
> Guillaume, I corrected java-formatting.xml on
> https://community.jboss.org/wiki/ContributingToHibernateUsingEclipse.
> Thanks for pointing that out.
>
> Brett Meyer
> Red Hat, Hibernate ORM
>
> - Origina
+1 -- absolutely. It seems a few of us keep overwriting each other ;)
Brett Meyer
Red Hat, Hibernate ORM
- Original Message -
From: "Steve Ebersole"
To: "Brett Meyer"
Cc: "Guillaume Smet" , "Hibernate"
Sent: Monday, March 31, 2014 10:52:57 AM
Subject: Re: [hibernate-dev] Fix for the
Gunnar, can you lead the work on getting that set of "fleshed out" use
cases. With a bit of luck we could have them by tomorrow for the
meeting and discuss them there.
BTW, as I said in my proposal the delegate does not work as there is not
always a delegate object created.
Emmanuel
On Mon 2014-
On 31 March 2014 15:33, Steve Ebersole wrote:
> http://lists.jboss.org/pipermail/hibernate-dev/2013-February/009426.html
Thanks Steve. So I guess that settles it for OGM as well?
(Removed all people from CC as we're changing subject)
-- Sanne
>
>
> On Mon, Mar 31, 2014 at 5:16 AM, Gunnar Morlin
Recently, we've been trying to clean up ORM's JIRA tickets. There are a lot of
duplication, stale issues, etc. One thought was pushing all ORM 3 tickets to
the "Awaiting Test Case" state and requesting a reproducer on ORM 4 or 5. They
would then fall under our policy of automatically rejectin
On 31 Jan 2014, at 21:09, Brett Meyer wrote:
> Recently, we've been trying to clean up ORM's JIRA tickets. There are a lot
> of duplication, stale issues, etc. One thought was pushing all ORM 3 tickets
> to the "Awaiting Test Case" state and requesting a reproducer on ORM 4 or 5.
> They wo
> I guess you would still include some features/improvements issues
I'm sure some legitimate things may get caught up in this, but I'd rather try
to clean things up aggressively, then re-open on a case-by-case basis. If
there's something we close that the community feels strongly about, the hop
On 31 Jan 2014, at 21:52, Brett Meyer wrote:
>> I guess you would still include some features/improvements issues
>
> I'm sure some legitimate things may get caught up in this, but I'd rather try
> to clean things up aggressively, then re-open on a case-by-case basis.
+1 That would be my thin
On 31 Jan 2014, at 22:01, Steve Ebersole wrote:
> Probably not a bad idea to write up a blog describing what we are doing and
> why. We could link to that in the Jira comment
+1, also an oppertunity to blog something else than ORM release blogs ;-)
_
Probably not a bad idea to write up a blog describing what we are doing and
why. We could link to that in the Jira comment
On Mon, Mar 31, 2014 at 2:52 PM, Brett Meyer wrote:
> > I guess you would still include some features/improvements issues
>
> I'm sure some legitimate things may get caugh
Good thoughts -- will do. If anyone has differing opinions, I'm all ears. I
won't attempt this for a week or so...
Brett Meyer
Red Hat, Hibernate ORM
- Original Message -
From: "Hardy Ferentschik"
To: "Steve Ebersole"
Cc: "Brett Meyer" , "Hibernate"
Sent: Monday, March 31, 2014 4:0
-
The message you sent to amigosenmarcha.org/informacion was rejected because it
would exceed the quota for the mailbox.
The subject of the message follows:
Subject: Vacancy - apply online
2014-03-31 18:28 GMT+02:00 Sanne Grinovero :
> On 31 March 2014 15:33, Steve Ebersole wrote:
> > http://lists.jboss.org/pipermail/hibernate-dev/2013-February/009426.html
>
> Thanks Steve. So I guess that settles it for OGM as well?
>
IIRC, the situation back then was a bit different. The JPA JAR
27 matches
Mail list logo
