Also, I just added a new "Troubleshooting" section to the wiki and
added an entry for this.
Incidentally, sorry for all the posting. I'm getting caught up :)
On 5/24/05, Cris Daniluk <cris.danilu..mail.com> wrote:
> I wonder if we couldn't create a few FindBugs checks for this to put
> on the Wiki..
>
> Would anyone find that useful?
>
> On 5/16/05, Gentry, Michael (Contractor) <michael_gentr..anniemae.com> wrote:
> >
> > This seems to bite a lot of people. Expressions are non-mutable (like
> > String). I thought we had this documented on the wiki (as an FAQ), but
> > maybe not. Could probably stand to be better documented elsewhere (maybe in
> > a big red/bold/flashing font).
> >
> > /dev/mrg
> >
> >
> >
> > -----Original Message-----
> > From: Joshua Pyle [mailto:joshua.t.pyl..mail.com]
> > Sent: Monday, May 16, 2005 1:44 PM
> > To: cayenne-use..bjectstyle.org
> > Subject: Compound expressions Problem and solution
> >
> >
> > One of our developers, new to cayenne, recently ran in to this problem...
> >
> >
> > (didn't work)
> > Expression exp =
> > ExpressionFactory.matchExp(AuthUserAttribute.ATTR_NAME_PROPERTY,
> > testAttributeName);
> > exp.andExp
> > (ExpressionFactory.matchExp(AuthUserAttribute.USERNAME_PROPERTY,
> > testUser));
> >
> >
> > (works)
> > Expression exp =
> > ExpressionFactory.matchExp(AuthUserAttribute.ATTR_NAME_PROPERTY,
> > testAttributeName);
> > exp = exp.andExp(
> > ExpressionFactory.matchExp(AuthUserAttribute.USERNAME_PROPERTY,
> > testUser));
> >
> > It seem smalll but could cost a developer significant time.
> >
> >
> > --
> > Joshua T. Pyle
> > Go has always existed.
> >
>
This archive was generated by hypermail 2.0.0 : Tue May 24 2005 - 10:36:03 EDT