[EMAIL PROTECTED] writes: > You know, after writing the email yesterday, and then mulling it over, I was > coming to the same conclusion. I looked at the commons-configuration code, > and noticed that it was all pulled from Turbine!
And most of that code was pulled from JServ. > What I was thinking was something where if you have a value in JNDI, use > that. If you don't, then go to TR.props. That way, on an individual basis, > you could override TR.props via JNDI, without moving *EVERYTHING* into it. > > My challenge is that we want as many "admin configurable" parameters in JNDI > so our sysadmins can change mail servers, file systems etc to their hearts > content. > > Martin seems to be the main committer on the commons-config project. Do you > have any suggestions on how to move forward. > > Maybe something in Turbine that deals with pulling from multiple config > hierarchies, and then something in commons-config for JNDI configuration? ... +1 on implementing the Configuration interface using JNDI -- good suggestion, guys. > -----Original Message----- > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 26, 2003 5:33 AM > To: [EMAIL PROTECTED] > Subject: Re: VelocityEmail Change Proposal > > > [EMAIL PROTECTED] writes: > > >------_=_NextPart_001_01C2DD27.040896D0 > >Content-Type: text/plain; > > charset="iso-8859-1" > > >Hi all, > > >I hadn't heard back from anyone on this, whether people think this would be > >good or not. > > >After thinking more about this, I would like to change TR.props so that if > >you have a setting mail.session=jndi then it would pull the > >javax.mail.Session using the key mail.jndi.key. > > >mail.session=jndi > >mail.jndi.key=env/cmp/mail/myjdbcmailsession > > Hi, > > I was just giving this a quick though, mainly because I'm not too deep > into JNDI and this specific part of Turbine (I use the Mail interface > mainly to let my applications send me mails with Stack Traces of > crashes. ;-) ) > > Would it be possible to extend the commons-configuration so that we > get a generic "configuration is in JNDI" which we then can exploit > for Turbine? That would be really great. > > Just picking out a single property and then putting it into JNDI seems > to me duplicating work. > > Regards > Henning > > -- > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ > > Java, perl, Solaris, Linux, xSP Consulting, Web Services > freelance consultant -- Jakarta Turbine Development -- hero for hire > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Daniel Rall <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
