Forums

Michael Hucka wrote:
> Let me ask a different question. If we don't go the route
> of implementing a pure java version, are there things that
> we can do with the current scheme to reduce implementation
> and portability headaches for people?
>
> Maybe some of the problems are things that we can fix by
> taking a hard look at the current code base, and improving
> that. If we can address even 50% of the problems, it sounds
> like that would be a significant help (roughly X * 50% fewer
> headaches in the world, where X is the number of people
> trying to deploy Java-based apps with libSBML).
>
>
One of the big, big, problem that force us to not use libsbml most of
the time for biomodels DB is crash of our tomcats during call to libsbml
functions.
And the problems is not necessary coming from libsbml but may be from
JNI or swig.

We have also some systems that are in general not supported, like osf,
solaris, old linux distrib but have a working JVM.

Nico

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

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

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