You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Wendy Smoak <ws...@gmail.com> on 2006/08/18 14:46:34 UTC
[ANNOUNCE] Struts v1.3.5 Beta
The Apache Struts team is pleased to announce the release of Struts 1.3.5 Beta.
Struts 1.3.5 is available in a full distribution, or as separate
library, source, example and documentation distributions.
http://struts.apache.org/download.cgi#struts135
It is also available in the central Maven repository under Group ID
"org.apache.struts".
Major changes since Struts 1.2 include
* Composable Request Processor
* Arbitrary configuration properties
* Opt-In Cancel Handling
* Enhanced Global Exception Handlers
* Extends attribute
* "isCommitted" Exception Handling
* Postback Actions
* Wildcard ActionConfig properties
Composable Request Processor: For Struts 1.3, we turned the request
processor methods into Commands that are part of a flexible Chain of
Commands.
Arbitrary configuration properties: Most every Struts configuration
element now accepts a map of key/value pairs. Arbitrary configuration
properties let us externalize more of our configurations, encouraging
reuse.
Opt-In Cancel Handling: In Struts 1.3, the Cancel token is only
honored if the new property "cancellable" is set for the Action
Mapping. If the Cancel token is present, but cancellable is not set,
then an InvalidCancelException is thrown. The InvalidCancelExeption
may be caught by a Declarative Exception Handler, like any other
Exception.
Enhanced Global Exception Handlers: We now support use of global
exception handlers in cases when no ActionConfig has yet been
identified, as in with "preprocessing" commands in a custom request
processing chain.
Extends attribute: In the Struts configuration file, we can now use
the extends attribute to adopt default settings from another element,
as we already can in the Tiles configuration files.
"isCommitted" Exception Handling: When using Tiles, sometimes the
response is already committed when an exception occurs. Now, the
ExceptionHandler tests response.isCommitted, and, if true, includes
the configured view path, rather than forwarding to it.
Postback Forms: The action attribute of the Form taglib is now
optional. If omitted, the original URI of the original request is
used.
Wildcard ActionConfig properties: Wildcards can now be used in the
properties of an ActionConfig.
The 1.3.x series of the Apache Struts framework has a minumum
requirement of the following specification versions:
* Java Servlet 2.3 and JavaServer Pages (JSP) 1.2
* Java 2 Standard Platform Edition (J2SE) 1.4
The release notes are available online at:
http://struts.apache.org/1.x/userGuide/release-notes.html
Notes on upgrading from prior versions can be found on the
community-maintained wiki:
http://wiki.apache.org/struts/StrutsUpgradeNotes12to13
--
Wendy Smoak
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Ted Husted <hu...@apache.org>.
After a day or so, the mirrors will have refreshed, and we could
mention it on the downloads page. But, I wouldnt' suggest that we
archive the release documentation on the website until the release
earns GA status and becomes the latest "Best Available Release". As it
stands, some people are still reserving judgment (otherwise it would
not be a beta).
-Ted.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
> Will 1.3.5 appear on the side bar?
>
> Ted Husted <hu...@apache.org> wrote: Thanks so much for mopping this up, Wendy. It's great to see that
> 1.3.5 is finally "out there".
>
> Next stop: 2.0.0 :)
>
> -T.
>
> On 8/18/06, Wendy Smoak wrote:
> > The Apache Struts team is pleased to announce the release of Struts 1.3.5 Beta.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>
> ---------------------------------
> Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
>
--
HTH, Ted.
* http://www.husted.com/struts/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Ted Husted <hu...@apache.org>.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
> So I ask: why is 1.2.x given preference (a version without a label or vote), but not 1.3.5
> (versioned and voted)?
First, 1.3.x is given preference, since 1.3.x is the top-level
website. We have a link to 1.2.x because is *not* the head, it's a
branch.
We had the link to 1.2.x because both the 1.2.x branch and the 1.3.x
head were under active development. It takes time before we know
whether development on a branch has petered out. If someone wants to
remove it now, I would have no complaint.
Though, we never actually declare any of the branches "dead". If
someone wanted to go back and do a 1.1.1 release to add the cancel
hack, there's nothing to prevent that (except motivation).
Or, if someone wanted to roll a 1.2.10 to fix something for some
reason, again the only thing preventing that is a willing volunteer.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
> That would statisfy me. "Current versions" can be versions of the latest release regardless of vote. While "Past Releases" can be actual GA. That's really a good idea!
Close... "Current Versions" are the latest snapshot docs. But 1.3.5
still doesn't get a menu link of its own until it makes GA. :)
I changed site.xml and re-published the site. It will sync in an hour or so.
If you want to add a section on 1.3.5 to the front page of the site,
you're welcome to do so-- the file to update is
current/site/src/site/xdoc/index.xml .
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Paul Benedict <pa...@yahoo.com>.
Wendy,
That would statisfy me. "Current versions" can be versions of the latest release regardless of vote. While "Past Releases" can be actual GA. That's really a good idea!
Paul
Wendy Smoak <ws...@gmail.com> wrote: On 8/18/06, Paul Benedict
wrote:
> If this were true, there would be no 1.2.x link on the sidebar menu. 1.2.9 was the last GA release, which means anything after that is a snapshot or some beta release.
>
> So I ask: why is 1.2.x given preference (a version without a label or vote), but not 1.3.5 (versioned and voted)?
Interesting, I'd move 1.2.x up with 'Current Versions' -- it's not a release.
But 1.2.x is not being given preferential treatment. The 'Struts 1'
link on the menu goes to http://struts.apache.org/1.x/index.html which
is devoted to the 1.3 line.
We could change the 'Current Versions' section to:
Struts 2
Struts 1.3
Struts 1.2
Should that be 'Development Versions' since these are the *.x URLs
that belong to the various SNAPSHOT versions?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail Beta.
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
> If this were true, there would be no 1.2.x link on the sidebar menu. 1.2.9 was the last GA release, which means anything after that is a snapshot or some beta release.
>
> So I ask: why is 1.2.x given preference (a version without a label or vote), but not 1.3.5 (versioned and voted)?
Interesting, I'd move 1.2.x up with 'Current Versions' -- it's not a release.
But 1.2.x is not being given preferential treatment. The 'Struts 1'
link on the menu goes to http://struts.apache.org/1.x/index.html which
is devoted to the 1.3 line.
We could change the 'Current Versions' section to:
Struts 2
Struts 1.3
Struts 1.2
Should that be 'Development Versions' since these are the *.x URLs
that belong to the various SNAPSHOT versions?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Paul Benedict <pa...@yahoo.com>.
>>But, the original question was about the sidebar menu. Those are links
to the archival copies for GA releases, not every incidental beta that
we release.
If this were true, there would be no 1.2.x link on the sidebar menu. 1.2.9 was the last GA release, which means anything after that is a snapshot or some beta release.
So I ask: why is 1.2.x given preference (a version without a label or vote), but not 1.3.5 (versioned and voted)?
Paul
Ted Husted <hu...@apache.org> wrote: On 8/18/06, Paul Benedict
wrote:
> I'll take the correction, but I don't understand it. We released a product and voted it beta --
> a beta release? :-)
As mentioned in another message, we can in fact have beta releases.
But, the original question was about the sidebar menu. Those are links
to the archival copies for GA releases, not every incidental beta that
we release.
We can mention the 1.3.5 beta on the welcome page, download page, and
announcements page. Should it passses the GA muster, then we will
archive the documentation for future reference. (Which is when it gets
a link on the sidebar.)
It's very important to remember that Struts applications tend to have
long life cycles. Nearly all the teams I meet with standardardized on
Struts 1.1. Many other teams are using Struts 1.2 in production, and
may not migrate to Struts 1.3 or 2.0 for many months, or years, or
ever.
We maintain archives of the GA releases for everyone's use and
benefit. (Mostly our own, since it's handy for answering questions
people have about legacy GA releases.) Should 1.3.5 make GA, we will
archive i's documentation too.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Ted Husted <hu...@apache.org>.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
> I'll take the correction, but I don't understand it. We released a product and voted it beta --
> a beta release? :-)
As mentioned in another message, we can in fact have beta releases.
But, the original question was about the sidebar menu. Those are links
to the archival copies for GA releases, not every incidental beta that
we release.
We can mention the 1.3.5 beta on the welcome page, download page, and
announcements page. Should it passses the GA muster, then we will
archive the documentation for future reference. (Which is when it gets
a link on the sidebar.)
It's very important to remember that Struts applications tend to have
long life cycles. Nearly all the teams I meet with standardardized on
Struts 1.1. Many other teams are using Struts 1.2 in production, and
may not migrate to Struts 1.3 or 2.0 for many months, or years, or
ever.
We maintain archives of the GA releases for everyone's use and
benefit. (Mostly our own, since it's handy for answering questions
people have about legacy GA releases.) Should 1.3.5 make GA, we will
archive i's documentation too.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Paul Benedict <pa...@yahoo.com>.
I'll take the correction, but I don't understand it. We released a product and voted it beta -- a beta release? :-)
Wendy Smoak <ws...@gmail.com> wrote: On 8/18/06, Martin Cooper wrote:
> Please be careful with the terminology. There is no such thing as a "beta
> release".
As I understand it, test builds are not releases, but once it passes a
vote it is a sanctioned release of alpha, beta, or GA quality.
I hope so, because I just announced "the release of Struts 1.3.5 Beta". :)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------
Do you Yahoo!?
Get on board. You're invited to try the new Yahoo! Mail Beta.
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Martin Cooper <ma...@apache.org>.
On 8/18/06, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 8/18/06, Martin Cooper <ma...@apache.org> wrote:
>
> > Please be careful with the terminology. There is no such thing as a
> "beta
> > release".
>
> As I understand it, test builds are not releases, but once it passes a
> vote it is a sanctioned release of alpha, beta, or GA quality.
Yes, you're right - I'm spacing. It's been a long week.
--
Martin Cooper
I hope so, because I just announced "the release of Struts 1.3.5 Beta". :)
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Ted Husted <hu...@apache.org>.
On 8/18/06, Wendy Smoak <ws...@gmail.com> wrote:
> As I understand it, test builds are not releases, but once it passes a
> vote it is a sanctioned release of alpha, beta, or GA quality.
True. The rule is that "releases" are approved by the PMC.
>From http://apache.org/dev/release.html
* Releases all have some measure of official approval. What this means
depends on the particular kind of release.
** Stable Releases are releases whose quality has been approved by
the development community and by the ASF project.
** Unstable Releases are releases whose quality has not been
demonstrated sufficiently to the development community to merit the
title of stable release. There are many different kinds of unstable
releases and the same names may mean different things for different
projects. These include release candidates, betas, alphas and
milestones.
Our own charter also states that a release can be classified "alpha",
"beta", or "general available" and reclassified as warranted.
So, once 1.3.5 passes the GA muster, then we would archive the release
documentation for future reference.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/18/06, Martin Cooper <ma...@apache.org> wrote:
> Please be careful with the terminology. There is no such thing as a "beta
> release".
As I understand it, test builds are not releases, but once it passes a
vote it is a sanctioned release of alpha, beta, or GA quality.
I hope so, because I just announced "the release of Struts 1.3.5 Beta". :)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Martin Cooper <ma...@apache.org>.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
>
> I understand both your concerns... But I don't believe it has to be the
> policy that we cannot advertise beta releases on the main page too.
Please be careful with the terminology. There is no such thing as a "beta
release".
1.3.5 is the latest (not the greatest with no GA) but we still have a link
> to 1.2.x, why? It is kind of silly to a dead branch (there will be no more
> 1.2) but are unsure to advertise the 1.3.5. If the side bar simply said "
> 1.3.5 (beta)", people could find it right on the home page and not be
> confused of its status.
>
> Other apache projects (including tapestry and httpd) advertise their beta
> projects on the home page, so why can't we?
To quote Wendy: "we could mention it on the front page".
And your problem with that, again, was...? ;-)
--
Martin Cooper
Paul
>
> Wendy Smoak <ws...@gmail.com> wrote: On 8/18/06, Paul Benedict
> wrote:
>
> > Will 1.3.5 appear on the side bar?
>
> Not until it's a GA release, but we could mention it on the front page
> below the 1.2.9 section.
>
> It is already on the mirrors, in ibiblio, and on the downloads page.
>
> If wider distribution doesn't turn anything else up, in a couple of
> weeks we can consider promoting 1.3.5 to GA status.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>
>
> ---------------------------------
> Stay in the know. Pulse on the new Yahoo.com. Check it out.
>
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
> I understand both your concerns... But I don't believe it has to be the policy that we cannot advertise beta releases on the main page too. 1.3.5 is the latest (not the greatest with no GA) but we still have a link to 1.2.x, why? It is kind of silly to a dead branch (there will be no more 1.2) but are unsure to advertise the 1.3.5. If the side bar simply said "1.3.5 (beta)", people could find it right on the home page and not be confused of its status.
>
> Other apache projects (including tapestry and httpd) advertise their beta projects on the home page, so why can't we?
I have no problem mentioning it on the front page, and said as much in
the message you quoted. Also, the announcements page needs to be
updated, and I need to post it to our own announcements list. Ted can
put it on Struts Central.
But I don't want it on the menu with a link to 1.3.5/index.html unless
it's going to stay, and we've said we will only host archived websites
for GA releases. Once we link to it, it will be indexed, and removing
it will break things (or we'd need another redirect.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Paul Benedict <pa...@yahoo.com>.
I understand both your concerns... But I don't believe it has to be the policy that we cannot advertise beta releases on the main page too. 1.3.5 is the latest (not the greatest with no GA) but we still have a link to 1.2.x, why? It is kind of silly to a dead branch (there will be no more 1.2) but are unsure to advertise the 1.3.5. If the side bar simply said "1.3.5 (beta)", people could find it right on the home page and not be confused of its status.
Other apache projects (including tapestry and httpd) advertise their beta projects on the home page, so why can't we?
Paul
Wendy Smoak <ws...@gmail.com> wrote: On 8/18/06, Paul Benedict
wrote:
> Will 1.3.5 appear on the side bar?
Not until it's a GA release, but we could mention it on the front page
below the 1.2.9 section.
It is already on the mirrors, in ibiblio, and on the downloads page.
If wider distribution doesn't turn anything else up, in a couple of
weeks we can consider promoting 1.3.5 to GA status.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------
Stay in the know. Pulse on the new Yahoo.com. Check it out.
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/18/06, Paul Benedict <pa...@yahoo.com> wrote:
> Will 1.3.5 appear on the side bar?
Not until it's a GA release, but we could mention it on the front page
below the 1.2.9 section.
It is already on the mirrors, in ibiblio, and on the downloads page.
If wider distribution doesn't turn anything else up, in a couple of
weeks we can consider promoting 1.3.5 to GA status.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Paul Benedict <pa...@yahoo.com>.
Kudos to all.
Will 1.3.5 appear on the side bar?
Ted Husted <hu...@apache.org> wrote: Thanks so much for mopping this up, Wendy. It's great to see that
1.3.5 is finally "out there".
Next stop: 2.0.0 :)
-T.
On 8/18/06, Wendy Smoak wrote:
> The Apache Struts team is pleased to announce the release of Struts 1.3.5 Beta.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
Re: [ANNOUNCE] Struts v1.3.5 Beta
Posted by Ted Husted <hu...@apache.org>.
Thanks so much for mopping this up, Wendy. It's great to see that
1.3.5 is finally "out there".
Next stop: 2.0.0 :)
-T.
On 8/18/06, Wendy Smoak <ws...@gmail.com> wrote:
> The Apache Struts team is pleased to announce the release of Struts 1.3.5 Beta.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org