 |
 |
Quick Links
- Home
- Installation
- Usage
- Getting help
Containers
- Geronimo
- GlassFish
- JBoss
- Jo!
- JRun
- Payara
- Resin
- WebLogic
- WebSphere
- WildFly
- WildFly 8.x
- WildFly 9.x
- WildFly 10.x
- WildFly 11.x
- WildFly 12.x
- WildFly 13.x
- WildFly 14.x
- WildFly 15.x
- WildFly 16.x
- WildFly 17.x
- WildFly 18.x
- WildFly 19.x
- WildFly 20.x
- WildFly 21.x
- WildFly 22.x
- WildFly 23.x
- WildFly 24.x
- WildFly 25.x
- WildFly 26.x
- WildFly 27.x
- WildFly 28.x
- WildFly 29.x
- WildFly 30.x
- WildFly 31.x
- WildFly 32.x
- WildFly 33.x
- WildFly 34.x
- WildFly 35.x
- WildFly Swarm
Independent extensions
Development
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Container supportHere are the configurations that currently support DataSource or Resource configuration:
Container-specific notes:
Notes:
DataSource propertiesDataSources are added through pipe-delimited configuration properties that starts with cargo.datasource.datasource1=cargo.datasource.url=jdbc:mydriver:userdb\|cargo.datasource.driver=org.database.Driver\|... cargo.datasource.datasource2=cargo.datasource.url=jdbc:mydriver:referencedb\|cargo.datasource.driver=org.database.Driver\|... Here are the properties that are valid for this:
JMS resource propertiesJMS resources (such as connection factories, queues or topics) are added through pipe-delimited configuration properties that starts with cargo.resource.resource.jms.cf=cargo.resource.name=jms/cf/MyCf\|cargo.resource.type=javax.jms.ConnectionFactory\|cargo.resource.id=MyCf cargo.resource.resource.jms.queue=cargo.resource.name=jms/MyQueue\|cargo.resource.type=javax.jms.Queue\|cargo.resource.id=MyQueue Here are the properties that are valid for this:
Java EE vs. Jakarta EE Even when you use Codehaus Cargo with a Jakarta EE container, you can keep on using Please note that this doesn't work the other way round: Other resource propertiesAll other resources are added through pipe-delimited configuration properties that starts with cargo.resource.resource1=cargo.resource.name=resource/apple\|cargo.resource.class=org.mycompany.Apple\|... cargo.resource.resource2=cargo.resource.name=resource/pear\|cargo.resource.driver=org.mycompany.Pear\|... Here are the properties that are valid for this:
Known issuesThe Glassfish container has various known issues with regards to DataSource support. When you try to use GlassFish 3.x or GlassFish 4.x with Derby DataSources, you might run into issues where Glassfish doesn't start, and the Glassfish logs show you messages such as the below: java.lang.SecurityException: sealing violation: package org.apache.derby is sealed This is because Glassfish is already shipped with Derby, and the Glassfish class loaders do not know how to the manage the situation where the same class is duplicated. So, the solution is to simply remove the Derby JAR from dependencies; on the other hand this is not feasible if you are using the same CARGO profile with different containers. Here is how you can work around the issue: <dependencies>
<dependency>
<groupId>org.apache.derby</groupId>
<artifactId>derby</artifactId>
<version>${derby.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
...
<build>
<plugins>
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven3-plugin</artifactId>
<version>${cargo.version}</version>
<!--
This configuration will be used in general.
-->
<configuration>
<container>
<dependencies>
<dependency>
<groupId>org.apache.derby</groupId>
<artifactId>derby</artifactId>
</dependency>
</dependencies>
<systemProperties>
<derby.system.home>\${project.build.directory}/derby</derby.system.home>
</systemProperties>
</container>
<configuration>
<properties>
<cargo.datasource.datasource.derby>
cargo.datasource.driver=org.apache.derby.jdbc.EmbeddedDriver|
cargo.datasource.url=jdbc:derby:derbyDB;create=true|
cargo.datasource.jndi=jdbc/CargoDS|
cargo.datasource.username=APP|
cargo.datasource.password=nonemptypassword
</cargo.datasource.datasource.derby>
</properties>
</configuration>
...
</configuration>
</plugin>
</plugins>
</build>
<profiles>
...
<profile>
<id>glassfish3x</id>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven3-plugin</artifactId>
<configuration>
<container>
<containerId>glassfish3x</containerId>
<artifactInstaller>
<groupId>org.glassfish.main.distributions</groupId>
<artifactId>glassfish</artifactId>
<version>3.1.2.2</version>
</artifactInstaller>
<dependencies>
<!--
Remove the org.apache.derby dependency since GlassFish 3.x is already
shipped with Derby, and adding the dependency twice results in a
java.lang.SecurityException: sealing violation: package org.apache.derby.
-->
<dependency>
<groupId>org.apache.derby</groupId>
<artifactId>derby</artifactId>
<classpath>none</classpath>
</dependency>
</dependencies>
</container>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
</profile>
</profiles>
ExamplesUsers of the Java API can take a look at the following classes as example:
Users of the Maven 3 Plugin can refer to the Maven 3 Archetype showing DataSource support. |
| Copyright 2004-2024. All rights reserved unless otherwise noted. |
Click here to read our privacy and cookie policy |