Hello Patrick, I started to work on the XDoclet @jdo module before Solarmetric support was released, so unfortunately the tags used are quite different - they use tag attributes extensively whereas Solarmetric's tags use one tag per option. I designed those tags to be as close as possible to the existing @ejb tags, and i tried to remove as much as possible vendor lock-in by factoring out the common functionality. So in short you have the following: @jdo tags cover the full JDO specification @sql tags deal with common object-relational mapping. This is an attempt to abstract as much as possible the vendor extensions Of course, not all vendors always support all the functions defined here, so when that happens XDoclet generates warnings when a vendor doesn't support the requested functionality. @kodo, @lido and other proprierary tags deal with vendor-specific functionality not covered by the tags above.
Have a look to the following tag definitions in xml format (sorry, the generation of nice html docs is broken) http://tinyurl.com/34t3 and http://tinyurl.com/34t7 The common @sql tags have been quite enlightning as they show that the current JDO spec is flawed in respect to vendor independance: for example, the definition of what is a JDO primary-key field in a relational database was left undefined when you are using datastore identity: Kodo uses a hidden primary-key field with an automatically generated OID and Lido uses the primary-key fields from the database table, and so you cannot use the same code for the same database across vendors... Using the more verbose application identity solves this problem, but still I think it shows that JDO is still not mature. Now if you want to help, you can become the official maintainer for the solarmetric module, and provide a migration utility or some king of adapter for people using the current Solarmetric module for XDoclet. Hope this helps, Ludovic Claude ----- Original Message ----- From: "Patrick Linskey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 29, 2002 2:02 AM Subject: Kodo JDO and XDoclet 1.2 > Hey, > > Erik Hatcher pointed me to XDoclet 1.2's @jdo tag support. He mentioned > that there is some controversy surrounding proprietary tags and a > module dedicated to SolarMetric/Kodo. > > I was hoping you could enlighten me about what work you've done with > JDO and XDoclet, and how we can participate in getting XDoclet's JDO > capabilities up-to-speed. Also, do you have a pointer to some design > docs about what goes in the solarmetric module as opposed to the jdo > module, or should we just dig in the source? > > Thanks, > > -Patrick > > -- > Patrick Linskey [EMAIL PROTECTED] > SolarMetric Inc. http://www.solarmetric.com > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
