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
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
>>
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"
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
As I move through the metamodel code, I try to keep an eye on things we
want to do eventually and where/how they might fit in the new mapping
processing and binding code.
One of the changes we are going through is the move to Jandex. Mainly we
are using Jandex for its "annotation indexing" capabi
