They do, but what the hell. I think we have reached a level of
sophistication (pronounced no dumb people on the team) where this should no
longer be a problem. I really haven't seen validation code in a setter
method anyway. They are usually generated as:
public void setFoo(String foo){
this.foo=foo;
}
On Fri, Dec 10, 2010 at 9:11 AM, Dave Newton <davelnew...@gmail.com> wrote:
> I think they still have to be public, but I don't really remember anymore.
>
> On Fri, Dec 10, 2010 at 10:09 AM, <stanl...@gmail.com> wrote:
>
> > No schit! Going to try it now.
> >
> > On Fri, Dec 10, 2010 at 9:04 AM, Dave Newton <davelnew...@gmail.com>
> > wrote:
> >
> > > On Fri, Dec 10, 2010 at 9:59 AM, <stanl...@gmail.com> wrote:
> > >
> > > > I have always thought the parameters interceptor should reflect on
> > object
> > > > properties in the case where it could
> > > > not find a set/get method.
> > > >
> > >
> > > Properties haven't needed setters since ~2.1, give or take. I don't
> know
> > if
> > > that was an OGNL change or an S2 change, but when I updated the book
> for
> > > S2.1 that was one of the changes I had to make. Don't know if anything
> is
> > > cached or not.
> > >
> > > Dave
> > >
> >
>
