Back from hell ;) > > > In my application I ended up modeling everything > > > (the graph I mean) as serializable dependent objects and > simply pass > > > them around. All ejb container dependent code is out of those > > > dependent objects, inside a session fa�ade. > > > > ...and the session facade decompose/compose the dependant > object and > > call the entity beans ? > > Well, I don't use entity beans in that sense :-) Just plain > java objects, but I also have a wrapper entity bean. > JavaBeans are dependent objects (remember ejb2 PFD2?). > > > That is the Value Object afaik except that the entity itselef is > > handling them, for you it is a session facade. ??? > > No it's plain java, nothing special.
OK > > > > And > > > btw if web and ejb tiers on in the same jvm you don't really need > > > value object, just wrap the access in a transaction. > > > > You mean having entity's fields getter in the local interface ? You > > still have the security/... that the container do on ejb acess > > Overhead no ? > > Well, you don't have that overhead when you're building the > valueobject? After all you're calling getter methods of the > bean, right? No, the bean instance is calling itself : getVO() just call getter on itself When talking to Interface (and "talking jboss") you talk to the container instance through the "interceptors" : security, locking, entity synchronizer (ejbLoader) : small overhead in most cases but overhead ;) > > Ara. > Vincent _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
