On Wed, 10 Nov 1999, Ernest Friedman-Hill wrote:
> First, using XML for bsaves would place an external requirement for an
> XML parser on Jess's users, or at least on those who wanted to do
> bsave/bload. I try hard to avoid external requirements because they
> generally just lead to problems and confusion.
If you can't add other packages then my proposal won't fly. I believe
Java is getting tighter integration with XML these days and would bet that
very soon most Java implementations will come with a SAX parser. However,
right now XML services are indeed an add-on.
> evolve, but it's still less work than writing the XML code by hand
> (also true, you could probably do XML encoding generically via
> reflection, but that would undoubtedly be slow and inefficient.)
>
I think you are being overly pessimistic. Doing a 2 minute search on
google I found this: http://www.inria.fr/koala/XML/serialization/
This GPL product appears to take binary representations of java
objects and convert them to XML. Deserialization converts from XML to
binary and then into java objects. There is no per-class handcoding.
If the issue is the size of XML files, gzip typically reduces XML file
size by an order of magnitude.
What is really cool in koala (but still alpha) is that you can use XSLt
for schema transformation -- which is a great idea.
-Alex-
___________________________________________________________________
S. Alexander Jacobson Shop.Com
1-212-697-0184 voice The Easiest Way To Shop
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
