Bug#268786: libxml-commons-resolver1.1-java: does not install CatalogManager.properties file

[Michael Smith]

--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: libxml-commons-resolver1.1-java
Version: 1.1-3
Severity: normal

Hi,

Is there a reason why libxml-commons-resolver1.1-java doesn't
install a CatalogManager.properties file?

I think it should and /etc/xml-commons-resolver/CatalogManager.properties
seems like an appropriate location.

As far as the content of the file, there's an upstream example at:

  http://xml.apache.org/commons/components/resolver/CatalogManager.properties

But that shouldn't be used off-the-self. At a minimum, the value
for the 'catalogs' property should be changed. It should be:

  catalogs=/etc/xml/catalog

Also, maybe the default for the 'verbosity' property should be
cranked down. The default in the upstream example file is '99',
which is the max. I reckon most users will probably get annoyed by
the amount of reporting that generates.

If/when the package is updated to install CatalogManager.properties,
the README.Debian file should be updated to tell people how to use -

  This package installs a CatalogManager.properties file in the
  /etc/xml-commons-resolver directory. Among other things, the
  CatalogManager.properties file tells the resolver where to find
  XML catalog files to use. Debian uses a single master catalog
  file -- /etc/xml/catalog -- so the CatalogManager.properties
  that this package installs points to that file.

  In order for the resolver to be able to find and use the
  CatalogManager.properties files, you need to include the
  *directory* that contains it -- the /etc/xml-commons-resolver
  directory -- in your Java classpath, either by specifying it on
  the Java command-line or via the CLASSPATH environment variable:

    export CLASSPATH=/etc/xml-commons-resolver:$CLASSPATH

That's it. Thanks,

  --Mike Smith

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (70, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-bytemark-uml-20040706-1
Locale: LANG=C, LC_CTYPE=C

Versions of packages libxml-commons-resolver1.1-java depends on:
hi  j2re1.3 [java2-runtime]    1.3.1.02b-2   Blackdown Java(TM) 2 Runtime Envir
ii  j2re1.4 [java2-runtime]    1.4.1.99rc1-2 Blackdown Java(TM) 2 Runtime Envir
ii  sablevm [java1-runtime]    1.1.6-2       Free implementation of Java Virtua

-- no debconf information

--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="CatalogManager.properties"

######################################################################## 
# CatalogManager provides an interface to the catalog properties.
# Properties can come from two places: from system properties or
# from a CatalogManager.properties file. This class provides a
# transparent interface to both, with system properties preferred 
# over property file values.

#######################################################################
# Catalog Files:
# The semicolon-delimited list of catalog files.
# Example: catalogs=./xcatalog;/share/doctypes/catalog

catalogs=/etc/xml/catalog

#######################################################################
# Relative Catalogs:
# If false, relative catalog URIs are made absolute with respect to the
# base URI of the CatalogManager.properties file. This setting only 
# applies to catalog URIs obtained from the catalogs property in the
# CatalogManager.properties file
# Example: relative-catalogs = [yes|no]

relative-catalogs=yes

#######################################################################
# Verbosity:
# If non-zero, the Catalog classes will print informative and debugging
# messages. The higher the number, the more messages.
# Example: verbosity = [0..99]

verbosity=99

#######################################################################
# Prefer:
# Which identifier is preferred, "public" or "system"?
# Example: xml.catalog.prefer = [public|system]

prefer=system

#######################################################################
# Static-catalog:
# Should a single catalog be constructed for all parsing, or should a
# different catalog be created for each parser?
# Example: static-catalog = [yes|no]

static-catalog=yes

#######################################################################
# Allow-oasis-xml-catalog-pi
# If the source document contains "oasis-xml-catalog" processing 
# instructions, should they be used?
# Example: allow-oasis-xml-catalog-pi = [yes|no]

allow-oasis-xml-catalog-pi=yes

#######################################################################
# catalog-class-name
# If you're using the convenience classes 
# org.apache.xml.resolver.tools.*, this setting allows you to specify
# an alternate class name to use for the underlying catalog.
# Example: catalog-class-name=org.apache.xml.resolver.Resolver

--r5Pyd7+fXNt84Ff3--