Since from section 3.3 of the JSP spec, jsp-property-groups are translation time mappings, the only "clean" solution I can see would be to implement something like the TC 3.3 JspInterceptor (obviously, changed to a JspValve :) that would handle the pre-compilation checks with the required jsp-property-group applied. This would still be bending the spec a bit, but not as much as this patch does.
Jan's solution seems unfortunately the least worst (my favorite by far is to not fix anything): the problem is that with TC > 4 (I know, this sucks), the valve will not be invoked for request dispatching :(
So, patatras, it becomes much slower and much more complex (the valve has access to the lower level stuff, while the RD does not). I suppose a filter-like algorithm wouldn't be too bad (works on Strings without GC), but it's another mapping operation and additional complexity (I believe the mapping rules have subtle differences :) ).
:( :( :(
I suppose it's when implementing specs completely that you uncover issues, and this is quite bad :(
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
