OK, so I've now played with deploying xdoclet on Orion, JBoss, WebLogic, Pramati, and Borland App Server. I'm going to submit my Pramati stuff to be added to CVS in just a minute (BAS will come next week), but I'd like to run something by everyone:
I mentioned this before: why not make a standard "ejb:persistence" tag that handles common values among 99% of app servers: table-name, datasource, and field mapping? We could easily write the templates to work with both orion:persistence, and if that doesn't exist, then ejb:persistence. I'm working on making some OpenSymhpony modules deploy on all these app servers, and I find it silly my code contains this: * @weblogic:table-name OS_PROPERTYDATA * @jboss:table-name table-name="OS_PROPERTYDATA" * @orion:bean table="OS_PROPERTYDATA" * @ejb:persistence table-name="OS_PROPERTYDATA" OR * @jboss:column-name name="id" * @weblogic:dbms-column id * @ejb:persistence column="id" * @orion:persistence persistence-name="id" I've written the new Pramati support to look at @ejb:persistence for the class-level values of 'table-name' and 'datasource'. For method-level tags, it looks for the attribute 'column'. I'd like to propose that we decide on a standard, such as this, and start modifying the templates to take advantage of both. This would allow for backwards compatability. If this were approved, I'd like to suggest we do the same for tags/attribute combos such as jndi-name. All the app servers I've worked on have a jndi-name value, but the templates don't all look for "ejb:bean jndi-name". -Pat _________________________________________________________________ Join the world�s largest e-mail service with MSN Hotmail. http://www.hotmail.com _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
