Hi,

did you have a look at
http://torque-addons.sourceforge.net/XML-Import-Export/index.html ?

Kind regards

Juergen

> -----Ursprüngliche Nachricht-----
> Von: Perumal, Lakshmi [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 22. Januar 2007 12:13
> An: Turbine Users List
> Betreff: RE: Generate xml from the output of the peer classes
> 
> Hi
> 
> Jaxme is similar to jaxb and requires a compile each time. I would like
> to use a xml binder like castor or digester which could generate the xml
> file on each request from the user.
> 
> My question was whether this generation of xml can be internally mapped
> in torque rather than using these binders. I would like to use the same
> peer classes and base classes which have the getters and setters rather
> than using a bean class (which maps it again). I hope you got my
> question.
> Expecting your reply soon
> 
> 
> -----Original Message-----
> From: Thomas Vandahl [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 20, 2007 2:15 AM
> To: Turbine Users List
> Subject: Re: Generate xml from the output of the peer classes
> 
> Perumal, Lakshmi wrote:
> > Hi
> > The output of the peer classes (which are used to query the DB )
> result in a set of query results should be displayed in a xml format.
> > My question is the achieve this, is it necessary to make use of xml
> binders (like digester) or is it possible to change configurations in
> torque to get the xml file with the output of the query.
> 
> Just for the record: this is actually a Torque question (see
> db.apache.org/torque for mailing lists).
> 
> The Torque generator can dump data from the database in XML format. I
> don't know if it is possible to use this from an application. I use the
> JAXB approach (look for JaxMe) together with a manual mapping. Works
> just fine and gives me the advantage of schema validation.
> 
> Bye, Thomas.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to