>
> Again, just my oppinion. HTH.
>
> Cheers,
> Freddy.
>
>
> -Mensaje original-
> De: David Suarez [mailto:[EMAIL PROTECTED]
> Enviado el: viernes, 15 de octubre de 2004 17:06
> Para: [EMAIL PROTECTED]; Struts Users Mailing List
> Asunto: RE: Exposing
the
> values have changed.
> If so, throw SecurityException or something similar?
>
> Would that work for you...djsuarez
>
> -Original Message-
> From: Lee Harrington [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 15, 2004 8:52 AM
> To: Struts Users Mailing L
line for all these issues.
>
> Again, just my oppinion. HTH.
>
> Cheers,
> Freddy.
>
>
> -Mensaje original-
> De: David Suarez [mailto:[EMAIL PROTECTED]
> Enviado el: viernes, 15 de octubre de 2004 17:06
> Para: [EMAIL PROTECTED]; Struts Users Mailing L
e: David Suarez [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 15 de octubre de 2004 17:06
Para: [EMAIL PROTECTED]; Struts Users Mailing List
Asunto: RE: Exposing ActionForm and MVC fields
How about creating a hash/digest when you send the page down with your
read-only fields and save it to
...djsuarez
-Original Message-
From: Lee Harrington [mailto:[EMAIL PROTECTED]
Sent: Friday, October 15, 2004 8:52 AM
To: Struts Users Mailing List
Subject: Re: Exposing ActionForm and MVC fields
> In this case, i`m still suceptible to be
> hacked by javascript, because of the ActionForm
ments IBuyer
> > >
> > > Seller seller = (ISeller)mainDataObj;
> > >
> > > then add seller to the request and populate your
> > form from that for the Seller view and vice versa
> > for the Buyer view.
> > >
> > > Friday pub lunch may
Lee, even if i use different Actions i wil be still
using BeanUtils and still suceptible to hacking.
--- Lee Harrington <[EMAIL PROTECTED]> escreveu:
> > In this case, i`m still suceptible to be
> > hacked by javascript, because of the ActionForm
> fields
> > exposure.
> > What about that???
>
ding there, you in Law by any chance ;)
>
> -Original Message-
> From: Hubert Rabago [mailto:[EMAIL PROTECTED]
> Sent: 15 October 2004 15:33
> To: Struts Users Mailing List
> Subject: Re: Exposing ActionForm and MVC fields
>
> > ***
ller)mainDataObj;
> >
> > then add seller to the request and populate your
> form from that for the Seller view and vice versa
> for the Buyer view.
> >
> > Friday pub lunch may have tarred my brain but I
> think that will work :)
> >
> > Chris
> >
> >
> >
Nice rewording there, you in Law by any chance ;)
-Original Message-
From: Hubert Rabago [mailto:[EMAIL PROTECTED]
Sent: 15 October 2004 15:33
To: Struts Users Mailing List
Subject: Re: Exposing ActionForm and MVC fields
> ***
> This
seller to the request and populate your form from that for the Seller view
> and vice versa for the Buyer view.
>
> Friday pub lunch may have tarred my brain but I think that will work :)
>
> Chris
>
>
>
> -Original Message-
> From: Leandro Melo [mailto:[EMAIL PRO
my brain but I think that will work :)
Chris
-Original Message-
From: Leandro Melo [mailto:[EMAIL PROTECTED]
Sent: 15 October 2004 14:49
To: Struts Users Mailing List
Subject: RE: Exposing ActionForm and MVC fields
Hi Chris, what do you mean by "interfaces to filter"
(sor
> In this case, i`m still suceptible to be
> hacked by javascript, because of the ActionForm fields
> exposure.
> What about that???
Different actions. I'd reccomend a dispatch action class...with
different methods depending on whether the buyer or seller submitted.
That way, in the seller meth
:[EMAIL PROTECTED]
> Sent: 15 October 2004 13:53
> To: Struts Users Mailing List
> Subject: RE: Exposing ActionForm and MVC fields
>
>
> Hi guys, thanks for your opinions, it seems that
> both
> of you stick with approach 2.
>
> However, none of you mentioned that "
e changes
> happen by copying and altering each tile fragment
> that is changing and updating the tile definition to
> point to the new fragment.
>
> Chris McCormack
>
> -Original Message-
> From: Freddy Villalba A.
> [mailto:[EMAIL PROTECTED]
> Sent: 15
by copying and altering each tile fragment
> that is changing and updating the tile definition to
> point to the new fragment.
>
> Chris McCormack
>
> -Original Message-
> From: Freddy Villalba A.
> [mailto:[EMAIL PROTECTED]
> Sent: 15 October 2004 11:54
> To:
List
Subject: RE: Exposing ActionForm and MVC fields
Hi,
I'd go for approach #2. After all, they are different VIEWS of the same
Model.
I've faced this situation in a couple of projects before, and in both cases
buyer's and seller's views differed in the long run. The more c
Hi,
I'd go for approach #2. After all, they are different VIEWS of the same
Model.
I've faced this situation in a couple of projects before, and in both cases
buyer's and seller's views differed in the long run. The more complex your
business rules / model gets, the higher is the chance for that
18 matches
Mail list logo