2014-03-11 18:17 GMT+01:00 Sanne Grinovero :
> On 11 March 2014 17:08, Gunnar Morling wrote:
> >
> >
> >
> > 2014-03-11 17:45 GMT+01:00 Sanne Grinovero :
> >
> >> On 11 March 2014 10:59, Gunnar Morling wrote:
> >> > 2014-03-09 18:31 GMT+01:00 Steve Ebersole :
> >> >
> >> > @Entity
> >> >> interf
Mainly we discussed OGM and its evolving need for contextual info and how
to best make that accessible from ORM contracts such as Session. Also, I
gave an update on the Jira/GitHub email from last week.
[12:46] Meeting ended Tue Mar 11 17:34:51 2014 UTC. Information
about MeetBot at http://wiki
There are actually lots of great use cases for pure persistence models.
Prototyping, modeling, designing is one as Sanne mentioned. "Dynamic"
models is another. You see this is envers, grails, and other places.
Also, whether *you* think persistence models should or should not be anemic
is fine.
On 11 March 2014 17:08, Gunnar Morling wrote:
>
>
>
> 2014-03-11 17:45 GMT+01:00 Sanne Grinovero :
>
>> On 11 March 2014 10:59, Gunnar Morling wrote:
>> > 2014-03-09 18:31 GMT+01:00 Steve Ebersole :
>> >
>> > @Entity
>> >> interface Employee {
>> >> ...
>> >> }
>> >>
>> >> 2) We'd dynamically
2014-03-11 17:45 GMT+01:00 Sanne Grinovero :
> On 11 March 2014 10:59, Gunnar Morling wrote:
> > 2014-03-09 18:31 GMT+01:00 Steve Ebersole :
> >
> > @Entity
> >> interface Employee {
> >> ...
> >> }
> >>
> >> 2) We'd dynamically generate a class to back this. This generated class
> >> can co
On 11 March 2014 10:59, Gunnar Morling wrote:
> 2014-03-09 18:31 GMT+01:00 Steve Ebersole :
>
> @Entity
>> interface Employee {
>> ...
>> }
>>
>> 2) We'd dynamically generate a class to back this. This generated class
>> can contain many of the performance tweaks we've been developing via
>>
On Mon, Mar 10, 2014 at 7:29 AM, Emmanuel Bernard wrote:
> Either this or have on the session owner contract a generic facility to
> store session specific data that OGM could extend.
> I think Steve has been reluctant of such contract in the past. We could re
> discuss the pluses and minuses.
>
>
I'm OK with exposing a getSessionOwner() method. This could actually be
helpful in other places like envers iiuc.
On Mon, Mar 10, 2014 at 6:59 AM, Gunnar Morling wrote:
> Hi,
>
> I'm looking into ways for reducing the number of datastore roundtrips in
> OGM [1].
>
> One idea is to fetch associa
But you're OK with the following instead?
@Entity
@Proxy(proxyClass=Employee.class)
class EmployeeImpl implements Employee {
...
}
?
See I find that (^^) less clear and less concise.
What's the basis for your gut to say -1? Because it "breaks" from JPA?
On Tue, Mar 11, 2014 at 5:37 AM,
2014-03-09 18:31 GMT+01:00 Steve Ebersole :
@Entity
> interface Employee {
> ...
> }
>
> 2) We'd dynamically generate a class to back this. This generated class
> can contain many of the performance tweaks we've been developing via
> bytecode extensions (inline dirty-checking, "entity entry"
BTW it is minimalist atm, but if you ask questions here, I'll update
that section.
Emmanuel
On Mon 2014-03-10 19:25, Hardy Ferentschik wrote:
> Nice
>
> On 10 Jan 2014, at 18:13, Emmanuel Bernard wrote:
>
> > I finally resolve WEBSITE-95 and explained how to build the website.
> > It is on th
That would be extremely useful. That being said, it's not the only
useful context. On top of the "entity" context, I can see usage for:
- per event context (flush event for example)
- transaction context
- global session context (not sure I have a use case yet but I suspect
it's useful.
Emmanue
On 9 Jan 2014, at 18:31, Steve Ebersole wrote:
> Then we had expanded the previous discussion to look at the more general
> case... interface based models. Imo, the best way to map the above model
> would be:
>
> @Entity
> interface Employee {
>...
> }
>
> Yes, this deviates from JPA whic
On Mon, Mar 10, 2014 at 4:26 PM, Brett Meyer wrote:
> Done! Thanks for pointing it out -- not sure how that happened to begin with.
Thanks, Brett.
--
Guillaume
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailm
14 matches
Mail list logo