[tomcat] branch master updated: Remove EL limitations

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[tomcat] branch master updated: Remove EL limitations

Rémy Maucherat
This is an automated email from the ASF dual-hosted git repository.

remm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/master by this push:
     new 6af4862  Remove EL limitations
6af4862 is described below

commit 6af486242795daf5f1c85baf8c291d73f06d96b0
Author: remm <[hidden email]>
AuthorDate: Wed Oct 9 18:24:03 2019 +0200

    Remove EL limitations
   
    Since a specific bean resolver is added, no manual configuration is
    supposed to be needed.
---
 webapps/docs/graal.xml | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/webapps/docs/graal.xml b/webapps/docs/graal.xml
index 5178b56..c751344 100644
--- a/webapps/docs/graal.xml
+++ b/webapps/docs/graal.xml
@@ -159,14 +159,7 @@ ant -Dwebapp.name=somewebapp -f graal-webapp.ant.xml</source>
 
   <p>
     Servlets, JSPs, EL, websockets, the Tomcat container, tomcat-native, HTTP/2
-    are all supported out of the box in a native image. However, EL uses
-    BeanInfo reflection which needs manual descriptor configuration.
-    To give an example, the EL expression
-    <source>${pageContext.servletContext.serverInfo}</source> needs full
-    reflection information on the concrete Jasper page context class, as well
-    as the Catalina Servlet context implementation. Graal error messages
-    during runtime generally indicate which classes are missing reflection
-    as the BeanInfo reported for these will be empty.
+    are all supported out of the box in a native image.
   </p>
 
   <p>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]