On 23.11.13 08:16, maremv wrote:
> 
> My tomcat version is 7.0.47, this is the 3rd or 4th time i have created
> the turbine project from scrach using the maven 4.0 script and i get the
> same error everytime. i have not modified any of the propertiey files, I
> figured if i built the default app using the maven archetypes it could
> at least get the default page saying that it was up and running. It
> seems to be complaining that it cannot log into the database - which
> would make since since i have not - nor do i know where - to enter in
> the username and password to do such. The Torque.properties file looks
> like it would be a good canidate - but not sure how to figure out what
> the propertie names are that i need to add/modify.
> 
> 
> -------------- Torque.properties:
> 
> torque.database.default=turbine
> torque.database.turbine.adapter=mysql
> 
> # Using JNDI
> torque.dsfactory.turbine.factory=org.apache.torque.dsfactory.JndiDataSourceFactory
> 
> torque.dsfactory.turbine.jndi.path=java:comp/env/jdbc/Turbine
> torque.dsfactory.turbine.jndi.ttl=300000
> 
> # Determines if the quantity column of the IDBroker's id_table should
> # be increased automatically if requests for ids reaches a high
> # volume.
> 
> torque.idbroker.cleverquantity=true
> 
> # Determines whether the managers cache instances of the business objects.
> # And also whether the MethodResultCache will really cache results.
> 
> torque.manager.useCache = true
> 

See the Tomcat documentation on JDBC datasources at
http://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html#JDBC_Data_Sources

You need to define a data source for your application.

As an alternative, you may define the Torque data source on your own.
See the section on "SharedPoolDataSourceFactory" at
http://db.apache.org/torque/torque-3.3/releases/torque-3.3/runtime/reference/initialisation-configuration.html


Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to