Because of HiveMind, you may always override a Tapestry implementation of a service.
In this case, the service is tapestry.request.RequestLocaleManager. i.e. <implementation service-id="tapestry.request.RequestLocaleManager"> <invoke-factory> ... </invoke-factory> </implementation> On 10/7/05, Siegenthaler Mario, Bedag <[EMAIL PROTECTED]> wrote: > Hi > Our application gets the information about the users locale out of a > database. Since the user must log in before he get to our application > (the apache in front of the tomcat takes care of that), we'd like to > welcome our users in their respective native language. After looking > through the tapestry sources we found the RequestLocaleManager interface > and found it to be the perfect place for our locale logic (instead of > reading it out of the http headers we make a call to the database with > request.getRemoteUser()). > However the RequestLocaleManager implementation is not changable outside > of tapestry itself since there is no configuration-point for it. Or at > least I was unable to find one. Does our approach to the problem make > sense and, if yes, would it be possible to add such a configuration > point? > > Sincerly & thanks for the great application > Siegenthaler Mario > Bedag Informatik AG > > --------------------------------------------------------------------- > 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 Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
