/show_bug.cgi?id=22743
A JSTL EL Validator rule would make a lot of sense.
--- Additional Comments From [EMAIL PROTECTED] 2003-09-10 11:50 ---
JSTL EL expression manager is specific to a server-side application. Commons
Validator could use JEXL to accomplish this goal
/show_bug.cgi?id=22743
A JSTL EL Validator rule would make a lot of sense.
--- Additional Comments From [EMAIL PROTECTED] 2003-09-10 13:50 ---
AFAIK, this proposal applies to Struts and not Validator so using EL is no big
deal. Currently, Validator provides a framework and low-level
/show_bug.cgi?id=22743
A JSTL EL Validator rule would make a lot of sense.
--- Additional Comments From [EMAIL PROTECTED] 2003-09-08 00:15 ---
Being able to use scripting expressions within XML seems like an interesting
idea. Expecially if the idea were to support any BSF scripting language
appreciate it if motivated Tiles/JSTL users could test it as much as possible
once I've put it into the nightly build.
I'll also start looking at the nested-el library, just for completeness.
--
===
David M. Karr ; Java/J2EE/XML
I'm planning on committing the tiles-el library this weekend, but I won't
have any unit or integration tests for it by the time I commit it. I'll
proceed down that path once it's committed, but that process will be slow. I'd
appreciate it if motivated Tiles/JSTL users could test it as much
Thanks for the update. I'll see if I can work them a little for you.
Edgar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Perhaps this belongs on the user list, but I think it is relevant for
the discussion at hand. You all seem to regard all of the Struts taglibs
as one item, for which JSTL is an alternative. While this is certainly
true for the logic: and bean: tags, I have not seen a replacement for
the
html: form
You are right, JSTL doesn't completely remove the need for Struts specific
tags.
I think for the purposes of this discussion, the next generation would be
JSTL plus the struts-el taglib and when we talk about the Struts tags, we're
really talking about the traditional, non-el tags.
So keep using
conversation Steve Raeburn indicated he would be interested
in these tags. Steve also pointed out we are missing the Nested tags,
but since I've never used those before I leave that tedious task to
someone else ;)
Matt
Steve Raeburn wrote:
You are right, JSTL doesn't completely remove the need
Sgarlata == Sgarlata Matt [EMAIL PROTECTED] writes:
Sgarlata Speaking of EL, I noticed we don't have EL versions of the Tiles tags. I
would
Sgarlata be happy to provide the implementations, but I know it will be tedious
so I
Sgarlata only want to proceed if there's a reasonably
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: August 29, 2003 6:08 PM
Each of us can only offer support from our own experience. If a person
is not using the html taglib, then they might not know the html taglib
solution. But if they are using JSTL, they might
Craig R. McClanahan wrote:
I'm -1 on making Struts 1.2.x dependent on Servlet 2.3 / JSP 1.2.
Ditto. Contrary to popular brief, a great number of organizations have
*not* migrated to 2.3/1.2, including some of the largest companies in
the world.
-Ted.
My original point really was that if the standard for Struts continues to be
2.2/1.1 that we should be careful not to reply to the How do I do this with
html:??? questions with the stock answer of use JSTL.
If we're supporting Struts tags then I believe we should first answer the
question
Each of us can only offer support from our own experience. If a person
is not using the html taglib, then they might not know the html taglib
solution. But if they are using JSTL, they might know a JSTL solution.
There's no limit on the number of responses we can post to a question.
If someone
] wrote:
On Fri, 29 Aug 2003, David Graham wrote:
Date: Fri, 29 Aug 2003 10:26:54 -0700 (PDT)
From: David Graham [EMAIL PROTECTED]
Reply-To: Struts Developers List
[EMAIL PROTECTED],
[EMAIL PROTECTED]
To: Struts Developers List
[EMAIL PROTECTED]
Subject: RE: Support for non-JSTL
[mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2003 7:10 PM
To: Struts Developers List
Subject: RE: Support for non-JSTL tags (was RE: DO NOT REPLY
[Bug 21465] - Enhancement of the html:link tag)
I feel it's become a bit too easy to give the JSTL answer and
not deal with the issue
I would like to see those responses.
Edgar
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2003 8:08 PM
(Hey, maybe I should start answering the html taglib
questions with the
Velocity Tools solution!)
It's my feeling that Struts 1.x has to support 2.2/1.1, because that's
where a significant number of users still live.
But, it's also my feeling that the refactoring of the Request Processor
could open the door to being able to offer more than one front
controller for Struts 1.x.
The default
David Graham wrote:
IMO, Struts 2.x should attempt to get out of the taglib business
altogether. Until then, we should just let the tags be and maintain
Struts 1.x as Servlet 2.2 minimum requirement.
+1
And along the way, we can start distancing the core distribution from
the taglib
On Fri, 29 Aug 2003, Steve Raeburn wrote:
My original point really was that if the standard for Struts continues to be
2.2/1.1 that we should be careful not to reply to the How do I do this with
html:??? questions with the stock answer of use JSTL.
Point well taken -- I've been guilty
On Sat, 30 Aug 2003, Ted Husted wrote:
Date: Sat, 30 Aug 2003 09:35:38 -0400
From: Ted Husted [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465
Many Jakarta products have subproducts with their own CVS. Perhaps there
should be a Struts taglib CVS where all three packages could live.
-Ted.
+1
What about also doing this for the contrib components? Some of these are
really only concepts or proposals rather than production quality
Id like to see Struts play nice with JSTL i18n support.
I have a suggestion along these lines. (This is prelim. I am going to write
some tests and do some prototyping but before I do
Id like to hear if
there are any thoughts on this).
Currently when you call Action.setLocale you get
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 9:20 PM
To: Struts Developers List
Subject: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465] -
Enhancement of the html:link tag)
I'm not singling Vic out for this (honest) but...
The standard advice we are now giving
:
Id like to see Struts play nice with JSTL i18n support.
I have a suggestion along these lines. (This is prelim. I am going to
write
some tests and do some prototyping but before I do
Id like to hear if
there are any thoughts on this).
Currently when you call Action.setLocale you get
On Fri, 29 Aug 2003, David Graham wrote:
Date: Fri, 29 Aug 2003 10:26:54 -0700 (PDT)
From: David Graham [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED],
[EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: Support for non-JSTL tags (was RE
Okay. No problem. I will still work on this (I need it) maybe I'll just
come up with a Best Practice for using JSTL i18N support with Struts or
something along those lines.
It seems like any JSTL integration is going to wait until Struts 2.0. I
understand the reasoning behind this. It makes
/show_bug.cgi?id=22743
A JSTL EL Validator rule would make a lot of sense.
--- Additional Comments From [EMAIL PROTECTED] 2003-08-28 02:38 ---
Would this make more sense in JSP Tags?
.V
-
To unsubscribe, e-mail: [EMAIL
I'm not singling Vic out for this (honest) but...
The standard advice we are now giving everyone is use JSTL, which I
wholeheartedly agree with and have said myself. However, I think we need to
make sure that we still adequately support non-JSTL solutions and continue
to consider bug fixes
--- Steve Raeburn [EMAIL PROTECTED] wrote:
I'm not singling Vic out for this (honest) but...
The standard advice we are now giving everyone is use JSTL, which I
wholeheartedly agree with and have said myself. However, I think we need
to
make sure that we still adequately support non-JSTL
Steve Raeburn wrote:
I'm not singling Vic out for this (honest) but...
The standard advice we are now giving everyone is use JSTL, which I
wholeheartedly agree with and have said myself. However, I think we need to
make sure that we still adequately support non-JSTL solutions and continue
For what my non-contributor opinion's worth, I totally agree with David.
So far as I know, while JSTL is not _required_ by the standard for JSP
1.2, it does not _require_ 1.2 -- and can be used with 1.1 containers;
so saying use JSTL does not translate to upgrade to Servlet 2.3.
Shai
JSTL does indeed require JSP 1.2.
Quoting [EMAIL PROTECTED]:
For what my non-contributor opinion's worth, I totally agree with David.
So far as I know, while JSTL is not _required_ by the standard for JSP
1.2, it does not _require_ 1.2 -- and can be used with 1.1 containers;
so saying use
/show_bug.cgi?id=22743
A JSTL EL Validator rule would make a lot of sense.
--- Additional Comments From [EMAIL PROTECTED] 2003-08-28 21:41 ---
Vic,
Can you clarify your comment?
Perhaps, I did not include enough details.
Here is an example of using this rule to check to see
:20 PM
To: Struts Developers List
Subject: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465] -
Enhancement of the html:link tag)
I'm not singling Vic out for this (honest) but...
The standard advice we are now giving everyone is use JSTL, which I
wholeheartedly agree with and have said
Rick,
It certainly sounds interesting but I'd like to have a working example to
play with.
It would be nice if you could:
a. Create a small working example as a war and post in on a website for us
to take a look at.
b. Create an enhancement request in Bugzilla and add your proposed patches
The only reason I didn't go with JSTL is that I couldn't find a way to
represent the Foo[] syntax (meaning the same index into Foo that is
being used by the field being checked) in JSTL, and that's very useful
when you're doing master-detail records where you want the Last Name for
a row
Comments below (**)
-Original Message-
From: James Turner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 26, 2003 4:38 PM
To: 'Struts Developers List'; [EMAIL PROTECTED]
Subject: RE: JSTL EL Validator rule: A better requiredif and validatewhen
using JSTL
The only reason I didn't
: Steve Raeburn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 26, 2003 4:37 PM
To: Struts Developers List
Subject: RE: JSTL EL Validator rule: A better requiredif and validatewhen
using JSTL
Rick,
It certainly sounds interesting but I'd like to have a working example to
play with.
It would
I only have the JSTL EL validator rule complete. It still needs testing,
logging, and some general refactoring.
Here is the war file
http://www.rickhightower.com/CustomRule.war
Here is the src
http://www.rickhightower.com/CustomRule.zip
Rick Hightower
Chief Technology Officer
Trivera
/show_bug.cgi?id=22743
A JSTL EL Validator rule would make a lot of sense.
Summary: A JSTL EL Validator rule would make a lot of sense.
Product: Struts
Version: Unknown
Platform: All
URL: http://www.rickhightower.com/CustomRule.zip
OS
of validatewhen, just not the
implementation. I've read James' book on Struts and I respect his talent
and
ability. I think JSTL should have been selected instead. If I was voting
back then and my vote counted, I would have given it a -1. I give James
a +1
for effort.
David Graham:
I
I am new to this list so I apologize if I break any etiquette. I was
thinking that I don't like validatewhen or requiredif so I wrote my own that
uses JSTL EL. (I like the idea behind requiredif and validatewhen just not
the implementation.) I believe this approach has several advantages over
What were your thoughts on JSTL EL validator rule?
You commented on BSF and OGNL, but not the JSTL EL validator rule, which I
actually wrote. The others just seem like a good idea.
Regarding:
This is a General suggestion you have probably given many times yourself
First off
Rick Hightower wrote:
What were your thoughts on JSTL EL validator rule?
You commented on BSF and OGNL, but not the JSTL EL validator rule, which I
actually wrote. The others just seem like a good idea.
Sorry, For not commenting on that. I agree that a JSTL EL expression
makes sense.
For now
I am using the JSTL EL Validator that I wrote, but not the BSF or OGNL
ones
I suggested. I just think they would be a good idea. I'll try the BSF
tag
since I don't know much about OGNL. I like the idea of using the same
JavaScript on the client side and the server side, but for now
David Graham et al.
I can feel the train derailing off the tracks. Screch!
For a moment let's pretend that I never mentioned BSF or Rhino. I want to
get your collective thoughts on JSTL EL Validator Rule.
JSTL EL Validator Rule (validatejstl) --
What feedback do
on Struts and I respect his talent and
ability. I think JSTL should have been selected instead. If I was voting
back then and my vote counted, I would have given it a -1. I give James a +1
for effort.
David Graham:
I agree that using the EL for validation makes sense for the reasons you
stated
are not set,
then it defaults to the current mechanism for determining the index
value.
c:forEach var=item items=${items} varStatus=status
html:checkbox indexed=true indexName=status indexProperty=index
.../
/c:forEach
That way you don't have any direct dependency on JSTL, and it might work
. Karr [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Another bright idea,
make indexed work with JSTL forEach and friends
Craig == Craig R McClanahan [EMAIL PROTECTED] writes:
Craig On 4 Jan 2003, David M. Karr wrote:
Can anyone
:
Date: 04 Jan 2003 17:28:58 -0800
From: David M. Karr [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Another bright idea,
make indexed work with JSTL forEach and friends
Craig == Craig R McClanahan [EMAIL PROTECTED] writes
. McClanahan wrote:
On 4 Jan 2003, David M. Karr wrote:
Date: 04 Jan 2003 17:28:58 -0800
From: David M. Karr [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Another bright idea,
make indexed work with JSTL forEach and friends
Craig
Sounds like we're all on the same page here. =:0)
I'm also looking at using the Jelly XLST for views as well (a la the
Velocity View Tools).
Martin Cooper wrote:
On Sat, 4 Jan 2003, Craig R. McClanahan wrote:
Longer term (2.0 time frame probably), I'm playing with more interesting
ideas
) to have the
html tags also look for JSTL iterators. However, to make this work,
we'd need to add a dependency on jakarta-taglibs so that the class would
be available.
I don't think that this would break anything in terms of JSP version
support, since it wouldn't require evaluation of ELs, just looking
On Sat, 4 Jan 2003, James Turner wrote:
Date: Sat, 4 Jan 2003 13:26:34 -0500
From: James Turner [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Another bright idea,
make indexed work with JSTL forEach and friends
As has been
bright idea,
make indexed work with JSTL forEach and friends
As has been pointed out, about the only remaining reason to use
logic:iterate over c:forEach is that you can't use an html:text tag (or
friends) with an indexed property set, because it only looks
be very simple (having peered at the source) to have the
html tags also look for JSTL iterators. However, to make this work,
we'd need to add a dependency on jakarta-taglibs so that the class would
be available.
I don't think that this would break anything in terms of JSP version
support
On Sat, 4 Jan 2003, Martin Cooper wrote:
If you want to do this, I'd rather see it happen in the html-el taglib
than the regular html taglib. Struts-EL already depends on
JSTL, and is
designed to work in cooperation with it, so it's a much more
natural fit
than trying to sneak JSTL
James == James Turner [EMAIL PROTECTED] writes:
James On Sat, 4 Jan 2003, Martin Cooper wrote:
If you want to do this, I'd rather see it happen in the html-el taglib
than the regular html taglib. Struts-EL already depends on
JSTL, and is
designed to work in cooperation
On 4 Jan 2003, David M. Karr wrote:
Can anyone envision any other situations in the Struts code where indirect
references to the JSTL would be convenient? That, at least, could give us some
additional perspective on this.
General purpose access to the EL evaluator (which David used
On Sat, 4 Jan 2003, James Turner wrote:
On Sat, 4 Jan 2003, Martin Cooper wrote:
If you want to do this, I'd rather see it happen in the html-el taglib
than the regular html taglib. Struts-EL already depends on
JSTL, and is
designed to work in cooperation with it, so it's a much more
that in the original code base.
;-)
--
Martin Cooper
James
-Original Message-
From: Martin Cooper [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 04, 2003 4:37 PM
To: Struts Developers List
Subject: RE: Another bright idea, make indexed work with
JSTL forEach
.
2) Empty catch clauses are evil. ;-) You should at least log a debug
message so that real problems can be debugged more easily.
Well, two of them shouldn't log anything because they are simply there
to catch the you haven't got JSTL case, I though about logging the
other cases but they should
class loader is tried first.
I'll do dat.
2) Empty catch clauses are evil. ;-) You should at least log a debug
message so that real problems can be debugged more easily.
Well, two of them shouldn't log anything because they are simply there
to catch the you haven't got JSTL case, I
On 4 Jan 2003, David M. Karr wrote:
Date: 04 Jan 2003 17:28:58 -0800
From: David M. Karr [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Another bright idea,
make indexed work with JSTL forEach and friends
Craig == Craig R
On Sat, 4 Jan 2003, Craig R. McClanahan wrote:
Longer term (2.0 time frame probably), I'm playing with more interesting
ideas like using Jelly scripts (or JSP pages) as Actions so you don't have
to write them in Java. We also need a good high level multi-request
framework, and it might be
There was some discussion on struts-user about how to access java
constants from EL / JSTL.
My idea is to have init parameters in web.xml for ActionServlet of the
form
init-param
param-nametaglib-constant/param-name
param-value[fully-qualified-class]/param-value
I was talking about general constant issues, not the Struts specific
constants. I don't think we need any Struts specific stuff for this.
David
From: edgar [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: 'Struts Developers List' [EMAIL PROTECTED]
Subject: Constants for EL / JSTL
Date
OOPS
-Original Message-
From: edgar [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 10:03 AM
To: 'David Graham'
Subject: RE: Constants for EL / JSTL
The idea wasn't intended to be struts specific, just a way to preload
constant classes for a struts based application
At end.
-Original Message-
From: Craig R. McClanahan [mailto:craigmcc;apache.org]
Sent: Tuesday, October 29, 2002 11:44 PM
David == David Karr Karr writes:
David Presently JSTL tags can't easily access
DynaActionForm objects. I haven't
David used these much, but I
10/30/2002 11:49:13 AM, Karr, David [EMAIL PROTECTED]
wrote:
Does anyone else want to chime in on this?
If you want to make the change, broadening the use of
DynaActionForms sounds like a worthwhile feature to me.
-Ted.
--
To unsubscribe, e-mail:
/show_bug.cgi?id=14116
Add getMap() method to DynaActionForm to let JSTL EL reference DynaActionForms
Summary: Add getMap() method to DynaActionForm to let JSTL EL
reference DynaActionForms
Product: Struts
Version: Nightly Build
Platform: Other
TO THIS MESSAGE WILL NOT BE COLLECTED AND
bugzilla INSERTED IN THE BUG DATABASE.
bugzilla http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14116
bugzilla Add getMap() method to DynaActionForm to let JSTL EL reference
DynaActionForms
bugzillaSummary: Add getMap() method
David == David Karr Karr writes:
David I'm asking this here first, to discuss the technical issues. If it appears
David to be feasible, I'll ask a similar question on the user list, and then
David perhaps write a bug report.
David Presently JSTL tags can't easily access
See below.
On 29 Oct 2002, David M. Karr wrote:
Date: 29 Oct 2002 23:16:25 -0800
From: David M. Karr [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Accessing DynaActionForm objects in JSTL tags?
David == David Karr Karr writes
Personally, I consider DynaActionForms and JSTL as top bullets for 1.1.
But if means delaying the release, well.you know.
James Mitchell
Software Engineer/Struts Evangelist
http://www.open-tools.org
Only two things are infinite, the universe and human stupidity, and I'm not
sure about
/show_bug.cgi?id=13788
Struts-EL: bean:include of a forward isn't covered in Struts-EL/JSTL
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/show_bug.cgi?id=12365
Contribution of Struts-EL library: Struts with JSTL EL attributes
[EMAIL PROTECTED] changed:
What|Removed |Added
AssignedTo|struts- |[EMAIL
/show_bug.cgi?id=12365
Contribution of Struts-EL library: Struts with JSTL EL attributes
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
/show_bug.cgi?id=12365
Contribution of Struts-EL library: Struts with JSTL EL attributes
--- Additional Comments From [EMAIL PROTECTED] 2002-09-06 14:30 ---
Created an attachment (id=2954)
Source distribution of the Struts-EL contribution
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED
Subject: Announce: JSTL (Standard Tags) + Struts (MVC) live web Demo
From: Vic C. [EMAIL PROTECTED]
===
If you are starting a Java Web, you should use MVC and Standard tags,
this kit is a sample of best (at least good) practices.
It is MVC (Struts/Tiles)+JSTL +XSLT+ DAO (Open Source Data
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 10:24 PM
To: [EMAIL PROTECTED]
Subject: Re: Subclass Struts tags to work with JSTL?
Craig == Craig R McClanahan [EMAIL PROTECTED] writes:
Craig On 16 Jul 2002, David M
From: Martin Cooper [mailto:[EMAIL PROTECTED]]
By the way, a good reason to use the name var for the n/p/s
attribute is because that is what JSTL uses for the
equivalent functionality. Consistency is good! ;-)
Well, I'm not sure that it is the equivalent functionality. From the
spec
Tim == Tim Moore [EMAIL PROTECTED] writes:
From: Martin Cooper [mailto:[EMAIL PROTECTED]]
By the way, a good reason to use the name var for the n/p/s
attribute is because that is what JSTL uses for the
equivalent functionality. Consistency is good! ;-)
Tim Well, I'm
on a single tag.
Martin Of course, where the RT tags have n/p/s today, the EL tags would have a
Martin var attribute instead.
Martin b) It matches the approach taken by JSTL itself, with parallel RT and EL
Martin taglibs.
I certainly agree with this. That is how I'm proceeding with my
On 17 Jul 2002, David M. Karr wrote:
Date: 17 Jul 2002 12:07:09 -0700
From: David M. Karr [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Subclass Struts tags to work with JSTL?
Tim == Tim Moore [EMAIL PROTECTED] writes
Craig == Craig R McClanahan [EMAIL PROTECTED] writes:
Craig If we stay with the dual libraries approach, this all makes sense.
Craig One thing we'll want to do *inside* the implementations is maximize the
Craig reuse of the actual tag classes, to minimize the effort of keeping the
On 16 Jul 2002, David M. Karr wrote:
Date: 16 Jul 2002 19:42:46 -0700
From: David M. Karr [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Subclass Struts tags to work with JSTL?
I don't know how much thought has yet gone into how
Craig == Craig R McClanahan [EMAIL PROTECTED] writes:
Craig On 16 Jul 2002, David M. Karr wrote:
I don't know how much thought has yet gone into how Struts and JSTL can work
together. I haven't noticed much serious talk about this. If these thoughts
are obvious or ignorant
On Sat, 22 Jun 2002, Craig R. McClanahan wrote:
One thing I'd like to see done is to have all the Struts tags that use
the name/property/scope pattern of attributes (for access to bean
properties) also support a var attribute that understands the
expression language syntax from JSTL.
I
On Fri, 21 Jun 2002, Shawn Bayern wrote:
Date: Fri, 21 Jun 2002 19:36:56 -0400 (EDT)
From: Shawn Bayern [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: JSTL
Struts developers,
I've just announced the final 1.0 release of the Standard
Struts developers,
I've just announced the final 1.0 release of the Standard Taglib at
Jakarta Taglibs (see announcement below). The Standard Taglib is an
implementation of the JSP Standard Tag Library (JSTL).
Concerning integration between JSTL and Struts in the future, I'm happy
- Original Message -
From: Craig R. McClanahan [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Saturday, April 06, 2002 5:15 PM
Subject: Re: anyone care to clarify difference between struts and JSTL?
On 3 Apr 2002, David M. Karr wrote:
Date: 03 Apr 2002 16:41
Craig == Craig R McClanahan [EMAIL PROTECTED] writes:
Craig My advice to Struts users is as follows:
Craig * If you're running on a Servlet 2.2 / JSP 1.1 container, you
Craig will not be able to use JSTL (it requires Servlet 2.3 / JSP 1.2).
Craig Go ahead and continue using
hi all,
i have taken a stroll through the mail archive and not found any clear
definition of what is the difference between the struts taglibs and the
'standard' taglibs.
let me admit first that i am completely new to JSTL, what i really want to
know is should i keep going with struts tags
On Tue, 2 Apr 2002, Stephenson Tim wrote:
Date: Tue, 2 Apr 2002 17:52:46 +1000
From: Stephenson Tim [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts mailing list (E-mail) [EMAIL PROTECTED]
Subject: anyone care to clarify difference between struts and JSTL
On Tue, 2 Apr 2002, Stephenson Tim wrote:
and some others have been deliberately (and i believe wisely) excluded on
grounds on breaking MVC (eg JSTL sql tags)
On this particular point, here's what I told the Struts BOF audience at
JavaOne:
Shame on you if you use the SQL tags in your
Taglibs community,
The JSP Standard Tag Library (JSTL) just entered its Public Review stage
under the Java Community Process, and Beta 1 of the reference
implementation (RI) is now available through Jakarta Taglibs.
This new draft spec and RI milestone solidifies JSTL in a number of
respects
Once again, I'm happy to announce a new Early Access release of the JSP
Standard Tag Library (JSTL).
Early Access Release 3 introduces tags for database access and
incorporates some changes to the internationalization and XML-manipulation
libraries.
The reference implementation is available
Camino Developers,
[DO NOT REPLY]
Keep an eye on this...
At 08:54 pm 21-11-2001 -0500, you wrote:
Hi everyone -
I'm pleased to announce Early Access Release 2 of the JSP Standard Tag
Library, now called JSTL (which replaces the old acronym, JSPTL). While
it is important to realize that Early
1 - 100 of 102 matches
Mail list logo
