[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.ejb-orm] Re: correction: EJB3 is specified for use outside of a J2EE container

<snipped usecase>

The above is doable in hibernate3 today.

How would you solve that with EJB3?

with a initial report query and then only load the full objects
when required - i'm more for explicit querying, than implicit loading via object navigation (but that is
just a diffferent opinion/taste)


And in any way - send request enhancmenets with describtion of why to the ejb3 spec group: jsr-220-comments@xxxxxxx

EObjectImpl.
This is one of the intrusive design issues I don't like.
Well, EObjectImpl gives you a superb meta-model in comparison to Java reflection,
out-of-the-box and DTD-conformant XML-serialization, super-flexible change
notification, validation, and probably lots of other nice stuff I forgot right
now. Just that you surely know what you don't like here ;)

I'm just saying that that stuff could be provided with much less intrusive means.


Some things don't work with these features, e.g. support for array types is not
possible. Also EMF currently doesn't support generics, which is a pity.

A realy pity.

/max