I'd be happy to see town ditched in favour of JDBC, if there was comprehensive enough config. put it this way, id like to set up seperate tables for each kind of repository, and might like to be able to map real field names onto the name of their contents, EG: <jdbcrepository name="users" db="james" table="users"> <field fieldname="ident" contents="password"> <connection file="blah>" > -----Original Message----- > From: okidz [mailto:okidz]On Behalf Of Oki DZ > Sent: Wednesday, May 30, 2001 3:21 AM > To: [EMAIL PROTECTED] > Subject: Re: Town > > > Charles Benett wrote: > > 'Town' may well be replaced in the next release. > > Either with straight JDBC or with the Torque/Peer OR tools from > > jakarta-turbine. > > Straight JDBC wouldn't be that good, IMO; you'd be tempted to use SQL > statements that are server spesific. > > IMHO, it would be great if James could be set like Tomcat; ie: column > names on the tables can be reconfigured via an XML config file. I'd also > like to attach "listeners" to the JDBC connection, so that on > insert/update/delete on the tables I'd have a chance to do something. It > would be great to be able to record the from/to addresses on a separate > table, for example. Could be useful, on back-end servers that don't > (yet) support triggers. > > Oki > > --------------------------------------------------------------------- > 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]
