Thanks Shing.
IN case of jetty, even though that warning shows up, the app is running
fine. Moreover tapestry initialization is able to find out the page
components.
As Geoff pointed out, i should probably find out the difference between my
app setup and jumpstart.
- Rakesh
--
View this mes
Sorry for the delay in responding.
Thanks for the pointer Geoff.
I was able to get the jumpstart up and running. No issues with pages too.
Need to find out the difference between my app setup and jumpstart. WIll
post the findings.
Thanks,
Rakesh
--
View this message in context:
http://tape
[WARN] TapestryFilter Application Module class
com.rakesh.demotapestry.web.services.TapestryModule not found
The above appears in both the Jetty and Jboss log. I would expect your app will
not work in Jetty nor in Jboss.
It looks as though the tapestry filter name in web.xml does not match
Rakesh,
I don't have time to debug your problem but I can offer you a working project
and packaging/deployment instructions to compare to: JumpStart is developed
with Jetty and the demo is deployed on JBoss 7.1.1. Here is the demo:
http://jumpstart.doublenegative.com.au/jumpstart/
The
