|
Hi all,
One classical source of discussion on EJB Entity
Beans is the performance issues that they introduce.
One generally not so well understood way to go
around this problem is to deploy the same beans several time using different
deployement attributes. For instance I deploy my Entity Beans as readonly
for the waste majority of the usecases where data needs only displaying and I
deploy my Entity Beans as read-write for the remaining cases where data needs to
be updated.
This approach has been recently highlighted in an
article by Tyler Jewell.
I have used multiple deployement in past
projects to improve performance. On my current project I need to reuse this
technic and but I want to keep using xdoclet, which does not seam to support
this feature.
Anyone thinks like me that it would be beneficial
to introduce this feature in XDoclet?.
Emmanuel
|
- RE: [Xdoclet-user] xdoclet and multiple deployement. Emmanuel Sciara
- RE: [Xdoclet-user] xdoclet and multiple deployement. aslak . hellesoy
- Re: [Xdoclet-user] xdoclet and multiple deployem... Rainer Schmitz
- RE: [Xdoclet-user] xdoclet and multiple depl... Ara Abrahamian
- Re: [Xdoclet-user] xdoclet and multiple deployement. aslak . hellesoy
- RE: [Xdoclet-user] xdoclet and multiple deployement. Jason Carreira
- RE: [Xdoclet-user] xdoclet and multiple deployem... Ara Abrahamian
- RE: [Xdoclet-user] xdoclet and multiple deployement. Jason Carreira
- RE: [Xdoclet-devel] RE: [Xdoclet-user] xdoclet a... Ara Abrahamian
