I've managed to fix the cross-context c:import problem described here: http://sling.markmail.org/thread/zux7mejcuvegidoe
In short, the fix is to include an implementation of JSTL in the JSP bundle and slightly modify the import tag implementation to reset the JspFactory to the original default before doing a cross-context include. Overall patch is here: http://codereview.appspot.com/4442079. This is using the current trunk version of JSTL from Tomcat. It doesn't appear Tomcat has formerly released JSTL version 1.2. The specific changes I made are here: http://codereview.appspot.com/4442079/patch/1/29 (search for Sling Custom). At present, this *has* to be fixed in the JSP Scripting bundle because going back to the original JspFactory uses an internal class (JspRuntimeContext; see http://codereview.appspot.com/4442079/patch/1/20). Although adding the whole JSTL library to the JSP scripting bundle is a bit extreme, I think it is more sensible than exporting the JspRuntimeContext class. WDYT? Justin
