You can use a servlet push to accomplish this. Change the content type in
the response header to text and then use print.out statements to output each
line of text. This is a very general explanation so I leave it up to you to
research the specifics. BTW you can use this technique to output abo
Try thinking of it this way. For every JSP page 2 actions take place. The
first action is used to populate the form bean and then control is passed to
the JSP page. During this phase you can ignore reset and set your
properties as you need them. The 2nd action is used to process the user's
res
In keeping with MVC there should not be any business loic in the form bean.
Therefore the action class should be responsible for populating your form
bean. Also, the main purpose of reset() in the form bean is to clear the
form's fields before the post() method populates it with the user's input.
ple design where you could use any
other connection pool by just changing one class.
Dick
- Original Message -
From: "Nick Thomson" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Sunday, January 16, 2000 9:56 AM
Subject: RE: about
Is there something wrong with the built-in connection pooling offered by
struts?
-Original Message-
From: Dick Starr [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 16, 2002 4:34 AM
To: Struts Users Mailing List
Subject: Re: about connectionPool
>From what I have seen by the posting
I have found with struts version 1.0 that if you have nested collections on
a form bean that struts will correctly reslove the getter methods but is
unable to resolve the setter methods. I have been forced to use scriptlets
inside the stuts tags to overcome this problem. I'm hoping the newest
ver
6 matches
Mail list logo
