Hello,
I am looking for the ideal internal format of some Metadata in an
information catalog system.
The (Meta)dataobjects result from a relational database (well known
schema) and describe environmental information. There is not really any
business logic in these data objects. In the past I just needed to
render HTML from these data objects. (However, these data objects are
quite complex and are build by many dependent SQL queries. So during
construction I need access to some attributes.)
Now I need
1) to render XML from these data objects and
2) to render the exact same HTML as before from external XML provided by
external sources
So for me it seems that I can benefit from an internal XML format
(considering that I am not really happy with the actual internal data
format consisting of some kind of entity (no EJB) with atomic- and
self-made-java.util.Vector-based collection attributes.
In the near future we possibly provide a data maintenance tool, too.
One issue is, that due to distributed access (RMI) to many sources, I
need a transport efficient format. (memory and speed is also an issue,
of course)
My questions:
As far as I know, dom4j currently does not support serialization at all.
When will this change and will the serialized format be tuned for
efficiency? (I tested JDOM beta 6 and got about twice the volume I had
from the already big XML-source...)
Or would you recommend to create an XML-file and use this (e.g.
compressed) for communication?
Is this use case a typical one for the use of an lightweight XML-API?
Do you think, Java-XML-Java Mapper tools (like Jato or Castor) would be
more appropriate in this use case?
Thanks in advance,
Sven Behrens.
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-user
