On Wed, 28 Mar 2001, Tahir  Awan wrote:

> Sorry Martin but I could not find any way to contact those volunteers
> (though I can see their names).
> 

STRUTS-DEV is the best way.

> Actually I was expecting that some committer will either accept or reject
> the idea. And if the idea is accepted then I can discuss the changes on
> one-on-one basis. The reason being those changes are just causing only a
> couple of new java class and effecting about 4 existing classes in
> struts/taglibs & struts/utils. So, I thought to first get the idea approved
> before putting in more efforts in formatting those changes to be posted on
> some website.
> 
> Thanks,
> 
> Tahir Awan 
> 

There are a couple of issues:

* I'm trying to hold the line on major feature enhancements for 1.0
  so that we can move to an actual release.  Therefore, discussion for
  major feature improvements can happen now, but implementation cannot
  really start (in the CVS repository) until after 1.0-beta-2 (when the
  repository will be branched so we can finish up 1.0 bugfixes).

* I'm on the road again this week (speaking at O'Reilly Enterprise
  Java Conference) and next week (ApacheCon).  Remote connectivity is
  a much more painful way to do commits than my nice DSL link at home.

I intend to bring 1.0 to a close as fast as humanly possible so that we
can start working on all the fun new stuff, along with (I
hope) increasing the number of committers.  But there are only so many
hours in the day at this point ...

Craig


> > -----Original Message-----
> > From: Martin Cooper [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 28, 2001 1:22 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: development issues
> > 
> > 
> > > Any idea how to wake up committers for struts-dev?
> > 
> > What makes you think they are asleep?
> > 
> > A few points:
> > 
> > 1) Rob Leland made some good suggestions on how to proceed, 
> > in an earlier
> > message on this thread. You might try taking his advice, 
> > although I would
> > recommend his option (1) over his option (2).
> > 
> > 2) The Struts 1.1 TODO list contains two items relevant to 
> > this discussion.
> > One is titled "Standard Validations", and has two volunteers 
> > signed up. The
> > other is titled "Client Side Validation", and has four 
> > volunteers signed up.
> > I would suggest you contact those people, and share your 
> > ideas with them.
> > 
> > 3) There is at least one other implementation of Struts form 
> > validation
> > using regular expressions that I am aware of, which was 
> > written by David
> > Winterfeldt, and is based on the Jakarta Regexp package.
> > 
> > --
> > Martin Cooper
> > 
> > 
> > ----- Original Message -----
> > From: "Tahir Awan" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, March 28, 2001 7:13 AM
> > Subject: RE: development issues
> > 
> > 
> > > That's the exact intention I had while putting in regex 
> > validation i.e.,
> > to
> > > provide basic validation.
> > >
> > > btw, I havn't seen any comment regarding automatic 
> > properties. For us, its
> > > saving a lot of time as we are not worried about 
> > prepopulating the input
> > > fields if some validation fails.
> > > Another scenario is for dynamic html forms. Like we have an 
> > input form
> > where
> > > user can input any number of email addresses. Default is 1 
> > and he can
> > click
> > > "Add Email" and the same form will be displayed with an 
> > additional text
> > box
> > > and all the already entered values intact. And all this is done by
> > framework
> > > without any custom coding in JSP or beans.
> > >
> > > Any idea how to wake up committers for struts-dev?
> > >
> > > Tahir Awan
> > >
> > >
> > > -----Original Message-----
> > > From: Cook, Levi [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, March 27, 2001 10:46 AM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: RE: development issues
> > >
> > >
> > >
> > > Surely I'm reiterating the obvious here, but Javascript alone
> > cannot/should
> > > not be relied upon for validation. It does play a useful 
> > and important
> > role,
> > > however its scope should normally be limited to improving the users
> > > experience with supplying input that our system understands. If the
> > > framework provides a facility for sending Javascript to the 
> > browser, I
> > would
> > > propose including a mechanism that allows the developer to 
> > specify which
> > > browsers their script can safely run in.
> > >
> > > Its just a quick observation, but the role of validation 
> > within Struts (a
> > > web app. framework) should be limited validating user input. This is
> > closely
> > > related to the role an ActionForm plays by representing 
> > user input as
> > > Strings. Therefore, IMHO, the goal of Struts validation 
> > should simply be
> > to
> > > ensure user supplied input can safely be converted into the 
> > objects &
> > > primitives our domain objects expect. Within this context, 
> > validating user
> > > input, regular expressions are very valuable and powerful 
> > and should be
> > made
> > > available.
> > >
> > > As someone else stated earlier, domain specific validations can, and
> > > normally do, require more sophisticated mechanisms than regular
> > expressions
> > > alone provide. In general, I would not advise that anyone make their
> > domain
> > > validations dependant on the validation facilities that Struts or
> > JavaScript
> > > provide.
> > >
> > > Anyway, that my 2 cents,
> > > Levi Cook
> > > Greenbrier & Russel
> > > Madison, Wisconsin
> > > www.gr.com
> > > [EMAIL PROTECTED]
> > >
> > >
> > > -----Original Message-----
> > > From: Jim Richards [ mailto:[EMAIL PROTECTED] 
> > <mailto:[EMAIL PROTECTED]> ]
> > > Sent: Tuesday, March 27, 2001 9:04 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: development issues
> > >
> > >
> > >
> > > >But its not bad either for basic form validation (null, 
> > range checks &
> > > like)
> > > >and much better than using Javascript. I dont think any 
> > backend will rely
> > > >upon JSP validation and wont perform its own tests prior 
> > to saving the
> > > data.
> > >
> > > Well, one of the 1.1 discussions is client side validation using
> > JavaScript,
> > >
> > > which as of JavaScript1.2 has regext facilties built in, so 
> > I'd expect
> > > they'd
> > > be used. But that stops older browsers from working. But as 
> > you point out,
> > > server side validation should be done as well to correctly 
> > check the data
> > > against a greater number of tests.
> > >
> > >
> > > --
> > > Kumera - a new Open Source Content Management System
> > > for small to medium web sites written in Perl and using XML
> > > http://www.cyber4.org/kumera/index.html
> > > <http://www.cyber4.org/kumera/index.html>
> > >
> > 
> > 
> 

Reply via email to