Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
From: "Jeremy Boynes" <jeremy@coredevelopers.net>
To: <geronimo-dev@incubator.apache.org>, <jan@coredevelopers.net>
Subject: RE: [dom4j/w3c] Exposing Documents on geronimo components
Date: Sat, 23 Aug 2003 08:37:55 -0700
Message-ID: <GHEHKNNAODAPCLJONCCDOEGHCPAA.jeremy@coredevelopers.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3F471DDE.1080903@coredevelopers.net>
Importance: Normal

I would say - neither!

The JSR88 deployer will have mechanisms for converting the XML to DDBean and
DConfigBean trees. I would suggest these are exposed rather than the XML in
either form.

This allows the deployer to store the config in any form - we have already
talked about storing config in an external, not-necessarily XML repository
such as RDBMS or JNDI. It also matches the future direction of replacing XML
DDs with J2SE metadata.

--
Jeremy

> -----Original Message-----
> From: Jan Bartel [mailto:jan@coredevelopers.net]
> Sent: Saturday, August 23, 2003 12:55 AM
> To: geronimo-dev@incubator.apache.org
> Subject: [dom4j/w3c] Exposing Documents on geronimo components
>
>
> Some of the web container components would like to expose a parsed XML
> Document in their methods.  Do we have any policy on whether any such
> exposed Documents from the core infrastructure should be w3c only, or
> would we allow a dom4j Document to be exposed?  The w3c interfaces
> guarantee interoperability but they are such a pain to work with ....
>
> Jan
> --
>
> /****************************************
>   * Jan Bartel <jan@coredevelopers.net>
>   * Associate
>   * Core Developers Network LLC
>   * http://www.coredevelopers.net
>   ****************************************/
>
>