Thomas Zajac

Then this was your SBML file that was wrong ? Not sure how we could prevent that and send a nice error message or warning. May be we could test...

I think its a bit difficult. The specification L3V1 §4.10 says, that the content of the message-tag has the namespace xhtml. So I thought that the sbml-file could look like:...

Yes, written like that, the first fragment should be valid and the message element should be processed by the SBMLCoreParser. I will have a look at it. Original comment by:...

- **status**: open-works-for-me --> open-accepted Original comment by: niko-rodrigue

I don't understand why it is necessary to access the parentSBMLElement? This might be null in some cases. What is it needed for? It seems the code fragment above should...

Andreas, this code is a part of the parsing, in StringParser.processStartElement and it is working fine. The problem is happening if you define the xhtml namespace in the message element...

- **milestone**: --> jsbml 1.0 Original comment by: niko-rodrigue

- **Group**: jsbml 1.0 --> jsbml 1.2 Original comment by: niko-rodrigue

This is the javadoc from libsbml : public String toSBML() Returns a string that consists of the partial SBML describing this object. This is primarily provided for testing and debugging...

- **labels**: 1240513 --> - **priority**: 5 --> 4 - **summary**: SBML String representation for all SBase inheritors --> implementation of the toSBML() methods Original comment by: niko-rodrigue