[jbossweb-commits] JBossWeb SVN: r877 - trunk.

Author: remy.maucherat(a)jboss.com Date: 2008-12-10 09:21:21 -0500 (Wed, 10 Dec 2008) New Revision: 877 Modified: trunk/PATCHES.txt trunk/ROADMAP.txt Log: - Update patches and roadmap. Modified: trunk/PATCHES.txt =================================================================== --- trunk/PATCHES.txt 2008-12-08 12:10:50 UTC (rev 876) +++ trunk/PATCHES.txt 2008-12-10 14:21:21 UTC (rev 877) @@ -30,3 +30,7 @@ various All changesets introducing generics, which have small value (new code or refactorings should use generics, however) + +724886 +Executor modifications, very specialized work that breaks the Executor design (a single task can be submitted +to the real executor more than once) to supposedly work better with the NIO connector Modified: trunk/ROADMAP.txt =================================================================== --- trunk/ROADMAP.txt 2008-12-08 12:10:50 UTC (rev 876) +++ trunk/ROADMAP.txt 2008-12-10 14:21:21 UTC (rev 877) @@ -1,20 +1,22 @@ Roadmap for JBoss Web 3.0 +Main development: +- Setup standalone TCK environment for testing compliance with the new features - Implement Servlet 3.0 async for APR HTTP connector - Update digester XML parsing rules for web.xml updates - Implement new APIs for programmatic deployment descriptor access -- Setup standalone TCK environment for testing compliance with the new features - Implement annotation scanning for JBoss Web standalone (likely disabled by default using conf/web.xml) - Implement any other Servlet 3.0 changes (web.xml fragments, security, etc) -- Implement JSP 2.2 changes - Implement Servlet 3.0 async for APR AJP connector - Implement Servlet 3.0 async for java.io HTTP connector - Implement Servlet 3.0 async for java.io AJP connector +- Implement JSP 2.2 changes +- Implement EL 1.1 changes - Coordinate with AS 6 to implement new web.xml parsing (out of tree) - Coordinate with AS 6 for annotation updates (out of tree) + +Other: - Diagnostic and monitoring features - -Other possible features: - .net support like the php support (looks ok, but PHP is hard to use, how would this be different ?) - fastcgi servlet (sounds useless) - Java proxy (probably too many components needed to compete with mod_cluster, but a very basic HTTP proxy could be useful