Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (hercules.apache.org: domain of flamefew@gmail.com
 designates 209.85.221.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=hQEJuui6zyNCwqN46kzwba5dNjnDHWquoSOFM7Gtu9HY2JIcrIIb4ilh7rjQ33FhZU
         txFxCfcDvMgIUjOpcVpUIYSkpuCBrqeqmAWURLaz007MeJtKv0l3UQ8lZxMKgwWB9sDc
         6bxL8bj8NpEUAY723SWB1SCZjRdybzSolW8bY=
MIME-Version: 1.0
In-Reply-To: <4ACF1EE3.5090407@apache.org>
References: <4ACF1EE3.5090407@apache.org>
Date: Fri, 9 Oct 2009 16:43:15 -0700
Message-ID: <31cc37360910091643q3d78cf1at6fb5e5511afe4225@mail.gmail.com>
Subject: Re: Question ad alternative of BSF taglib in Tomcat ? [Fwd: In the
	move of some taglibs to Tomcat, the BSF taglib got retired]
From: Henri Yandell <flamefew@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Cc: Bean Scripting Framework developers <bsf-dev@jakarta.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

(dropping tomcat-users@)

The BSF Taglib was deprecated in July 2007, one of the first to be
recognized as unsupported. And as you say below, retired in the
Taglibs move to Tomcat.

If BSF users still have a strong need for it for legacy reasons, I'd
suggest it go in Jakarta BSF. There's been no one in the Jakarta
Taglibs (and now Tomcat I'll assume) project with an interest for many
years now (the last code change being in 2002). If there's strong
interest in JSP support of the JSR-223, that would be tempting either
for Extended Taglib if simple enough an API or its own BSF/JSR223
Taglib that (assuming people wanted to actually code it) could be in
Apache Taglibs at Tomcat.

An opinion anyway :)

Hen

On Fri, Oct 9, 2009 at 4:30 AM, Rony G. Flatscher (Apache)
<rony@apache.org> wrote:
> Hi there,
>
> not sure whether this is a user or dev question, hence sending it to
> both, please forgive, if wrong.
>
> Learning about the finalization of moving taglib from jakarta to tomcat,
> one could also learn that the BSF taglib got retired in the process.
> AFAIK the BSF taglib has been allowing one to add code in all of the BSF
> supported scripting languages to JSPs. Not knowing, wheter there are
> alternatives available in the current Tomcat (did a coarse research on
> that issue, but did not find any info on this) I created the enclosed
> e-mail to the BSF user and dev list to make sure, that users of the BSF
> taglib learn about where it has moved to, in case it is still needed.
>
> In case the BSF taglib is needed for adding scripts in scripting
> languages to JSPs, I would kindly suggest to not retire it, but to keep
> it available for interested parties in the Tomcat realm. In case there
> are alternatives available in Tomcat to the BSF taglib, please be so
> kind and point them out (just short pointers would suffice!).
>
> TIA,
>
> ---rony
>
> P.S.: If the BSF taglib is still needed, then one more (dev) point to
> discuss/raise would be to create in a addition a new JSR-223/BSF3 taglib
> for the newly released BSF 3.0, which implements the JSR-223
> (javax.script) specs. Unlike JSR-223, which is only available starting
> with Java 6, BSF 3 supplies the same functionality for Java 1.4
> installations or higher, making it a very attractive technology for Java
> 1.4 and 1.5 installations, as they gain the standard scripting APIs with
> it. There would be more to this, but should only be discussed, if a need
> for this exists.
>
>
> -------- Original Message --------
> Subject: =A0 =A0 =A0 =A0In the move of some taglibs to Tomcat, the BSF ta=
glib got retired
> Date: =A0 Fri, 09 Oct 2009 12:18:31 +0200
> From: =A0 Rony G. Flatscher <Rony.Flatscher@wu-wien.ac.at>
> Reply-To: =A0 =A0 =A0 Bean Scripting Framework developers <bsf-dev@jakart=
a.apache.org>
> To: =A0 =A0 Bean Scripting Framework developers <bsf-dev@jakarta.apache.o=
rg>,
> Bean Scripting Framework users <bsf-user@jakarta.apache.org>
>
>
>
> Hi there,
>
> just learned from the announcement that in the process of moving taglibs
> from Jakarta to Tomcat a lot of taglibs got retired, among them the BSF
> taglib.
>
> Not sure at the moment how Tomcat will allow for creating JSPs that
> embed code in scripting languages, which was one of the original
> applications of BSF, when it was originally developed at IBM (as a
> matter of fact, IBM's WebSphere distributed BSF in order to enable Java
> Server Page authors to embed scripts in any of its supported scripting
> languages, very much like MS allows for in their ASPs).
>
> So for those who have a need for the BSF taglib, here the relevant links:
>
> Information about BSF taglib and examples on how to use it:
>
> =A0 =A0<http://jakarta.apache.org/taglibs/doc/bsf-doc/>
>
> Download BSF taglib from:
>
> =A0 =A0<http://svn.apache.org/repos/asf/jakarta/taglibs/deprecated/bsf/tr=
unk/>
>
> Retired taglibs as of 2009-10:
>
> =A0 =A0<http://jakarta.apache.org/site/retired-taglibs.html>
>
> ---rony
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org