First a reservation: I'm not an expert!

But I'm willing to help.


Your configurations seem to be incomplete:

1) Did you specify a context for your webapp? Please see
http://tomcat.apache.org/tomcat-5.0-doc/config/printer/context.html

2) How does your hivemind configuration for tapestry.url.ServiceEncoders
look like?


</Firas>


-----Original Message-----
From: Huang Gehua [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 28, 2006 8:13 PM
To: Tapestry users
Subject: friendly url problem when setting context path to the web root
directory

I was a beginner of Tapestry 4.0.x.
In my T4 project I've activated Friendly URLs and it works fine.
But when i deploy the T4 project to a new Virtual Host and set the context
path as the web root I meet problems.I can visit the Home page with
http://10.0.0.201/app.But can't visit orther pages through friendly url.For
example when i visit /pub/Login page tomcat error is
:

HTTP Status 404 - /pub/Login.cnbrn

type Status report

message /pub/Login.cnbrn

description The requested resource (/pub/Login.cnbrn) is not available.
Apache Tomcat/5.5.20
============================

here is my context setting in server.xml is:

      <Host name="10.0.0.201" appBase="E:\project\cnbrn"
       unpackWARs="true" autoDeploy="true"
       xmlValidation="false" xmlNamespaceAware="false">

       <Context path="" docBase="." debug="0"/>
       </Host>
=============================

here is my web.xml setting of servlet-mapping:

        <servlet-mapping>
                <servlet-name>cnbrn</servlet-name>
                <url-pattern>/app</url-pattern>
        </servlet-mapping>
        <servlet-mapping>
                <servlet-name>cnbrn</servlet-name>
                <url-pattern>*.cnbrn</url-pattern>
        </servlet-mapping>
=============================

How to resolve this problem???Any advice is welcome and thank you very
much!!!


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to