Quoting enzhong fu [EMAIL PROTECTED]:
Currently, Struts recommends all fields of ActionForm be of type String. If
you use other type (such as Date), and user inputs the value in an invalid
format so the value could not convert to the suitable type, BeanUtils would
throw an exception and it
Quoting Joe Germuska [EMAIL PROTECTED]:
Oh yeah, also I can't go back from having versioned JAR in my lib
directories. I suspect that's a matter of taste too, but I'll take
the overhead of pruning old JARs when new versions are deployed over
the mystery of knowing which versions your apps
+1 on the TLP proposal.
+0 on me as VP (I'm willing, but don't consider this a prerequisite to
TLP-ness), although I should point out that this is actually only a
*recommendation* to the ASF Board. The Board is free to appoint whomever they
wish, although they've historically tended to go along
Quoting [EMAIL PROTECTED] [EMAIL PROTECTED]:
An alternative is to directly run the python scripts,
it's probably easier than applying the patch.
I could do that.
In the committers module (relicense directory) there is also a Java version of
the relicensing tool that works quite well. I
This is fixed in the Nightly build of Validator as of March 9th.
It may take a few days for the nightly build of Struts to
start using this version, and so it's client side validation
will be broken until that point.
I'm picking up the most recent changes for tonight's nightly build.
Quoting Steve Raeburn [EMAIL PROTECTED]:
The intention is that anyone will be able to submit a logo.
But first, the committers will have to decide whether they want a new
logo. ** There is no competition yet! **
For the record, I'm +1 on having a new logo (well, maybe it's really havig a
I'm happy to announce the availability of the first nightly build of the
integration library supporting the use of JavaServer Faces and Struts that has
been updated to support the final release of JavaServer Faces 1.0. This is not
a formal Apache release; however, it is intended to support
Quoting Greg Reddin [EMAIL PROTECTED]:
Ted Husted wrote:
On Fri, 12 Mar 2004 10:30:08 -0600, Hookom, Jacob wrote:
What I would like to do is develop Struts 2.0 test-first. The idea being we
cold start with a simple application and write just enough of 2.0 to develop
the first page (or
Quoting Joe Germuska [EMAIL PROTECTED]:
We'd like not to subclass ActionServlet, but is really difficult to
do something like this outside the ActionServlet hierarchy mainly
'cause of the call to initConfigDigester(), that's obviously
protected.
The questions are:
- is there a way to
Quoting Joe Germuska [EMAIL PROTECTED]:
At 2:48 PM -0500 3/14/04, Ted Husted wrote:
I'd say we could branch what we have as 1.2 and start thinking of
the HEAD as 1.3.
IMHO, the quickest way to sort out what we need to do with the
Struts-Chain RequestProcessor is to get it out there as
Quoting Thomas L Roche [EMAIL PROTECTED]:
David Geary spoke on JSF at trijug.org M 15 Mar 04. My notes of
his remarks include
- Is JSF a replacement for Struts? Yes!
- JSF is a standard. Struts will never be a standard.
which I believe to be pretty-nearly-direct quotes. I'm assuming
Miscellaneous comments intermixed.
Quoting Martin Cooper [EMAIL PROTECTED]:
The following is a set of proposed changes to the Apache infrastructure to
accommodate the Struts move to an Apache top level project. The idea is to
come up with a single agreed-upon set of changes that we can submit
Quoting Steve Raeburn [EMAIL PROTECTED]:
Like most people, I imagine, I still haven't had time to do more than
give JSF a cursory glance. It's clear that there is some overlap between
JSF and Struts. However, that does not mean that one or other will
simply disappear.
Craig has previously
Quoting Martin Cooper [EMAIL PROTECTED]:
On Sun, 21 Mar 2004, Ted Husted wrote:
On Sun, 21 Mar 2004 00:07:28 -0800, Steve Raeburn wrote:
Option 1 works for me. Simplest thing that could possibly work. As
you've said, we can always change things around later.
The problem is that is
Quoting Martin Cooper [EMAIL PROTECTED]:
On Sun, 21 Mar 2004, Martin Cooper wrote:
On Sun, 21 Mar 2004, Ted Husted wrote:
On Sun, 21 Mar 2004 00:07:28 -0800, Steve Raeburn wrote:
Option 1 works for me. Simplest thing that could possibly work. As
you've said, we can always change
Quoting Thomas L Roche [EMAIL PROTECTED]:
Sun, 21 Mar 2004 13:49:45 -0500, Thomas L Roche (not speaking for IBM)
summary: McClanahan should clearly state *in some major publication*
* that JSF does/will not replace Struts
* how JSF and Struts will likely tend to specialize, in future
Quoting Joe Germuska [EMAIL PROTECTED]:
At 5:24 PM -0800 3/21/04, Craig R. McClanahan wrote:
I think the presentation-tier-independent things about Tiles (like mapping
forwards to definitions) should be built in to the core, so there isn't any
such thing as a separate TilesRequestProcessor
Quoting David Graham [EMAIL PROTECTED]:
Personally, I find the Struts build files to be complex and confusing.
I've come to associate Maven with easy builds because building commons
components (including the distro, website, tests, etc) is a snap compared
to Struts. I agree that storing
Quoting Martin Cooper [EMAIL PROTECTED]:
On Mon, 22 Mar 2004, Ted Husted wrote:
On Mon, 22 Mar 2004 11:36:37 -0700, Matt Raible wrote:
While it's great to break out things into separate modules - I'd
love to be able to get struts.jar w/ everything in it - including
EL and tags. I
Quoting James Holmes [EMAIL PROTECTED]:
+1 on this!!
Agreed.
You hit the nail on the head. Many people (mostly managers) are reluctant
to adopt Struts add-ons because they are not perceived as having the same
tried and true stamp as the official Struts core. I think doing this
Quoting Ted Husted [EMAIL PROTECTED]:
On Tue, 23 Mar 2004 11:53:55 +0100, Filippo Munafò wrote:
Perfect! What you did in JSF is exatcly what we need:
the controller servlet automatically recognize 'META-INF/struts-
config.xml' resources in any JAR files that were included in the
Quoting Martin Cooper [EMAIL PROTECTED]:
On Tue, 23 Mar 2004, Martin Cooper wrote:
On Tue, 23 Mar 2004, Craig R. McClanahan wrote:
Quoting Ted Husted [EMAIL PROTECTED]:
On Tue, 23 Mar 2004 11:53:55 +0100, Filippo Munafò wrote:
Perfect! What you did in JSF is exatcly what we
Quoting Peter A. Pilgrim [EMAIL PROTECTED]:
Joe Germuska wrote:
Whether the classic and el taglibs are one chunk or two isn't
hugely important to me either -- I would prefer that this decision be
made by developers who've done more work on that code to date.
However, I did find
Quoting Joe Germuska [EMAIL PROTECTED]:
At 7:00 AM -0500 3/26/04, Ted Husted wrote:
Another way to go would be to provide a API object in the request
that the tags, or any other presentation technology, could use to
access framework resources.
In this way, no one else would need to the
Quoting Peter A. Pilgrim [EMAIL PROTECTED]:
Craig R. McClanahan wrote:
Quoting Peter A. Pilgrim [EMAIL PROTECTED]:
Joe Germuska wrote:
Whether the classic and el taglibs are one chunk or two isn't
hugely important to me either -- I would prefer that this decision be
made
901 - 925 of 925 matches
Mail list logo
