o put this code someplace else -- like in an Action (or delegate).
It is hard for me to guess without more specific information.
Gogineni, Pratima wrote:
> We have bean:write tags that read bean properties and output to the jsp
> page.
> I am wondering why we are always forced to set be
e to guess without more specific information.
Gogineni, Pratima wrote:
> We have bean:write tags that read bean properties and output to the jsp
> page.
> I am wondering why we are always forced to set bean properties through one
> of the form tags.
>
> In many cases where there ar
We have bean:write tags that read bean properties and output to the jsp
page.
I am wondering why we are always forced to set bean properties through one
of the form tags.
In many cases where there are a lot of common properites to be set it is
easier to set the bulk of the bean properties through
Hi,
I ran into the same problems of overloaded setters in particular for indexed
properties. I have created a short Note based my observations if it is of
any help to other users.
Please comment/correct/add to the note...
Also i think the design patterns for list based indexed properties is ver
Apologies if this was already posted. I requested the digest as well as
looked at the archives & didnt find the below message. So Im assuming it did
not get posted.
> -Original Message-
> From: Gogineni, Pratima
> Sent: Monday, April 12, 2004 4:59 PM
> To: &
5 matches
Mail list logo
