Once the JSPTL is finalized, I'm sure that we will revisit the Struts
tag extensions, and probably move as many as possible over to Jakarta
Taglibs, keeping only those that are too strongly tied to Struts to be
useful in another environment (e.g. the html lib).

Right now, the general feeling is that the tag extensions we have aren't
broken, and there's no point in making any drastic changes until JSPTL
is finalized. 

In general, I think the Struts tags play nice with the expression
language, and can be used side by side. See 

http://www.mail-archive.com/struts-user@jakarta.apache.org/msg12915.html

for an example.

Of course, if someone wanted to work on some tags in the JSPTL vien that
accessed Struts application resources, like the mappings and message
resources, I'm sure everyone would love to see the result, both here and
in Jakarta Taglibs. 

-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel +1 716 737-3463
-- http://www.husted.com/about/struts/


stuart robertson wrote:
> 
> Two questions.
> 
> Has anybody made a JSP 1.1 version of the jsptl?  The
> documentation mentions that this may be considered (I
> think), but I couldn't find anything in the newsgroups
> regarding this.
> 
> Has anybody played with modifying Struts tags to use
> the expression language?
> 
> If not, I may take a swing at both of these.
> 
> The company I'm working for is looking into to start
> using custom tags rather than scriptlets.  I would
> like, if possible, for this library(ies) to be based
> on the current snapshot of the Standard Tag Library,
> using the new Expression Language.  Yes, I realize
> this isn't close to being finalized yet, but it seems
> to me that even in its current state it works and
> provides much
> more flexibility than the typical taglib designs.  I
> suspect this will be done anyway by the maintainers of
> Struts.  Any idea on the timeframe?
> 
> Would anybody else be interested in working on this,
> if nobody is currently?
> 
> Regards,
> 
> Stuart Robertson

Reply via email to