Hi Emmanuel,
You an either use the merge feature, providing your own deployment decriptor
snippets to be merged into the final one. See examples/docs.
A different approach is to use @some:tag
someParameter="${some.ant.property}", and XDoclet will replace
${some.ant.property}" with the ant property's value. You can define these
properties in build.xml, or in external properties files, which you can read
into ant with <property file="fubar.properties"/>. Then you can provide
different versions of this external properties file to obtain different
deployment descriptors without having to change anything else. This requires
the CVS version (I think).
Would that do the trick for you?
Aslak
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Emmanuel
Sciara
Sent: 11. januar 2002 11:44
To: xdoclet-user
Subject: [Xdoclet-user] xdoclet and multiple deployement.
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.
(See http://www.onjava.com/pub/a/onjava/2001/12/19/eejbs.html )
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
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
