Marco Tedone wrote:
>> Interesting, I also build commercial apps, and try to use wizards
>> whenever
> possible to keep things >simple for my users
>
> We prefer to keep things easy for us also for maintainability as we
> look at the project long life term.
Doing and maintain wizards with stru
Marco Tedone wrote:
- Original Message -
From: "Michael McGrady" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 07, 2004 3:09 PM
Subject: Re: A couple of questions
Hello, Marco,
First, Struts merely adds
> -Original Message-
> From: Jim Barrows
> Sent: Tuesday, September 07, 2004 1:44 PM
> To: Struts Users Mailing List
> Subject: RE: A couple of questions
>
>
>
>
> > -Original Message-
> > From: Marco Tedone [mailto:[EMAIL PROTECTED]
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 1:22 PM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
> What do you mean? This is often our case. I mean, we often
> have com
What do you mean? This is often our case. I mean, we often have composite
value objects: one that contains another, which contains another. Are there
any issues with such design?
Example:
public class OrderVO implements Serializable {
/** Order lines */
private LinesVO[] orderLines; //Eclipse w
> i personally avoid javascript like the plague. :) i think if you keep
> your website design clean and simple, it makes avoiding javascript
> easier. i also believe that no matter how much functionality or
> business you need to accomplish, you can do so with good web page/site
> design, rather
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 12:04 PM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
> Thank you for your emails. I feel I've got a better
> under
hihi all!
--- Marco Tedone <[EMAIL PROTECTED]> wrote:
> We are talking here about the user submitting a form from a JSP page:
> the
> fact that I've got request and action form both populated, doesn't
> suggest
> me any added value in maintainability, it's simply a duplication of
> data. We
> cho
rs Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 07, 2004 7:15 PM
Subject: RE: A couple of questions
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 10:51 AM
> To: Struts Users Mailing List
>
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 11:05 AM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
> We are talking here about the user submitting a form from a
> JSP pag
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 10:51 AM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
>
> >Not really... your way you have to add the code to the
>
We are talking here about the user submitting a form from a JSP page: the
fact that I've got request and action form both populated, doesn't suggest
me any added value in maintainability, it's simply a duplication of data. We
chose Struts as web framework not because of Action Forms (not yet at lea
>Not really... your way you have to add the code to the action to do the
validation and extraction as well as the JSP, model and SQL.
Model and SQL is not necessarily (and often) true: if I used course grained
strategy, it may be that I've already got the field in my model, and if I
use CMP EJB,
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 10:37 AM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
>
> I use it for my login actions when I'm not using container
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] Behalf Of Lionel
> Sent: Tuesday, September 07, 2004 10:30 AM
> To: [EMAIL PROTECTED]
> Subject: Re: A couple of questions
>
>
> Jim Barrows wrote:
> >> How do you manage this ?
> >
I use it for my login actions when I'm not using container managed security.
My typical worse case action is:
TheForm theForm = (TheForm) form;
ActionErrors errors = form.validate();
if( errors.isEmpty()) {
errors = weirdValidations( form);
if( errors.isEmpty()) {
TheVo vo = new TheVo();
BeanUtil
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 10:26 AM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
> >Interesting, I also build commercial apps, and try to use
> wizar
Jim Barrows wrote:
>> How do you manage this ?
>
> I use a defense-in-depth strategy, starting at the UI, and going to
> the Business layer.
as I do.
> I use coarse-grained form objects, but limit the
> fields on the page to what the user can actually change. Depending
> on complexity, I'll eith
>Interesting, I also build commercial apps, and try to use wizards whenever
possible to keep things >simple for my users
We prefer to keep things easy for us also for maintainability as we look at
the project long life term.
>And therefore a whole hell of a lot easier to modify and change a
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 10:06 AM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
>
> - Original Message -
> From: "Jim Barrows"
>If you put it into session scope, then you only have threading issues if
you allow a single user to invoke more then one thread in a session. The
way to avoid that is >to use the request scope.
That's where we came from. On the other side, if you put the action form in
the request form, after
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 10:01 AM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
> - Original Message -
> From: "Matthew Van Horn" &l
- Original Message -
From: "Jim Barrows" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 07, 2004 5:18 PM
Subject: RE: A couple of questions
Because so much of what you're doing in processing th
- Original Message -
From: "Michael McGrady" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 07, 2004 3:09 PM
Subject: Re: A couple of questions
> Hello, Marco,
>
> First, Struts merely adds to yo
- Original Message -
From: "Matthew Van Horn" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 07, 2004 3:22 PM
Subject: Re: A couple of questions
> Not necessarily - you can use one ActionForm to col
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] Behalf Of Lionel
> Sent: Tuesday, September 07, 2004 9:32 AM
> To: [EMAIL PROTECTED]
> Subject: Re: A couple of questions
>
>
> Jim Barrows wrote:
>
> > In much of my code I do:
> > Bea
Jim Barrows wrote:
> In much of my code I do:
> BeanUtils.copyProperties( dataVo, dataForm);
> and I'm done. Your way would require a lot more code.
This seems great, but I can't do that because of user rights.
Some users don't have rights to update certain fields, so I have to call
each setter
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 7:40 AM
> To: Struts Users Mailing List
> Subject: Re: A couple of questions
>
>
>
> > There are many. First, when you use an ActionForm you can
> -Original Message-
> From: Marco Tedone [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 07, 2004 6:53 AM
> To: Struts-users
> Subject: A couple of questions
>
>
> Hi, in my company we are writing a new J2EE application using
> Struts. So far
> we've used standard JSP/Servlet tec
> There are many. First, when you use an ActionForm you can mine the
> values of request parameters from multiple requests.
In the kind of applications we write this is not an issue. Additionally, it
seems to me
that when put in the 'session' scope, there will only be one ActionForm
object for
a
Marco Tedone wrote:
Well, as far as I can see, a part from the validation bit, the use would be
pretty much the same:
with action forms, to retrieve values, I'd have to invoke a getter method on
the action form, while with straight HTML I'd invoke the get on the request.
The downside, as far as I c
On Tue, 2004-09-07 at 23:14, Marco Tedone wrote:
> The downside, as far as I can see, is that I'd have to declare a new class
> for any new form. Are there any other advantages from using ActionForms?
Not necessarily - you can use one ActionForm to collect data from
several HTML forms, for use in
Well, as far as I can see, a part from the validation bit, the use would be
pretty much the same:
with action forms, to retrieve values, I'd have to invoke a getter method on
the action form, while with straight HTML I'd invoke the get on the request.
The downside, as far as I can see, is that I'
Hello, Marco,
First, Struts merely adds to your options. Struts is not invasive. You
don't have to use it at any time.
Second, I find Struts to be absolutely reliable and easy to use. If you
understand how it works, it is also really, really flexible. I worry
sometimes that they will try t
34 matches
Mail list logo
