Ernst Bunders <[EMAIL PROTECTED]> wrote:
>
> but than, if you'd update your website to jsp2 you would have to change all
> the templates. I dont know...
Yes, that will be so in any case, because currently you can make templates
which would not work in jsp2. The smallest change you have to do is adding
isELIgnored="true" to every page.
But if you don't want to,
-If we disable rtexpr, you have to remove those <%= %> things.
-If we don't disable rtexp, but let $(..) work too, you have to change ${} in $().
So, it is impossible to make all current pages work in JSP2, simply because
there is a conflict (which is, in essence, that they came up with the same
idea as we).
'Old' web-apps remain functional in any case, because the 'old-style'
web.xml triggers jsp1-compatiblity mode. I'm running tomcat 5 for months but
did not even notice this problem because of that.
The only question remaining is what we should do. My suggestion was to add a
little extra syntax to mmbase taglib, so that it is at least possible to
make new jsp's which are jsp1 and jsp2 at the same time. 'Generic editors'
and such can use this new syntax, and they will then work in JSP1 and JSP2
withouth troubles. According to Rob that will also be achieved by disabling
rtexp, but I see two disadvantages:
- The tld needs a different version when using jsp1 or jsp2. Or we should
drop <%= %> altogether, meaning that you can't even upgrade your jsp1 sites.
I would prefer to have one mmbase-taglib.jar and one tld which can be used
always.
- You cannot use EL in mmbase-attributes, even in the few cases where it
would be interesting.
Michiel
--
Michiel Meeuwissen
Mediapark C101 Hilversum
+31 (0)35 6772979
nl_NL eo_XX en_US
mihxil'
[] ()
