greetings, i just signed up to this list; i'm faily new to tapestry, especially 5. i've searched the web extensively trying to find some reference to this issue, with so little success that i think i'm fundamentally misunderstanding something at this point. any assitance or pointers would be greatly appreciated:
we have a tapestry 5 webapp running with tomcat (5 and 6, on different environments) and apache2. apache passes along the requests to particular webapp instances via virtual hosts using mod_jk workers to handle the service requests. all pretty standard. however, we can't get the requests for the tml files in a subdirectory (not in WEB-INF) to be handled correctly. i'm fairly convinced that the apache configs are the issue here because on the localhost builds that run from the tomcat root without apache, we don't see this issue, but i can't find a way to resolve it. the app has an 'admin' user interface that imo should be a separate webapp altogether, but that's a different story; in this story, there is an /admin subdir at the webapp root (so, not a subdir of WEB-INF). hitting that admin dir directly should produce the index.tml in that subdir, which is a login form for this subset of users. however, webapp.com/admin produces a directory listing, which clearly is not what we want. webapp.com/Admin, however, does indeed bring us the Index.tml in the admin dir, with a loginForm therein. which brings us to the second issue: submitting the form causes apache/tomcat to throw a 404 because "index.loginform" can't be found. so it seems clearly that there's some kind of proxy/precedence issue happening with apache trying to serve the "admin" directory, but tapestry handling the request for the "Admin" directory correctly. i know tapestry does pretty urls and is largely case-insensitive in that manner, and i'm guessing the above behavior may have something to do with that? we've tried moving components around, creating additional app descriptions and filters in the web.xml, etc, with no luck so far. this seems absurdly trivial, but i'm not sure if we're just trying to do something that is outside of the intended tapestry design or what. we moved all of the files out of the /admin directory, refactoring code accordingly, and it all works fine, but that's not much of a solution for the kind or the scale of development we're doing going forward here. so, again, any help would be much appreciate indeed. cheers, -michael huff tapestry newbie --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
