geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Köhler <>
Subject Re: [jira] Updated: (GERONIMO-155) [proposal] resolving for kernel
Date Wed, 04 Feb 2004 13:15:26 GMT

Kristian Köhler wrote:

> I think that's only one part of the problem. While using xmlbeans 
> geronimo doesn't need the grammar files during deployment. But what 
> about other services like jetty? If they call
>     SAXParserFactory.newInstance();
> for any reason they still get a regular implementation probably not 
> doing any entity resolving. This could again trigger a remote connection.
> I think it would be useful to have serverwide catalog/ repository. This 
> could also include things like caching and runtime config.

This still remains.

>> Anyway, all comments on my alternate suggestion would be greatly  
>> appreciated.

The xmlbeans based approach seems to work very nicely. However is there 
a special reason for putting the information in two documents, e.g. 
ra.xml and geronimo-ra.xml? Maybe if the geronimos could be adjusted via 
namespace magic so that only document is required which could then serve 
  as the base for a xmlbeans class creation? If really necessary the 
relevant information (sun vs. geronimo specific) could still be easily 
separated and changed via sax xmlfilters.

When using one document the generated classes could be also used as 
model classes and no additional data shifting like

geronimoConnectorDocument = 
GeronimoConnectorLoader.load(geronimoConnectorDoc, connectorDocument);

is needed.

We are interested in your opinion on this ;-)

Steffen and Kristian

View raw message