Yes. It is currently used in the LocalEntityResolver. There's also a
catalog file in CVS. (modules/core/src/conf/resolver-catalog.xml)
The idea is to set this LocalEntityResolver for all Parsers in Container.
thanks,
Kristian
Davanum Srinivas wrote:
Has anyone looked into using xml commons catalog resolver? -
http://xml.apache.org/commons/components/resolver/index.html
thanks,
dims
--- Kristian_K�hler <[EMAIL PROTECTED]> wrote:
Hi
David Jencks wrote:
I have been well aware of this problem for quite a while, but have not
done much (such as applying all of your previous patches) to fix it
because I have been working on using xmlbeans to read all the xml
files. This xmlbeans solution would not require geronimo to be able to
access the schemas at runtime at all, as the generated xmlbeans code
validates while reading xml.
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.
At the moment, the schemas are still required, and some network access
is still required, to generate the xmlbeans classes. Looking at the
xmlbeans cvs, it appears that the somewhat experimental v2 code allows
you to set an entity resolver or catalog, but v1 doesn't. I wonder if
we could encourage them to add this useful feature into their v1 code
base.
Anyway, all comments on my alternate suggestion would be greatly
appreciated.
I will try to look into it ASAP.
Kristian
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
--
Kristian K�hler
