Updated Deployment to JEE and Servlet containers (markdown)

Ralph Soika
2016-12-18 10:51:35 +01:00
parent f8d220ceff
commit ee27ff3616

@@ -4,7 +4,7 @@
For JBoss 7.X, Wildfly 8.X (not tested for 9.X & 10.X) when deploying gitbucket, you will probably face the following deployment error: `java.lang.NoClassDefFoundError: com/sun/net/ssl/internal/ssl/Provider`. For JBoss 7.X, Wildfly 8.X (not tested for 9.X & 10.X) when deploying gitbucket, you will probably face the following deployment error: `java.lang.NoClassDefFoundError: com/sun/net/ssl/internal/ssl/Provider`.
Due to class loading restrictions inside JBoss/Wildfly, you need to explicitly allow gitbucket to access some classes from the jdk. For that, modifiy gitbucket.war and add the following under `WEB-INF\jboss-deployment-structure.xml` Due to class loading restrictions inside JBoss/Wildfly, you need to explicitly allow gitbucket to access some classes from the jdk. For that, modify gitbucket.war and add the following under `WEB-INF\jboss-deployment-structure.xml`
``` ```
<jboss-deployment-structure> <jboss-deployment-structure>
@@ -21,14 +21,26 @@ Due to class loading restrictions inside JBoss/Wildfly, you need to explicitly a
</jboss-deployment-structure> </jboss-deployment-structure>
``` ```
## Wildfly 9.X ## Wildfly 9.X, Wildfly 10.X
*TODO* Wildfly 9.X & 10.X have the same class loading restrictions as previous versions. So also here you need to explicitly allow gitbucket to access some classes from the jdk. are similar to previous versions. Modify gitbucket.war and add the following under `WEB-INF\jboss-deployment-structure.xml`
## Wildfly 10.X
*TODO*
```
<jboss-deployment-structure>
<deployment>
<dependencies>
<system export="true">
<paths>
<path name="com/sun/net/ssl/internal/ssl" />
<path name="com/sun/net/ssl" />
</paths>
</system>
<!-- add snakeyaml dependency -->
<module name="org.yaml.snakeyaml"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
```
# Tomcat # Tomcat