geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianny Damour <gianny.dam...@optusnet.com.au>
Subject Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Date Tue, 18 Mar 2008 12:41:39 GMT
Hello,

This is a problem with the deployment descriptor. You name of the  
clustering substitution group element is tomcat-clustering-wadi for  
tomcat and not clustering-wadi. As a matter of fact, I have on my to- 
do list a task to refactor substitution group element builders for  
Tomcat, Jetty and OpenEJB so that all of them offer the same external  
structure to end-users.

Here is an updated DD:

<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2">

     <environment>
         <moduleId>
             <groupId>org.codehaus.wadi</groupId>
             <artifactId>wadi-webapp</artifactId>
             <version>2.0M3-SNAPSHOT</version>
             <type>war</type>
         </moduleId>
     </environment>

    <tomcat-clustering-wadi/> <-- this is the correct element name to  
use for tomcat.

</web-app>

Thanks,
Gianny


On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote:

> I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ 
> clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1.   
> even though org.apache.geronimo.configs/jetty6-clustering-builder- 
> wadi//car is running, deploying the sample application resulted in  
> an error given below:
>

> error: cvc-complex-type.2.4a: Expected elements 'context- 
> root@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- 
> dir@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1  
> clustering@http://geronimo.apache.org/xml/ns/j2ee/application-2.0  
> web-container@http://geronimo.apache.org/xml/ns/naming-1.2  
> host@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- 
> context@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1  
> disable-cookies@http://geronimo.apache.org/xml/ns/j2ee/web/ 
> tomcat-2.0.1 valve-chain@http://geronimo.apache.org/xml/ns/j2ee/web/ 
> tomcat-2.0.1 listener-chain@http://geronimo.apache.org/xml/ns/j2ee/ 
> web/tomcat-2.0.1 tomcat-realm@http://geronimo.apache.org/xml/ns/ 
> j2ee/web/tomcat-2.0.1 manager@http://geronimo.apache.org/xml/ns/ 
> j2ee/web/tomcat-2.0.1 cluster@http://geronimo.apache.org/xml/ns/ 
> j2ee/web/tomcat-2.0.1 abstract-naming-entry@http:// 
> geronimo.apache.org/xml/ns/naming-1.2 ejb-ref@http:// 
> geronimo.apache.org/xml/ns/naming-1.2 ejb-local-ref@http:// 
> geronimo.apache.org/xml/ns/naming-1.2 service-ref@http:// 
> geronimo.apache.org/xml/ns/naming-1.2 resource-ref@http:// 
> geronimo.apache.org/xml/ns/naming-1.2 resource-env-ref@http:// 
> geronimo.apache.org/xml/ns/naming-1.2 message-destination@http:// 
> geronimo.apache.org/xml/ns/naming-1.2 security-realm-name@http:// 
> geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 service@http:// 
> geronimo.apache.org/xml/ns/deployment-1.2 persistence@http:// 
> java.sun.com/xml/ns/persistence' instead of 'clustering-wadi@http:// 
> geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here
>
>


> The deployment plan I am using is:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web/ 
> tomcat-1.2">
>
>     <environment>
>         <moduleId>
>             <groupId>org.codehaus.wadi</groupId>
>             <artifactId>wadi-webapp</artifactId>
>             <version>2.0M3-SNAPSHOT</version>
>             <type>war</type>
>         </moduleId>
>     </environment>
>
>    <clustering-wadi/>
>
> </web-app>
>


Mime
View raw message