I disagree with </ELSE>, there are numerous tags like <DISPLAY> (as noted)
that are "standalone"), the proper XML notation for them would be:
<ELSE/> and <DISPLAY ... /> and decent JSP should handle tags with that
notation. ELSEIF was a good suggestion, SWITCH etc is "taking it too far"
IMHO. The reason I suggested <ELSE> in the first place is that I've noticed
that you want it in ~90% of the cases you use INCLUDEIF/EXCLUDEIF :)
As for the "we want Java code in our HTML" people - I think it should be
supported, but absolutely not the "main direction". Orion will have an
optional mode for users to be able to produce JSP pages (secured) but
without the explicit scripting capabilities. I.e. only using preinstalled
beans in "non-trusted" environments. Tying "general" JSP strictly to Java is
a bad design decision too IMHO.
On the <include> issue, seems like we've done a bad decision when including
the rendered content (of whichever type it may be) into the output and not
the source (the JSP spec is a moot point on this issue - how does the
reference implementation act?). What are your opinions? People from JRun
replied with propriety JRun syntax (<%@ vinclude ... %>) but didn't seem to
make any effort to push it as something to include in the JSP spec which I
think is sad. Having <!--# include ... --> include generated content (from
whatever parser is tied to that resource) is also a valuable feature, but
then again <!--# exec cgi ... --> handles that part - just a bit awkward
syntax. Ideas/suggestions?
/Magnus Stenman
Orion WebServer - http://orion.evermind.net
-----Original Message-----
From: A mailing list about Java Server Pages specification and
reference [mailto:[EMAIL PROTECTED]] On Behalf Of Christopher Cobb
Sent: den 28 april 1999 15:05
To: [EMAIL PROTECTED]
Subject: Re: ELSE tag
<< File: ccobb.vcf >>
Rod McChesney wrote:
> To retain some vestige of HTML or XML syntax, I believe this would
> have to look like
>
> <IF>
> <ELSE>
> </ELSE>
> </IF>
>
> and so on. Otherwise the tags don't nest meaningfully. This kind of
> thing is easy to hack into a parser but SGML/HTML/XML tools won't
> necessarily understand it. Unless I'm just missing something...
I agree that
<IF>
<ELSE>
</IF>
is very non-XLM-ish. On the other hand, neither is:
<DISPLAY>
with no </DISPLAY>. And neither is:
<USEBEAN>
<SETFROMREQUEST>
</USEBEAN>
That is, the <SETFROMREQUEST> has no close tag.
Given these asymetries, I think
<IF>
<ELSE>
<ELSEIF>
</IF>
is just fine. Are you listening, Sun?
cc
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
