[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.ejb-orm] Re: JDO fetch-groups important for RCP, EJB3 doesn't have comparable concept

Basically, you still left the question unanswered: how do you do it in O(k)
instead of O(n)? Just claiming that you can do it somehow isn't very convincing.

I would not use lazy properties in the first place to solve - please read what
I'm writing.

For the sake of the best thinkable technology becoming a Java standard, why don't
you just say alright, EJB3 is missing something here. I mean who said EJB3 is
perfect, or JDO2? Why not be open to putting it on the agenda for EJB 3.1 or
something, or to making it an optional feature? If you say nobody needs fetch-groups,
then you shouldn't mind competing implementors featuring it, but they should be
able to feature it as per the standard.

I never said EJB3 were perfect and it was not the whole point of the discussion.
The point was that you said EJB3 is not suitable for a specific case and I said
I could solve it with EJB3 (albeit in a different way - but the problem is solvable
without fetch groups).

I actually pin-pointed you to write it to the ejb3-spec committe!

btw. Hibernate3 can do much of this, but noone ever asked for dynamically
fetch groups probably since all known usecases too me (including yours)
can be implemented in other ways (and I would say it would be more efficient)

I can't help it, but to me this seems to be a constant denial of facts, somehow
reminding me of Microsoft's usual stance. It makes me furious that this short-sighted
over-protection of interests seems to be a major influence on the EJB3 expert
group, potentially putting Java on the client side at danger. Java's competition
here is Microsoft, and you're actively sabotaging Java's competitiveness here.

Ok - this is just blatently stupid low-blows against someone who tries to discuss
different ways of solving things and actually suggest you to talk to the
ejb3 spec-people.

/max