Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <003d01bf6627$719fd0c0$8eac85ce@DRF26>
From: "Danno Ferrin" <shemnon@earthlink.net>
To: <tomcat-dev@jakarta.apache.org>
References: <8525686F.006DC9F2.00@d54mta04.raleigh.ibm.com>
Subject: Re: Jsp scripting elements revisited
Date: Sun, 23 Jan 2000 21:56:56 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


<rubys@us.ibm.com> wrote:


>
> I'll probably do that as an initial step, but my real interest is in
> usurping the meanings of things like <% %> while still providing a
standard
> syntax which can be safely emitted by tags.
>
> I'm envisioning non-Java scriptlets to be essentially templates/quoting
> mechanisms which contribute Java code to the servlet.  This code will do
> the necessary mapping between Java and the language in question.
>
> The hard issues to work through are dealing with things like nested tags,
> and collecting together the script fragments into a whole.
>

Usurping the meaning of a core element like that means you are changing the
spec.  The very need to describe an action as usurping is revolutionary to
the core.  Start a revolution and post the existing code so we can see if
the two can co-exists.  Tomcat is a refrence implementation, not a
production implementation.  If you want to do that go start a code fork, the
lincese allows it.  But it dosen't appear to me that you need to do what you
are trying to do to <% %>, if you could keep needed state information in
page attributes then you could jsut make a taglib:
  <beanscripting:expression language="NetRexx"> foo( 'bar')
</beanscripting:expression>
and use the suggestions in section 5.8.1.  Remember, the implementation of
jsp:expression was a bug to begin with, and a progammer can never depend on
bugs not getting fixed.

--Danno