Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
I posted in Tomcat forum and got this response - have not tested - posting
here as-is, use at your own risk:
> If a file named index.jsp is declared as a welcome and it is not there in
> the system,
> tomcat does not allow failover to framework like Tapestry.
It sounds like behaviour that can be controlled by "resourceOnlyServlets"
option in ,
See http://tomcat.apache.org/tomcat-7.0-doc/config/context.html
The current behaviour is caused by compatibility concerns with earlier
versions of Tomcat. Read the doc for more details.
> However, if a file named Bienvenue.jsp is declared as welcome file, the
> failover is allowed.
Unlikely. You have to provide specific example to confirm that. The above
mentioned option could explain that as well.
> However
> is ignored and server picks up default values in
> ${Tomcat.home}/conf/web.xml
conf/web.xml is not just default. It is merged with app's web.xml using the
rules for merging web fragments, as specified in the Servlet 3.0 Rev.a
specification. If current behaviour contradicts with
specification, please cite what point in merging algorithm is not followed.
Best regards,
Konstantin Kolinko
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5641083.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Agree. Welcome file list is probably the cleanest (standards-based) fix. This seems to tell Tomcat "there are no welcome files" ... In fact, seems like you can set welcome file to any arbitrary component and it will still pick up Tapestry Index. For instance, index Or, about Note that there is an about component in newapp - still picks up Index (?!) - seems like anything here is ignored. Or, Burger King in Moscow All of of the above are equivalent. However a physical file name with extension, Bienvenue.jsp will work whether or not there is a Bienvenue.jsp (i.e. go to Bienvenue.jsp if present, failover to Index when not). The ONLY filename that generates the error (does NOT failover to Index when no in system) index.jsp The htm and html extensions to index are OK...meaning failover to Index if not present just like the "french" verison. I think we have beaten this to death, thanks guys. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5639153.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
welcome-file-list element is a standard part of web.xml. index.jsp is the default value for it at the container level of Tomcat, so setting the value to "index" in a Tapestry5 application is the correct option. Looks like we are missing the configuration from the archetype, I'll fix it for the next version. Kalle On Fri, Apr 13, 2012 at 5:27 AM, Lance Java wrote: > Have you tried: > > > Or with jstl > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Have you tried: Or with jstl
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
How about getting rid of index.jsp and adding "index" to your web.xml in the welcome file list. I'm assuming tomcat will try your config before the default
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Nope forward does not work, tried that first (see previous post). -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5638114.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Redirect will cause an extra request and will change the URL in the browser. Try forward instead
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
And now empty welcome file list in application does NOT work. Make sense, since the server will just default upward from application to container level default list. I win ;-) -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5638095.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Placing index.jsp with the following in it solves the problem:
<%
response.sendRedirect("Index");
%>
No need to jury rig the configuration.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5638076.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Perhaps you can override the tomcat defaults by adding an empty to your web.xml Then no tapestry config required?
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
YES, that worked. Sort of. Root URL is not found, but if pulled up as Index, no mo [ERROR]. Specifically, http://localhost:8080/newapp/ leads to HTTP 404 error - page not found However, http://localhost:8080/newapp/Index works (?!) Sorry to be pickyHere is the quote from http://tapestry.apache.org/configuration.html#Configuration-Changestoweb.xml http://tapestry.apache.org/configuration.html#Configuration-Changestoweb.xml User Guide wrote > > Tapestry Requests vs. Container Requests > > The Tapestry filter matches all the requests that apply to Tapestry, and > passes the rest off to the servlet container. In situations where there > would be a naming conflict, */actual files inside the web application take > precedence over Tapestry pages./* (*) > > *Tapestry recognizes the root URL, where the servlet path is simply "/", > and renders the application page "Index", if it exists.* (which is the > case with newapp...it has an Index component, but that is NOT what T5 is > doing) (**) > (*)meaning an index.jsp inside web app would intercept the request meant for the Index component? Guess what, it does...! ) (**) This contradicts (*) - I think we just discovered that this may not be working as advertised in (and probably not just in) Tomcat 7...unless configured to ignore welcome file list as advised. Basically, the root URL is not pulling up Index (first/before other resources)...and Tapestry is AMBIGUOUS about the precedence - at least in the manual. One would think the simplest fix would be to put an index.jsp in the newapp folder with a jsp forward to Index, as follows: But, sure enough, that does NOT work...would be too easy ;-). Nevertheless, good work. This has been fun. Yes, the JIRA 1904 may be closed...with the proper explanation of the workaround (as you guys see fit). -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5638049.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Please try the following:
public static void contributeIgnoredPathsFilter(Configuration
configuration) {
configuration.add("/index\\.(?:html|htm|jsp)");
}
If it works, we'll close the JIRA and put some tomcat specific
documentation somewhere
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Yes, this may indeed be the temporary workaround. Since it is limited to the application, and not the entire server/container, this is the preferred fix. Much Thanks for fleshing this out. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637951.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
YES. That solves the problem indeed. BUT, no thanks ;-). This fix will almost certainly break many other applications on the production server and I am pretty sure the community shares my sentiment. Unfortunately, T5 will need to address this. JIRA created: https://issues.apache.org/jira/browse/TAP5-1904 -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637941.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Another option might be to tell tapestry to ignore the welcome file list
public static void contributeIgnoredPathsFilter(Configuration
configuration) {
configuration.add("(index\\.html)|(index\\.htm)|(index\\.jsp)");
}
http://tapestry.apache.org/configuration.html#Configuration-ConfiguringIgnoredPaths
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
It looks like you will need to remove all entries from the in $TOMCAT_HOME/conf/web.xml See "How do I override the default home page loaded by Tomcat?" here http://wiki.apache.org/tomcat/HowTo
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Here is the complete access log from Tomcat 7 (I pulled up about then index ... captured in 2nd last tine...and then about again)...not sure (yet) what the server config should be ... and if that is even advisable since in production there are other apps to contend with ... 127.0.0.1 - - [13/Apr/2012:00:05:11 -1000] "GET / HTTP/1.1" 200 7388 127.0.0.1 - - [13/Apr/2012:00:05:28 -1000] "GET /manager/html HTTP/1.1" 401 2542 127.0.0.1 - admin [13/Apr/2012:00:05:35 -1000] "GET /manager/html HTTP/1.1" 200 13364 127.0.0.1 - admin [13/Apr/2012:00:05:41 -1000] "POST /manager/html/undeploy?path=/newapp&org.apache.catalina.filters.CSRF_NONCE=5E267AF1A2CF07C36BE4802B8A7190CF HTTP/1.1" 200 11831 127.0.0.1 - admin [13/Apr/2012:00:05:50 -1000] "POST /manager/html/upload?org.apache.catalina.filters.CSRF_NONCE=89C1AF8973D749095B555ADE319A1CE8 HTTP/1.1" 200 13364 127.0.0.1 - - [13/Apr/2012:00:06:23 -1000] "GET /newapp/about HTTP/1.1" 200 1021 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/tapestry/tapestry-console.css HTTP/1.1" 200 267 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/tapestry/t5-alerts.css HTTP/1.1" 200 334 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/tapestry/tree.css HTTP/1.1" 200 422 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/ctx/layout/layout.css HTTP/1.1" 200 1224 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/stack/en/core.js HTTP/1.1" 200 82756 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/ctx/layout/images/img01.jpg HTTP/1.1" 200 752 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/ctx/layout/images/img10.gif HTTP/1.1" 200 1344 127.0.0.1 - - [13/Apr/2012:00:06:24 -1000] "GET /newapp/assets/1.0-SNAPSHOT/ctx/layout/images/img08.gif HTTP/1.1" 200 297 127.0.0.1 - - [13/Apr/2012:00:11:49 -1000] "GET /newapp/about HTTP/1.1" 200 1021 127.0.0.1 - - [13/Apr/2012:00:11:57 -1000] "GET /newapp/ HTTP/1.1" 500 288 127.0.0.1 - - [13/Apr/2012:00:12:16 -1000] "GET /newapp/about HTTP/1.1" 200 1021 -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637875.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Thanks. YES, commenting out yui-compressor dependency in pom.xml eliminates the first error above. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637859.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Inspect the HTTP logs, is Tomcat trying to redirect from root to some other page (index.jsp or something)? There might be some config in tomcat that you can tweak / remove.
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Indeed. But it is the reference implementation of the servlet standard. In other words, the "fault" is not with Tomcat...even if it probably is. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637826.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
I think you've now hit this https://issues.apache.org/jira/browse/TAP5-1729
Try commenting out the following in your pom.xml
org.apache.tapestry
tapestry-yuicompressor
${tapestry-release-version}
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
The tapestry source code does not have a single reference to "jsp". I think that tomcat might be trying to "help" somehow.
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
YES, about link works, with errors in logs, both in Tomcat 7 and 5, (and the index page continues to barf in Tomcat 7). Here is the corresponding stacktrace: First [ERROR] is from About page (renders fine though). Second, now familiar, [ERROR] is generated by clicking on Index link from About page Application 'app' (version 1.0-SNAPSHOT) startup time: 234 ms to build IoC Regis try, 780 ms overall. __ __ /_ __/__ ___ ___ / /___ __ / __/ / / / _ `/ _ \/ -_|_-http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637797.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
The index page of the T5 tutorial. Not sure of component. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637774.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
I wonder if this has something to do with how tomcat 7 is trying to serve the root. Are you able to hit http://localhost:8080/newapp/about
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
So, I think that eliminates the problem that howard was mentioning on his blog. Can you paste the page / component that is trying to run? I'm trying to think of where a "jsp" component would be references inside the tapestry archetype.
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Thanks for suggestion. No luck, though. Same error in Tomcat 7 with exploded war approach BUT...war file works in Tomcat 5.5.31 ...JDK 1.6.0_03... Go figure... -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637743.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
I know it's not ideal but you could deploy an exploded war.
Re: Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
Found this little nugget: http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html http://tapestryjava.blogspot.com/2007/02/fighting-with-tomcat.html Unfortunately, our production is tomcat. Have to comply. Jetty will not do. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637652.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Tomcat 7 deployment TapestryModule.RequestExceptionHandler Processing of request failed with uncaught exception: Component Index does not contain embedded component 'jsp'.
To Reproduce (using Tomcat 7.0.4 with jdk1.6.0_22 64-bit), follow "Getting Started" at http://tapestry.apache.org/getting-started.html Specifically, 1. mvn archetype:generate -DarchetypeCatalog=http://tapestry.apache.org 2. Create newapp, change to newapp directory (verify works in jetty, stop it by CTRL+C) 3. mvn package 4. Startup tomcat, use manager to deploy the war file generated under newapp/target 5. No errors 6. Click on http://localhost:8080/newapp (ERROR, see below) Expecting to see something like: http://tapestry.apache.org/getting-started.data/getting-started.png BUT, Chrome Browser shows (View Source): Application Exception An unexpected application exception has occurred. Component Index does not contain embedded component 'jsp'. Tomcat Console stacktrace (after deployment) is: Application 'app' (version 1.0-SNAPSHOT) startup time: 208 ms to build IoC Regis try, 674 ms overall. __ __ /_ __/__ ___ ___ / /___ __ / __/ / / / _ `/ _ \/ -_|_-http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5637647.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
