It's been discussed tens of times but no one dared to implement it because it needs a deep understanding of different application servers and their cmp capabilities. I was actually the first guy who proposed it a year ago (called "Unified Persistence Tags")!
What we need is: some guys with deep knowledge of their application server. So we can discuss a unified tag and see if it's general enough. And I'm gonna tell you that it's way harder than you think, for example some vendors (TopLink and websphere for example) support mapping a single field to a combination of many database column, so you specify a db-field mapper there and it takes care of merging/splitting it. So other than the simple one-field->one-db-column mapping you have more sophisticated one-field->many-db-columns mapping! How are you going to cover both now in your generic tag? And stuff like that. Tricky.... Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Marcus Brito > Sent: Thursday, February 28, 2002 8:36 AM > To: [EMAIL PROTECTED] > Subject: [Xdoclet-devel] Proposal: Vendor tags unification > > 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 _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
