the problem with this approache, although cleaner, is that every get/set method to populate the vo ou EJB are done through the various interceptors, see a thread at jboss list (Entity Bean Performance Tuning Help).

Chris Conrad wrote:
For EJB 2.0 CMP Entity Beans it has started to become bad practice to
include your ValueObject getter and setter in the bean itself. Instead
you are encouraged to have a factory which creates value objects. This
allows your entity bean to remain static even when additional value
objects are found to be needed. Has there been any thought of adding
the creation of value object factories to xdoclet? It seems that most
of the code would already exist in the current value object and entity
cmp code and templates.

--Chris






-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user


--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
| Emerson Cargnin          |
| Analista de Sistemas Sr. |
| Tel : (051) 3358-4959    |
| SICREDI Servi�os         |
| Porto Alegre - Brasil    |
|xxxxxxxxxxxxxxxxxxxxxxxxxx|



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to