> no, I did not get *any* feedback - I ain't got *no* feedback. :-) See below.
> > Now, what's the remedy? > > > > Do not generate VOs in the entity bean. The right point for > > VO generation is > > the session facade of the component that executes on behalf > > of the client to > > support its workflow. Create a factory for VOs and get the > > data from the > > entity bean via its local interface. > > > > The effect? > > > > Reuse of the entity bean will be easier, even in different > > projects. Each > > project writes its own value object factories (for the same > > entity beans) to > > support its own use cases. The original entity bean developer > > may turn to > > the next task in line. Agree. I'm doing exactly that in my project. VO is for remote clients in session facades. VO is for a specific scenario/client. Ara. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
