Forums

Hi all,

Still we are facing the difficulty how to include all package parsers in
the JSBML binary distribution. In the trunk, the configuration file that
contains all mappings from namespaces to the actual parsers is in a
comment block. If somebody wants to use an SBML package at the moment,
the specific comment has to be removed locally - comiting this change is
then prohibited.

I now wonder why it is actually not possible, to simply include all
possible package parsers there and, instead of throwing an error if some
parser cannot be loaded, to log a warning that a package could not be
parsed correctly.

A difficulty I see with this approach would be that customized packages,
i.e., packages that are really defined by some individual group and not
part of some JSBML release would have to be registered in the
configuration file as well (by the people developing this specialized
package). On the other hand, this would not really be the business of
the JSBML developers.

Summary: I would be very happy to get to know why at the moment JSBML
crashes if it tries to load a non existing package parser.

Cheers
Andreas

--
Dr. Andreas Dräger
University of Tuebingen
Center for Bioinformatics Tuebingen (ZBIT)
Sand 1
72076 Tübingen
Germany

Phone: +49-7071-29-78982
Fax: +49-7071-29-5091

____________________________________________________________
To manage your jsbml-development list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/jsbml-development

For a web interface to the jsbml-development mailing list, visit
http://sbml.org/Forums/

For questions or feedback about the jsbml-development list,
contact sbml-team@caltech.edu