Hi everybody!
I'm new to xalan (and xerces) and am looking for some information on the
livecycle of Xalan documents (fragments) and nodes.
I haven't found any documentation on the livecycle of Xalan Documents/Nodes.
I'm developing a program that periodically collects data of arbitrary type.
I would like to use XML as data format as it is flexible and the collected
data eventually gets transformed several times.
Usage scenario:
(best viewed with fixed-sized font)
THREAD1 THREAD2
------------------- -------------------
| datacollector | | dataprocessor |
------------------- -------------------
| |
collect data |
| |
create xml |
representation |<-----------
| ----------- | |
----------->| queue | | |
----------- | |
| | |
----------->get data |
from queue |
| |
transfrom data |
using compiled |
stylesheet |
| |
----------- put data |
| into queue |
| | |
v -------------
-----------
| queue |
-----------
|
V
further
processing
with another
thread...
Is it possible to create a document (fragment), keep it, move it around
and perform an arbitrary number of transformations and destroy it when all
further processing is done or is the newly created document (fragment) bound
to a specific instance of a xalan class (XalanTransformer/...) and will be
destroyed whenever the instance is destroyed/goes out of scope?
What would be the best container for the generated data: a Xerces (I)DOM
document, a Xalan document (fragments) or a single Xalan node?
And what about compiled stylesheets? Are they bound to a specific instance
of a xalan class or can I create and destroy it whenever I want?
Any help is greatly appreciated.
Many thanks in advance
Wolfgang
--
Wolfgang Schell
[EMAIL PROTECTED]
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
