Description Chris Frost 2011-06-10 07:15:15 EDT

When not enabled all my WABs deploy just fine, including ones that use the JSTL standard tag libs as they are actually available via the jetty-osgi-boot bundles jsp fragment. When I want to use some other tag-libs I enable Require-TldBundle support in the jetty.xml file and now all my apps are failing to respond to requests. Just a 404 is returned but when checking '/' I'm told they are actually deployed. 

Related to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=306971

This is using Jetty embedded in Virgo. I have been in the debugger and the code in 'org.eclipse.jetty.osgi.boot.jsp.TagLibOSGiConfiguration' is working fine, when the WAB is deployed it scans the META-INF folder in the bundle I specify and finds the .tld files. These are turned in to resources and returned. The deployment then continues on and completes but obviously something is going wrong but I don't know what.

Steps to reproduce:
1. Unzip the attached copy of the Virgo Jetty Server.
3. Startup the server by going to the bin dir and running startup.sh
3. Once the console reports that the test app has been deployed navigate to 'http://localhost:8080/taglibs'. Error reported.
4. Navigate to 'http://localhost:8080/' to the list of deployed contexts to confirm that something is deployed to '/taglibs'

If you want to see the other apps that come with Virgo working remove the Jetty config in the jetty/etc/jetty.xml file for the 'Require-TldBundle' support. The test app will still not be working as it uses some spring tlds.

The included test app is much simpler for the purpose of debugging than the admin app (id-admin/pass-springsource). Finally, the splash screen app which doesn't use tlds also fails to respond to http requests when 'Require-TldBundle' support is enabled.

Thanks, Chris.