Right.  JSP was designed (sometimes with quite a bit of effort) to allow
different scripting languages.  So far the only scripting language that
has been standarized is "java", but SQLJ, and WebMacro (if desired - no
smiley here!) can be handled.  In particular, the design of the
implementation of custom tags had as a requirement to be usable
regardless of the scripting language used in the JSP page.

Another direction is to use custom tags to introduce the non-java
scripting language.  This seems doable with some constraints on the
language structures used in the custom tag, and an assumption that the
non-java scripting language is intrepreted.  I know of one person who is
(said he was) looking into this right now.  The one area that I think
needs improvement is the "quoting" properties of the custom tag.  One
nice thing of  <% %> is that you can use a plain old "<" instead of
&lt;.  Going the custom-tag route does not give you that but this
*could* be addressed in a future extension to the spec.  [[Of course,
the hard part of specs is deciding what to leave out]]

Hope this helps,

        - eduard/o


> Date:    Fri, 28 Jan 2000 14:12:24 -0500
> From:    "Bail . Jeff" <[EMAIL PROTECTED]>
> Subject: Re: access to ORACLE from JSP
>
> > SQLJ requires preprocessing, so you wouldn't be able to use
> > it in a JSP page
> > unless you tampered with the JSP implementation.
>
> With JSP 1.1 you can actually use SQL as your scripting language which is
> along the same lines as SQLJ. I just saw an example of this during an Oracle
> presentation at Sun Technology Days. I'll post a URL if I can find one.
>
>
> Jeff
>

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html

Reply via email to