Post a link to the JIRA if you create one. I think it's a good idea to
allow the container to handle requests not handled by T5, but should be
configurable and probably NOT the default. Perhaps web.xml would be the
appropriate place to toggle this behavior.
Ritesh.S wrote:
Hello Davor,
Thank
Hello Davor,
Thanks for your help. I will try to implement the custom filter you
suggested.
Also I will post a JIRA if necessary.
Thanks once again...
From,
Ritesh S.
Davor Hrg wrote:
>
> this is just a workaround,
>
> you should post a JIRA about this problem,
> there's been some talk a
this is just a workaround,
you should post a JIRA about this problem,
there's been some talk about tapestry letting container deal with paths
that tapestry can not resolve ... so this may be fixed in current trunk...
here's something that might work, and
save you headaches before an official sol
Hello Davor,
Thanks for your reply. I am giving stack trace below and problematic url.
Following is the stack trace I get when I try to upload a file through the
servlet
which produces the .htm file and shows in url.
This occures when use /*
An unexpected application exception has occurred.
could you post stack trace,
and problematic url ?
Davor Hrg
On Dec 4, 2007 11:18 AM, Ritesh.S <[EMAIL PROTECTED]> wrote:
>
> Hello everybody,
>
> I am new to tapestry and I am using Tapestry core 5.0.5.
> I integrated Tapestry 5 with spring and hibernate.
>
> I configured my application's web.xm
Hello everybody,
I am new to tapestry and I am using Tapestry core 5.0.5.
I integrated Tapestry 5 with spring and hibernate.
I configured my application's web.xml as below -
<-spring-app configuration is here->
tapestry.app-package
com.myproject
