Greetings to all xdoclet developers. The current xdoclet vendor support is great. For every major vendor there are xdoclet subtasks to generate deployment descriptors, source code and other required files. Choose your application server, mark you source with the right tags and xdoclet will do the work.
However, this is fine as long as your application targets a single vendor. If you're intending to deploy your app on multiple servers, there will be lots of redundant tags, one for each app server. For example, almost every J2EE vendor has a tag @vendor:column-name to indicate the database column a CMP field should be persisted. There are also tags to indicate read only beans, jdbc types, sql types, queries and lots of other info. So, I hereby propose a unification of similar vendor tags. Instead of @jboss:column-name, @bluestone:column-name, @mvcstone:column-name and all other @vendor:tags, we should strive to use @ejb:column-name or similar. Unless a feature is *very* vendor specific, we should always use an @ejb prefix. Each vendor template will then look at the generic tags for the info needed. I know this is a great task to be done, but if we split up the work we'll be able to accomplish this. I myself could take care of modifying the JBoss tags. I hope most of you see this proposal as a benefical thing. We need this kind of stardardization on tag names to make xdoclet a vendor-independent source/descriptor generator. -- Ja ne, Marcus Brito mailto: [EMAIL PROTECTED] Anime Gaiden - De f�s para f�s, sempre. http://www.animegaiden.com.br
signature.asc
Description: This is a digitally signed message part
