esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <richard.hir...@siemens.com>
Subject AW: Using a container-based Datasource
Date Mon, 22 Dec 2008 15:01:59 GMT
Good idea. 

By the way, I already got the datasource with jndiName = "esme" working in the stax environment.
Details here - http://blog.esme.us/esme-in-the-cloud-it-works/

D. 

-----Urspr√ľngliche Nachricht-----
Von: David Pollak [mailto:feeder.of.the.bears@gmail.com] 
Gesendet: Montag, 22. Dezember 2008 15:28
An: esme-dev@incubator.apache.org
Betreff: Re: Using a container-based Datasource

Dick,
How about if we have it based on a property so it's user (deployer)
configurable?

Thanks,

David

On Sat, Dec 20, 2008 at 9:31 PM, Hirsch, Richard <richard.hirsch@siemens.com
> wrote:

> I was looking at the possibility of using a datasource for the Stax
> deployment, because it is not allowed to use local files or dbs (which we
> currently have with derby).
>
> I looked at the description of using a datasource in the lift wiki (
> http://liftweb.net/index.php/HowTo_configure_a_JNDI_data_source_for_lift_and_Tomcat)
> and suggest that we change the first code line in the "Boot.scala" from
> DefaultConnectionIdentifier.jndiName = "esme" to
>  DefaultConnectionIdentifier.jndiName = "jdbc/esme".
>
> D.
>



-- 
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

Mime
View raw message