Gareth
I Looked at your solution. I think IMO it is not necessary to add this toXML() to classes especially
changing DTD to accomodate this.
It should be possible to achieve exactly the same thing by having another XMLSerializer class do this.
It should be possible to use the solution w/o changing existing implementations.
For instance what if people already have an XML serializer/deserializer that works on beans and
jsut want to use that with Torque data objects?
For instance, I used JOX (www.wutka.com/jox) which serializes and deserializes beans.
The only problem it is so generic that it takes every "get" method and generates XML elements.
I am changing JOX to pass in an array of properties of interest .
-vasan
Gareth Boden wrote:
I have now.. but the interface confused me and I managed not to add the
third attachment and can't see a way to add it now. So it can be found
in the previously mentioned e-mail, if anyone knows how to add it...
G.
----------
From: Rodney Schneider
Reply To: Turbine Torque Users List
Sent: Tuesday, November 19, 2002 0:33 AM
To: Turbine Torque Users List
Subject: Re: retrieving objects as XML
On Mon, 18 Nov 2002 21:14, you wrote:
I posted some patches on September 19th (subject was "Re: Is torqueHi Gareth,
dying?") to do this sort of thing using Betwixt.
Have you submitted these patches to Scarab? This way they won't get forgotten about.
-- Rodney
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
