Return-Path: Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: (qmail 62188 invoked from network); 13 Jul 2006 17:57:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Jul 2006 17:57:17 -0000 Received: (qmail 95320 invoked by uid 500); 13 Jul 2006 17:57:17 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 95247 invoked by uid 500); 13 Jul 2006 17:57:17 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" List-Id: Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 95236 invoked by uid 99); 13 Jul 2006 17:57:17 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jul 2006 10:57:17 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jul 2006 10:57:16 -0700 Received: from ajax.apache.org (localhost [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 7977CD495F for ; Thu, 13 Jul 2006 18:56:55 +0100 (BST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: derby-commits@db.apache.org Date: Thu, 13 Jul 2006 17:56:55 -0000 Message-ID: <20060713175655.416.90607@ajax.apache.org> Subject: [Db-derby Wiki] Update of "High Level Design" by SanketSharma X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Dear Wiki user, You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification. The following page has been changed by SanketSharma: http://wiki.apache.org/db-derby/High_Level_Design ------------------------------------------------------------------------------ [[BR]] [[Anchor(Issues)]] == 9. Issues == - * ''' Version Incompatibilities: ''' Currently, most of Derby's source is built against Java version 1.3, only code that is inherantly dependant on 1.4 is compiled against javac version 1.4. However, JMX support is available only on Java versions 5 (1.5) and above. Ant scripts will have to be modified in this case to support the building of JMX modules. [[BR]] + * ''' Version Incompatibilities: ''' Currently, most of Derby's source is built against Java version 1.3, only code that is inherantly dependant on 1.4 is compiled against javac version 1.4. However, JMX support is available only on Java versions 5 (1.5) and above. Reference implementations of JMX are available for JMV version 1.3 and 1.4 as seperate download (Please see the discussion below for JMX implementations). Ant scripts will have to be modified in this case to support the building of JMX modules. [[BR]] * ''' Modules.properties: ''' The modules.properties file uses derby.env.jdk.={1|2|4} to identify which modules are supported under which JVM environments. Since JMX requires 5 and above, we need to extend support for 5 and maybe 6 as well. (Not very sure about this) [[BR]] + * ''' JMX Implementations: ''' Anothe design issue it the choice of JMX implementations. Besides the one available as part of Sun JDK 1.5 and above there are several other open source implementations available. Each has its own advantages and disadvantages. The following is a list of the most apparant ones:[[BR]][[BR]] + '''1. Sun JDK 1.5 and above: ''' Requires no additional Jars to depolyed with the client. Leads to smaller footprint. One the negetive side, it will always require Derby to run on JRE 1.5 and above. My not be a good choice as some implementations might be using earlier versions.[[BR]][[BR]] + '''2. Sun JDK prior to version 1.5: ''' Sun's references implemenation (available as a seperate jar download) for JDK versions 1.3 and above. Applications running on JVM 1.3 and 1.4 will need to download install this jar.[[BR]][[BR]] + ''' 2. XMOJO Project: ''' This JMX supports JDK version 1.2 and above, which means it imposes no additional JDK requirements. Hoewever, additional JARs will to be deployed on the client for them to use JMX. They can either be bundled with Derby or can be seperately installed on client. Another point to note is that XMojo itself requires two more jars to be present (xalan.jar, crimson.jar, and jaxp.jar and org.mortbay.jetty.jar)[[BR]][[BR]] + ''' 3. Apache Commons Modeller framework: ''' The commons modelling framework is another Apache project developed under the Jarkarta project. Although, it is not an implementation in itself, it facilitates writing of MBeans in a big way and future updates are easily managed. The Metadata for MBeans is specified in an XML file which is parsed to gernerate MBeans.It is know to work with all major JMX implementations.[[BR]][[BR]] + ''' 4. MX4J:''' Another very popular JMX framework know to work with JDK 1.3 and above. It also supports automatic generation of ModelMBeans using XDoclets. Needs additional jars to be deployed. Supports HTTP adapters for access via HTTP. [[BR]][[BR]] + + My recommendation is to use Sun's reference implementation with the commons modelling framework.[[BR]] [[Anchor(Geronimo)]] == 10. Geronimo and Glassfish ==