db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Monroe" <Greg.Mon...@DukeCE.com>
Subject RE: Plan to enhance Database Mapping info
Date Fri, 28 Apr 2006 14:08:45 GMT

> -----Original Message-----
> From: Thomas Vandahl [mailto:thomas.vandahl@tewisoft.de] 
> Please keep in mind that the Avalon interface 
> (Torque/TorqueComponent) should be updated as well.

In digging into the code some more, I probably won't add the
methods to the Torque class.  Instead, I'll just add an 
initialize() method to the DatabaseMap class.  This means
that not interfaces will need to be updated.  More on this
when I answer Thomas F's note.

> What about the managers? Maybe I'm the only one who uses JCS caching, 
> but I would love to see them considered...
> This would require some getManager() method in all objects and 
> getOmClass(), getPeer() and getTableMap() in the managers.

Good point and the reason to run this by everyone first.  Once 
again, more on this in the next note.
> Just one question for my understanding. Why do you need special 
> introspection code if you can have Beans generated? Could you 
> give some example where this is useful?

In my particular case, I'm looking at having some generic XML 
import and export code that uses the Torque generated schema DTD. 

For the import case, as the XML file is parsed, the element and 
attribute tag strings have to be mapped into the Torque objects
that will be populated and saved.  Since I want it to be generic 
so that no code has to be changed as tables and columns are added
or modified, I need a fully populated map structure find this 

In the export case, I want to generate the proper element and 
attribute tags from a (possibly mixed) List of objects generated
by application specific code.  So I have to be able to inspect
each object on the list and find the matching strings that
identify it in the XML output file.

Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are confidential communication
or may otherwise be privileged or confidential and are intended solely for the individual
or entity to whom they are addressed.  If you are not the intended recipient you may not rely
on the contents of this email or any attachments, and we ask that you  please not read, copy
or retransmit this communication, but reply to the sender and destroy the email, its contents,
and all copies thereof immediately.  Any unauthorized dissemination, distribution or copying
of this communication is strictly prohibited.

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message