Kin-Man Chung wrote:
Date: Fri, 21 Feb 2003 19:16:46 +0100
From: Remy Maucherat <[EMAIL PROTECTED]>
Subject: Re: [5.0.1] Tagging today
To: Tomcat Developers List <[EMAIL PROTECTED]>
Costin Manolache wrote:
Kin-Man Chung wrote:
I also don't believe jsp-examples has been successful compiled with JSPC
before. I know haven't tried that with JSP2.0 examples. With automatic
compiling of the tag files, I won't be surprise if there are problems. :)
It doesn't matter what it's for - if it is valid JSP it should compile
with jspc the same as with jspservlet :-). If it's not valid - it should be
removed...
I tried to look into the issue, but it's quite complex :-(
I have just committed a fix for using JSPC to compile JSP pages that uses
tag files. The complication comes from the need to compile tag files
into class objects before a JSP page that references them can be compiled.
I don't know a better strategy for precompiling an application would be to
first compile all the tag files first, then compile the JSP pages after
that. The added complication is that a tag file may use other tag files, or
even be circularly dependent.
Yes, I understood the purpose of the code (but not really the code itself).
I don't like that new spec feature, overall. Same for the ability to put
the TLD in random places.
It's supposed to help page authors that are not programmers. But if a
seasoned programmer find tag files hard to use, it's not a good sign.
No, it's easy to use. The problem is that I don't quite see the point,
and on the implementation side, it gets nasty ;-)
It seems the new spec revisions mean "more complex + more bloated" :-(
This is quite disappointing ...
Isn't that always true? :-) You need to add new features but cannot
remove old ones.
Yes, it's always true.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
