thanks a lot.
It does not satisfy my intention. I thought the ValueObjects were obsolete in EJB3.0.
So i have to rebuild my application for speedup.
wait a moment! You don't need Value Objects necessarily when you work with lazy loading in a thin client environment. But as soon as you jump over the border of the remote interface you have to take an alternative approach. Do you have a fat client - swing for example?
hmm, yes i have. Its a Swing Client. It was written for EJB2.1 and we now have to go further on the project and migrate it to ejb3.0.
All teh entities, interfaces, value and lightValue object were generated by middlegen. But the middlgen plugin for ejb3.0 is not that capable for these features.
So we have to implement them on our own like some other improvements for ejb3.0.
Thanks for your help
contains an explanation of detached objects (value objects)
You need only to define what data to be contained into the detached objects (for lazy relations you can create extra methods with queries to populate only the relations needed, this gives you flexibility to choose what to send outside the ejb container)
see the JOIN FETCH option into the ejb3 documentation
that's how a expected it to work.
But the case using the lightValueObject isn't defined anywhere i guess.