Re: XML/Convert.java

[Lars Martin <lars@softwarebuero.de>]

Hi,

Wed, 22 Mar 2000 Thomas Guettler wrote:
>I liked it because it is much faster than working with proxy-objects.
>For serializing a proxy DOM i needed 90sec. Serializing
>the in memory representation needed 2sec. 
>
>In Enhyda you use a precompiled dom-object, which you use
>to add data taken from JDBC. The data you add is added for each
>request. This means the changes to the DOM shouldn't get 
>persistent.

Well, this is a perfect example where the convertNode() method will 
extremely boost  your application. ;-)

>Currently I try to make the changes of the DOM on serverside.
>I want to change the DOM with xslt and then serialize it.
>But how can I return the result (plaintext xml) to the client?
>I could use a bytearray like org.ozoneDB.xml.util.DOMConverter(),
>but this method returns always null. 

Serverside code is most effective for applications that uses a lot
of database method calls. There are different possibilities to return
the xml file to the client side. 1. String, 2. StringBuffer, 3. ByteArray
... but I don't know the advantages or disadvantages of each kind
iin the way of cost effectiveness.

>Or, but I don't know if it is possible, I use an OutputStream to
>get the result to the client.
>Is it possible to have a OzoneObject with a memberfunction who
>takes an OutputStream as argument? (Outputstream is not serializable)

I don't understand this! Please give more information about that.

Regards,
Lars
--
________________________________________________________________
Lars Martin                         mailto:lars@softwarebuero.de
softwarebuero m&b (SMB)              http://www.softwarebuero.de