JDG Remote Client-Server Mode Usage Example: Difference between revisions
Jump to navigation
Jump to search
(→GitHub) |
(→Maven) |
||
Line 25: | Line 25: | ||
<pre> | <pre> | ||
<?xml version="1.0" encoding="UTF-8"?> | |||
<jboss-deployment-structure> | |||
<deployment> | |||
<dependencies> | |||
<module name="org.infinispan.client.hotrod" slot="jdg-7.0"/> | |||
</dependencies> | |||
</deployment> | |||
</jboss-deployment-structure> | |||
</pre> | </pre> | ||
Revision as of 14:42, 4 May 2017
Internal
Overview
The example is deployed in a wrapper servlet, to facilitate interaction.
GitHub
Maven
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-remote</artifactId> <version>8.3.0.Final-redhat-1</version> <scope>provided</scope> </dependency>
If support for remote client-server JDG is deployed within the target EAP (preferred), declare the dependency <scope>provided</scope> and configure the jboss-deployment-structure.xml as shown:
<?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <dependencies> <module name="org.infinispan.client.hotrod" slot="jdg-7.0"/> </dependencies> </deployment> </jboss-deployment-structure>
Otherwise, all required dependencies it with your deployment, by not declaring them "provided".