On Mon, 22 Apr 2002, Struts-dev Newsgroup wrote:
> Date: Mon, 22 Apr 2002 16:25:01 -0700
> From: Struts-dev Newsgroup <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: 1.1 new build needs setter for every getter?
>
> Subject: 1.1 new build needs setter for every getter?
> From: JDavids <[EMAIL PROTECTED]>
> ===
> I used 1.1 beta, and other builds just fine.
>
> Late builds throw an exception if there are no setters.
> Some of my beans/pages do not need a setter, only a getter.
> It throws no such method exception.
> I think it should not require a setter.
> We have 40 beans with lots of properties, but not all properties are
> updateable.
>
> Is it me?
> Do I need a dummy setter in case the field is read only?
>
There's been a bunch of work done on commons-beanutils since Struts
1.1-b1, and I believe part of that was some bug fixes in this area --
could you try a recent nightly build and see if the problem still exists?
If so, please file a bug report in Bugzilla so that the issue does not get
lost.
http://nagoya.apache.org/bugzilla/
> tia, Vic
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
