Redundant only if you're using the appropriate prerequisites. As a
practical matter, not everyone can migrate as quickly as they might
like. In the 2.x series, the JSTL argument would have some technical
merit. In the 1.x series, it is not applicable to everyone in our target
base.
Of course,
Thought are welcome, patches are appreciated. Test cases are ... really
nice :-) If there's one thing I've found, persistence (polite
persistence) is a very good thing to have as well ;-)
John Yu wrote:
At 08:31 pm 01-03-03, you wrote:
First, David was probably trying to be helpful. (Why rei
Summing up, is it fair to say that "an enhancement request which comes with
a patch (and possibly some test cases) will be given relatively higher
priority, regardless whether its functionality overlaps with other
technologies"? (And "persistence counts as well.")
I personally won't commit any c
At 08:31 pm 01-03-03, you wrote:
First, David was probably trying to be helpful. (Why reinvent the wheel?)
No dispute about that! David's and other committers' dedication of time and
energy is much appreciated.
But to answer your question, I think the litmus test would be whether
there is a wor
At 01:36 am 02-03-03, you wrote:
The test I use is this:
Does the requested feature exist in JSTL? If so, don't duplicate the
effort in Struts. This is not just my opinion, it has been discussed
among the committers before.
I don't think people requesting enhancements or patches realize the am
At 03:15 am 02-03-03, you wrote:
My personal preferences on the immediate future are to make Struts 1.2 an
evolutionary path for existing 1.0 and 1.1 users, but adopt a "release
often" model of 1.2.x releases like what the Apache HTTPD server does, and
what Tomcat 4.1 and 5.0 have adopted -- relea
Craig R. McClanahan wrote:
On Sat, 1 Mar 2003, Ted Husted wrote:
Date: Sat, 01 Mar 2003 17:56:04 -0500
From: Ted Husted <[EMAIL PROTECTED]>
Reply-To: Struts Developers List <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: Short term plans
Craig R
Thank you for reminding us of that - seems (nearly) everyone (except
you, I, and [ probably still ] Craig) wants to do that in 1.2.0 and that
was, at the time we decided to make 1.2.x move to an incremental build
system, determined to be more than 1.2.0 should entail.
... and folks wonder why
The sentiments are good but the reality is sometimes different.
I submitted two sets of logic tags in May 2001 which provided switch/case
and if/and/or/else logic. They were basically wrappers for the existing
struts logic tags.
They were rejected at the time because the JSTL would be providing t
On Sat, 1 Mar 2003, Ted Husted wrote:
> Date: Sat, 01 Mar 2003 17:56:04 -0500
> From: Ted Husted <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Short term plans
>
d Graham [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 01, 2003 6:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Short term plans
>
>
> How about we solve the 7 remaining 1.1 bugs first ;-).
>
> Dave
>
>
>
> >From: Ted Husted <[EMAIL PROTECTED]>
&g
How about we solve the 7 remaining 1.1 bugs first ;-).
Dave
From: Ted Husted <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: Short term plans
Date: Sat, 01 Mar 2003 17:56:04 -05
Craig R. McClanahan wrote:
My personal preferences on the immediate future are to make Struts 1.2 an
evolutionary path for existing 1.0 and 1.1 users, but adopt a "release
often" model of 1.2.x releases like what the Apache HTTPD server does, and
what Tomcat 4.1 and 5.0 have adopted -- release a ne
Craig R. McClanahan wrote:
http://www.geocities.com/fullback_21_csca/index5.htmlhttp://www.geocities.com/fullback_21_csca/index5.htmlhttp://www.geocities.com/fullback_21_csca/index5.html
* I'm interested in decoupling the controller part of Struts
from its current heavy reliance on the Servlet AP
On Sat, 1 Mar 2003, John Yu wrote:
> Date: Sat, 01 Mar 2003 16:34:07 +0800
> From: John Yu <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Short term plans
>
> A
standard taglib.
David
From: John Yu <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Subject: Re: Short term plans
Date: Sat, 01 Mar 2003 16:34:07 +0800
At 11:46 am 01-03-03, y
The plan is to change the base servlet requirement in 2.0 not 1.2.
David
From: Vic Cekvenich <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Short term plans
Date: Sat, 01 Mar 2003 07:37:38 -0500
Yes, it
ices" in 1.2. Alternative? Struts 1.2 in
18 months?
.V
Craig R. McClanahan wrote:
On Fri, 28 Feb 2003, David Graham wrote:
Date: Fri, 28 Feb 2003 17:50:08 -0700
From: David Graham <[EMAIL PROTECTED]>
Reply-To: Struts Developers List <[EMAIL PROTECTED]>
To: [EMAIL PR
First, David was probably trying to be helpful. (Why reinvent the wheel?)
But to answer your question, I think the litmus test would be whether
there is a working patch annexed.
All anyone has said is that since the attention of the Committers in
their own work is likely to be on other technolo
At 11:46 am 01-03-03, you wrote:
JSTL (and JavaServer Faces, when it becomes available) require Servlet 2.3
and JSP 1.2, so they are not even an option for a very significant portion
of the Struts user community. Thus, it would be irresponsible to abandon
our focus on ensuring the quality of the S
uts Developers List <[EMAIL PROTECTED]>
Subject: Re: Short term plans
Date: Fri, 28 Feb 2003 19:46:27 -0800 (PST)
On Fri, 28 Feb 2003, David Graham wrote:
> Date: Fri, 28 Feb 2003 17:50:08 -0700
> From: David Graham <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL
On Fri, 28 Feb 2003, David Graham wrote:
> Date: Fri, 28 Feb 2003 17:50:08 -0700
> From: David Graham <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Short term plans
>
> The taglibs are a heavi
The taglibs are a heavily used feature. We get a lot of bug reports on them
so the tests are badly needed. There is no doubt that we should use JSTL
but at this point not everyone has that option.
David
With respect, consider how much time struts-devs should spend on tags, I
kind of agree wi
With respect, consider how much time struts-devs should spend on tags, I
kind of agree with those that say slowly move them over to taglibs and
separate jar away from "core" struts, for example if JSTL can do it.
Of course I know, open source means donating contributors kind of get to
work on w
> -Original Message-
> From: James Mitchell [mailto:[EMAIL PROTECTED]
>
> My plans are to finish up html this weekend, and tiles, upload, and
> validator by the end of next week. After that I hope to get all the
> nested tags done between 3/15 and 3/22, then move on to the struts-el
> tag
Sounds great James! Thanks a bunch for doing the tests.
David
From: "James Mitchell" <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Subject: Short term plans
Committers/Developers
As most of you know, I've been adding Cactus tests to try and cover
(hopefully) all the core taglibs with every conceivable combination of
attributes.
Considering the hierarchy of how the tags are implemented, someone might
say that a lot of these tests are redundant, but
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 2:41 PM
To: Struts Developers List
Subject: Re: Comptability of JSR 127 and Struts [Was: SHORT TERM PLANS]
"Craig R. McClanahan" wrote:
> I've got one more useful new goody on my workbench - an ActionForm
> implemen
"Craig R. McClanahan" wrote:
> I've got one more useful new goody on my workbench - an ActionForm
> implementation that uses the new DynaBean APIs in the Commons version of
> BeanUtils that let you define form beans without having to write all the
> properties in individual bean classes.
Bryan Fi
On Mon, 14 Jan 2002, John Yu wrote:
> Date: Mon, 14 Jan 2002 20:13:47 +0800
> From: John Yu <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Comptability of JSR 127
opers List <[EMAIL PROTECTED]>
> > To: Struts Developers List <[EMAIL PROTECTED]>
> > Subject: Comptability of JSR 127 and Struts [Was: SHORT TERM PLANS]
> >
> > I'm wondering how JSR-127 will fit with Struts.
> >
>
>It's too early to know much, bu
the release process, and will have
very little impact on the way people build Struts today.)
--
Martin Cooper
- Original Message -
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, January 13, 2002
On Mon, 14 Jan 2002, John Yu wrote:
> Date: Mon, 14 Jan 2002 11:13:34 +0800
> From: John Yu <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Comptability of JSR 127 and Strut
I'm wondering how JSR-127 will fit with Struts.
While it's beyond my comprehension how JSR-127 will look like and offer, I
have this gut feeling that there is an architectural impedance. Frankly,
it's still vague to me what and how JSR-127 tries to achieve and I always
thought the JSR-127 effo
"Craig R. McClanahan" wrote:
> What about the stuff that's shared across multiple taglibs
> (org.apache.struts.util.*, org.apache.struts.action.*, and so on)? I
> haven't checked them all, but I'd be surprised if *any* of the tag
> libraries can stand on their own without needing the proposed
> s
On Sat, 12 Jan 2002, Martin Cooper wrote:
> Date: Sat, 12 Jan 2002 23:16:29 -0800
> From: Martin Cooper <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: [SHORT TERM PLANS]
> Take a squizz at the tutorials I put up on my nested extension page.
http://www.dictionary.com/cgi-bin/dict.pl?term=squizz
:)
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Building Java web applications with Struts.
-- Tel +1 585 737-3463.
-- Web http://www.husted.com/struts/
--
To un
Arron Bates wrote:
> PS: Any tag extensions planned for the "Short Term Plans"? :)
I think most of us are waiting on the JSTL.
What we have now seems sufficient, especially in a MVC environment, and
I would be concerned about doing anything that would heighten the
migration path.
hat the effort
in creating tutorials in such a manner is beneficial.
It does add to the development time however.
All that other stuff in the blank.war etc...
blank.war was how I first started hacking Struts, so I'm +1 on keeping
that system alive.
Arron.
PS: Any tag extensions planne
Martin Cooper wrote:
> I'm planning on making some other changes to the Struts build process in the
> near future, and I could certainly roll these in if people think it would be
> desirable.
Here's a different but related issue.
For the example applications, I'm wondering if we want to adopt a
I'm definately +1 on a core Strut JAR.
I'm alo +1 on a struts-template.jar. We might consider moving this to
contrib, since many people are migrating to Tiles. I could help with
that if it matters, or just update the documentation when we are
through.
I'm +0 on either putting the others (bean,
t;
Sent: Saturday, December 15, 2001 8:35 AM
Subject: Re: [SHORT TERM PLANS]
> Ooops, one more.
>
> * Adjust the build process so that there is a struts-core.jar and a
> struts-tags.jar
>
>
> Ted Husted wrote:
> >
> > So to wrap up several outstanding threads, he
Ooops, one more.
* Adjust the build process so that there is a struts-core.jar and a
struts-tags.jar
Ted Husted wrote:
>
> So to wrap up several outstanding threads, here's what is on my
> near-term agenda
>
> * Commit the initial ContextHelper to ActionServlet.
>
> * Commit the InvokeActi
So to wrap up several outstanding threads, here's what is on my
near-term agenda
* Commit the initial ContextHelper to ActionServlet.
* Commit the InvokeAction class to ActionServet.
* Commit a SuperForm base class to action, for discussion purposes.
* Develop a "smart" ActionForward class,
44 matches
Mail list logo
