Perhaps this type of thing would be better pulled from the deployment descripton then TR.props...
> -----Original Message----- > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 26, 2003 4: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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
