I actually gave reference of the original article by "Thor Kristmundsson" in
my first posting regarding this. It contains the details of the idea and
implementation proposal.
Anyway, here its again.
Article: Strut your stuff with JSP tags by "Thor Kristmundsson" (in Dec-2000
JavaWorld).
http://www.javaworld.com/jw-12-2000/jw-1201-struts.html
The only little problem with this articles is that its outdated with the
current struts code. So, I had to make some more changes in RequestUtils &
PropertyUtils in order to implement the idea.
If anybody needs more info. about this, please let me know. As you might
have guessed, I want to merge those changes in order to remain compatible
with new Struts releases. Even if there's some better implementation, I wont
mind throwing away my code and adopting to the better world.
Tahir Awan
> -----Original Message-----
> From: Martin Cooper [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 3:31 PM
> To: [EMAIL PROTECTED]
> Subject: Re: development issues
>
>
> I'm sure you could find all the addresses in the archives,
> but I agree that
> that is not too convenient. The original intent was that the
> names on the
> TODO list have mailto: links. In fact, the addresses are in
> the XML file,
> but there seems to be a problem with the XSL that generates
> the web page.
>
> Anyway, to get to the point...
>
> I don't think the idea is to come up with final code as the
> first step.
> Personally, I would rather see something like a spec first.
> Nothing formal
> or elaborate, but a detailed description of the functionality
> you would
> propose. You might think of this as writing a first cut at the
> documentation, so that people can see how they would use the
> features you
> are proposing. An example or two would be good. So long as
> it's not very
> long, a message to this list would be fine. Otherwise, a web
> page might be a
> good idea.
>
> Once this has been discussed and accepted, we can move on to
> discussing the
> "best" way of implementing the functionality. At that point, you can
> introduce us to the way you have done it, and we can talk
> about changes or
> potential improvements.
>
> Then it's up to the committers. :-)
>
> (By the way, I should point out that I'm not a committer, just an
> "interested party".)
>
> --
> Martin Cooper
>
>
> ----- Original Message -----
> From: "Tahir Awan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, March 28, 2001 11:55 AM
> Subject: RE: development issues
>
>
> > Sorry Martin but I could not find any way to contact those
> volunteers
> > (though I can see their names).
> >
> > 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
> >
> > > -----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>
> > > >
> > >
> > >
>
>
