Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 64345 invoked from network); 23 Dec 2004 23:22:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 23 Dec 2004 23:22:46 -0000 Received: (qmail 35016 invoked by uid 500); 23 Dec 2004 23:22:45 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 34274 invoked by uid 500); 23 Dec 2004 23:22:43 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 34258 invoked by uid 99); 23 Dec 2004 23:22:43 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=FORGED_RCVD_HELO,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from mail.tsainc.com (HELO lng002.tsacorp.com) (206.201.23.30) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 23 Dec 2004 15:22:40 -0800 To: dev@geronimo.apache.org Subject: XDoclet 1.2.2 support for Geronimo ( different to XDoclet2 support in GERONIMO-519 ) MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004 From: sissonj@insession.com Message-ID: Date: Fri, 24 Dec 2004 09:22:35 +1000 X-MIMETrack: Serialize by Router on lng002/SVR/TSA(Release 6.5.2|June 01, 2004) at 12/23/2004 17:23:14, Serialize complete at 12/23/2004 17:23:14 Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I have done some work on XDoclet 1.2.2 support for Geronimo ( http://xdoclet.sourceforge.net/xdoclet/index.html ). Currently there is support for generating the openejb-jar.xml file for session and message-driven beans (not entity beans). The reasons I chose XDoclet 1.2.2 instead of XDoclet2 ( http://xdoclet.codehaus.org/ ): * it appears to have a larger user base, is already used by many projects and the supports the majority of other application servers. Adding Geronimo support to a future XDoclet 1.2.* distribution would expose Geronimo to that user base and hopefully encourage its adoption. * a lack of XDoclet2 documentation * not many other application servers had XDoclet2 support * not much activity on the XDoclet2 mailing list archives * I have limited time to get some existing projects (that use XDoclet for generating App Server specific deployment descriptors for various App Servers) to be able to generate Geronimo deployment descriptors/plans. I'm not suggesting XDoclet2 is not the way forward and my decision was based upon nontechnical observations. It would be nice if we could provide both XDoclet 1.2.2 and XDoclet2 support, so the user has the choice of what they want to use. If we are going to do that, we would want to ensure that the @Geronimo tags are consistent between the two, so people can move from one to the other as easily as possible. The tags supported in Len Yeung's XDoclet2 support ( http://nagoya.apache.org/jira/browse/GERONIMO-519 ) don't appear to overlap the tags supported in my XDoclet 1.2.2 support, so we have time to get this right. I am currently working on basic tag reference doco (the xtags.xml file) and once complete, will create another JIRA issue and attach patches so people can review and contribute. Once Geronimo's configuration has stabilised we could then look at moving the Geronimo XDoclet 1.2.2 module source to the sourceforge project so that it is included in future XDoclet releases (assuming there aren't any licensing issues preventing that). Regards, John Sisson