catalogLocation not used in multi-module projects on modules 2-N
----------------------------------------------------------------
Key: MXMLBEANS-60
URL: http://jira.codehaus.org/browse/MXMLBEANS-60
Project: Maven 2.x Xmlbeans Plugin
Issue Type: Bug
Affects Versions: 2.3.3
Environment: All
Reporter: Ron Gallagher
Attachments: ParameterAdapter.diff
In a multi-module project where each module uses a different set of catalog
files (see the catalogLocation parameter), the contents of the catalogs that
are specified on modules 2-N are not used. This is because the
org.apache.xml.resolver.CatalogManager class loads the contents of the first
set of catalog files and caches those contents in a static variable. The
ParameterAdapter class tells the CatalogManager class where to find the catalog
files for each module, but the CatalogManager class only loads/caches the first
set of catalog files.
However, passing a value of 'false' to the setUseStaticCatalog() method causes
the org.apache.xml.resolver.CatalogManager class to NOT use it's statically
cached catalog. Instead, the org.apache.xml.resolver.CatalogManager class
serves up a fresh Catalog every time the getCatalog method is called. This
introduces a slight performance hit, but it ensures that the catalog files that
are specified will actually be used.
The attached patch file introduces this behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
