We're updating the issue view to help you get more done. 

conf/server.xml is not populated with the data source when the container Id is tomcat5x

Description

The conf/sever.xml generated by Cargo does not contain the datasource configuration when the container is tomcat 5x. Below is the cargo-maven2-plugin configuration. I do not believe this is an issue with the plugin since changing the <containerId> to tomcat4x results in the datasource configuration in conf/server.xml

<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>0.3.1</version>
<configuration>
<container>
<containerId>tomcat5x</containerId>
<home>${cargo.tomcat5x.home}</home>
</container>
<configuration>
<properties>
<cargo.datasource.datasource>
cargo.datasource.url=jdbc:edbc://testsvr.mikon.com:GN7/termite_dev|
cargo.datasource.driver=ca.edbc.jdbc.EdbcDriver|
cargo.datasource.username=ingres|
cargo.datasource.password=platform2000|
cargo.datasource.type=javax.sql.DataSource|
cargo.datasource.jndi=jdbc/Termite
</cargo.datasource.datasource>
</properties>
</configuration>
<wait>false</wait>
</configuration>
<executions>
<execution>
<id>start-container</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start</goal>
</goals>
</execution>
<execution>
<id>stop-container</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
</plugin>

Status

Assignee

Unassigned

Reporter

Paul Spencer

Components

Fix versions

Affects versions

0.9

Priority

Major