James Mitchell wrote:
I consider myself a reasonably minded person, yet I tend to disagree
with such assertions that, in my mind, are unreasonable.
Yeah, but I was being sarcastic.
"Look, an argument isn't simply a contradiction [...]"
"Yes it is."
Dave
---
: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
- Original Message -
From: "Dave Newton" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, May 12, 2005 11:16 AM
Subject: Re: StrutsCatalogInputOutputSeparation
James Mitchell wrote:
I disagree.
James Mitchell wrote:
I disagree.
Wait, trinary logic?
Dave "Is it Friday already?" Newton
Ted Husted wrote:
Reasonable minds can disagree. :)
No they can't.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
AIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, May 12, 2005 10:59 AM
Subject: Re: StrutsCatalogInputOutputSeparation
Ted Husted wrote:
Reasonable minds can disagree. :)
No they can't.
Dave
-
Ted Husted wrote:
Reasonable minds can disagree. :)
No they can't.
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Michael,
I want to continue this discussion because I think it has merit.
I've used the PRG pattern for over a year since I first came across your
article on TheServerSide.com. It works well in most cases, but I don't use
it 100% of the time because of certain limitations. It just happened that
y
Original Message-
From: Michael Jouravlev [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 10, 2005 4:51 PM
To: Struts Users Mailing List
Subject: Re: StrutsCatalogInputOutputSeparation
On 5/10/05, Benedict, Paul C <[EMAIL PROTECTED]> wrote:
> I have read Michael Jouravle
On 5/10/05, Benedict, Paul C <[EMAIL PROTECTED]> wrote:
> I have read Michael Jouravlev's article:
> http://wiki.apache.org/struts/StrutsCatalogInputOutputSeparation
>
> I can't find any blog or comment box on the page, so I'll write here. I
> would like peo
See inline
On 5/10/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote:
> > > Aehm... The double submit problem is not a problem of POST
> > or GET request.
> > > Ist a problem of bad programmed browsers, proxies etc, and
> > there are
> > > enough techniques to avoid it.
> >
> > No. It IS a problem of P
> -Ursprüngliche Nachricht-
> Von: Michael Jouravlev [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 10. Mai 2005 23:58
> An: Struts Users Mailing List
> Betreff: Re: StrutsCatalogInputOutputSeparation
>
> One more thing:
>
> On 5/10/05, Leon Rosenber
> -Ursprüngliche Nachricht-
> Von: Michael Jouravlev [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 10. Mai 2005 23:58
> An: Struts Users Mailing List
> Betreff: Re: StrutsCatalogInputOutputSeparation
>
> One more thing:
>
> On 5/10/05, Leon Rosenber
> > Aehm... The double submit problem is not a problem of POST
> or GET request.
> > Ist a problem of bad programmed browsers, proxies etc, and
> there are
> > enough techniques to avoid it.
>
> No. It IS a problem of POST and GET requests. First, the
> dialog itself. According to HTTP specs,
> > Aehm... The double submit problem is not a problem of POST
> or GET request.
> > Ist a problem of bad programmed browsers, proxies etc, and
> there are
> > enough techniques to avoid it.
>
> No. It IS a problem of POST and GET requests. First, the
> dialog itself. According to HTTP specs,
One more thing:
On 5/10/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote:
> Now seriously. Using ActionForms for result presentation is just a matter of
> bad style, it doesn't mean, that struts is badstyles,
> after all, everything, that can be misused, will be :-)
So, you are saying that using Acti
I've read the article now too, and must say i can't disagree more.
First:
>HTML FORM is submitted from the input page, usually using POST request
method. Struts populates form bean (marked with [F]) with
>request data. Then form bean validates input and if something wrong, it
generates error me
I've read the article now too, and must say i can't disagree more.
First:
>HTML FORM is submitted from the input page, usually using POST request
method. Struts populates form bean (marked with [F]) with
>request data. Then form bean validates input and if something wrong, it
generates error me
On 5/10/05, Benedict, Paul C <[EMAIL PROTECTED]> wrote:
> I have read Michael Jouravlev's article:
> http://wiki.apache.org/struts/StrutsCatalogInputOutputSeparation
>
> I can't find any blog or comment box on the page, so I'll write here. I
> would like peo
Dave Newton wrote:
Isn't that where ActionForms are? In any case, nobody said it couldn't
be encapsulated in some nice, tidy object.
You're absolutely right. This is exactly what I do. It's just that
when Paul said the following:
> I put my output data
> exclusively in request or session attri
ro Salgado
>
> Aladin
>
>
> Benedict, Paul C wrote:
>> I have read Michael Jouravlev's article:
>> http://wiki.apache.org/struts/StrutsCatalogInputOutputSeparation
>>
>> I can't find any blog or comment box on the page, so I'll write here. I
Aladin Alaily wrote:
Doesn't putting all of the output data in the session or even in the
request add even more clutter and confusion? When the data is nicely
packaged in an object you can manipulate it more easily and you can
keep track of where the information came from. Although using an
A
nForm
for this purpose might confuse some, I think that it is a better
alternative than putting the data in the session or request scope.
Aladin
Benedict, Paul C wrote:
I have read Michael Jouravlev's article:
http://wiki.apache.org/struts/StrutsCatalogInputOutputSeparation
I can't f
On 10/05/2005 21:30, "Benedict, Paul C" <[EMAIL PROTECTED]> wrote:
> I have read Michael Jouravlev's article:
> http://wiki.apache.org/struts/StrutsCatalogInputOutputSeparation
>
> I can't find any blog or comment box on the page, so I'll write here. I
I have read Michael Jouravlev's article:
http://wiki.apache.org/struts/StrutsCatalogInputOutputSeparation
I can't find any blog or comment box on the page, so I'll write here. I
would like people to freely respond to my comments.
I disagree with the two-actions methodolo
23 matches
Mail list logo
