Properties which take primitive values (boolean, long, double, etc.) can use smart translator.
Properties which take object values (configurations, services, etc.) can use object translator I don't think there's a lot of overlap.. On Tue, 13 Jul 2004 16:20:30 +0200, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Of course, there'll be a configuration to define prefixes, and > > services to implement each type of prefix. If the one you need isn't > > available, then you'll be able to supply your own. > > > > Sounds great! I assume this would then supercede the smart translator. > I.e. if no prefix is given the smart translator is applied. Otherwise > we'd have to write things like: > > boolean:true > long:2 > > which wouldn't be very fun ;-) > > Thinking of it, maybe this is just the next version of the smart > translator, which is configurable and even smarter :-) > > --knut > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
