Pierre van Rooden wrote: > The scanpage class is replaced in the core by > org.mmbase.util.PageContext. This small container class acts as a > wrapper for HttpServletRequest and HttpServletResponse. > The scanpage class will extend PageContext and be passed by SCAN, so > that old scan classes can still its the functionality.
I suggest we rename it to something else. This will cause some inconvenience. I added it as wish #6601: Imagine you have a JSP with the following: <[EMAIL PROTECTED] import="org.mmbase.util.*" %> This leads to: Generated servlet error: [javac] Since compiler setting isn't classic or modern,ignoring fork setting. [javac] Compiling 1 source file [javac] Since compiler setting isn't classic or modern,ignoring fork setting. [javac] /home/mmbase/tomcat/work/Standalone/localhost/mm/org/apache/jsp/resourceedit_jsp.java:87:5:87:15: Semantic Error: Type "PageContext" is imported on demand from package "javax.servlet.jsp" and package "org.mmbase.util". [javac] /home/mmbase/tomcat/work/Standalone/localhost/mm/org/apache/jsp/resourceedit_jsp.java:94:5:94:15: Semantic Error: Type "PageContext" is imported on demand from package "javax.servlet.jsp" and package "org.mmbase.util". [javac] /home/mmbase/tomcat/work/Standalone/localhost/mm/org/apache/jsp/resourceedit_jsp.java:678:96:678:106: Semantic Error: Type "PageContext" is imported on demand from package "javax.servlet.jsp" and package "org.mmbase.util". etc etc.. I think for an MMBase related JSP it is not very strange to import org.mmbase.util.*. I did not even import javax.servlet.jsp.*, I suppose this was done by the jsp-to-java compiler of tomcat. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
