Adding Resources Examples
+Adding Resources Examples
The add-resources goal allows you to add resources such as datsources etc to a running WildFly instance.
Adding datasources
+Adding datasources
This can be combined with the add-resource goal to automatically deploy the datasource drivers.
The example below shows how to add a datasource that uses the default h2 database:
Adding datasources<
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
- <version>3.0.0.Beta1</version>
+ <version>3.0.0.Final</version>
<executions>
<execution>
<id>add-datasource</id>
@@ -243,7 +243,7 @@ Adding datasources<
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
- <version>3.0.0.Beta1</version>
+ <version>3.0.0.Final</version>
<executions>
<execution>
<id>deploy-postgresql</id>
@@ -325,7 +325,7 @@ Adding datasources<
Adding datasources<
The xml tags in the <properties> element correspond directly to the DMR nodes in the corresponding management operation. If you need to use DMR nodes of a non-primitive type then you must prefix the value with the !! escape sequence, which will cause the value to be interpreted as a string representation of a DMR node. For example in the <xa-data-source-properties> element about <xa-datasource-properties> is a DMR property list.
Adding other resources
+Adding other resources
It is also possible to deploy resources other than datasources, the example below shows how to deploy a JMS queue:
Adding othe
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
- <version>3.0.0.Beta1</version>
+ <version>3.0.0.Final</version>
<executions>
<execution>
<id>add-jms-queue</id>
@@ -370,7 +370,7 @@ Adding othe
Adding resources in domain mode
+Adding resources in domain mode
Adding resources in domain mode works the same as the examples above, except you need to add the <profiles> property as well as specify at least one profile.