I used the admin webapp for tomcat 5.5 to create the following two
jndi resources.
jdbc/continuum
jdbc/users
This resulted in the following context being created in the server.xml
<Context
path="/continuum-webapp-1.1-SNAPSHOT">
<Resource
name="jdbc/continuum"
type="javax.sql.DataSource"
password="continuum"
driverClassName="org.postgresql.Driver"
maxIdle="2"
maxWait="5000"
username="continuum"
url="jdbc:postgresql://127.0.0.1/continuum"
maxActive="4"/>
<Resource
name="jdbc/users"
type="javax.sql.DataSource"
password="continuum"
driverClassName="org.postgresql.Driver"
maxIdle="2"
maxWait="5000"
username="continuum"
url="jdbc:postgresql://127.0.0.1/users"
maxActive="4"/>
<WatchedResource>/opt/tomcat/conf/context.xml</WatchedResource>
<WatchedResource>/opt/tomcat/conf/context.xml</WatchedResource>
</Context>
On 10/19/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Hi all,
After going through the build process for continuum v1.1-SNAPSHOT, the
end result is a WAR file, which I dropped into a tomcat container.
On startup I get the following error:
2006-10-19 15:07:29,654 [main] INFO PlexusContainer -
Loading on
start [role]: [org.apache.maven.continuum.Continuum]
2006-10-19 15:07:30,112 [main] ERROR 1-SNAPSHOT] -
Exception
sending context initialized event to listener instance of class
org.codehaus.ple
xus.xwork.PlexusLifecycleListener
org.jpox.exceptions.ConnectionFactoryNotFoundException: Connection
Factory "java
:comp/env/jdbc/continuum" not found
It looks like there are extra steps to get continuum to work as a WAR file.
Does anyone have any instructions anywhere?
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
