--- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > Yes, all if/unless attributes should behave the same (target is not > alone with its interpretation, take a look at PatternSet.NameEntry or > JUnitTest). > > What kind of use case would be satisfied by treating empty properties > similar to those that don't exist? I think the current concept is > quite clear.
I have a need to test if a property is set "true" or "false". Didn't see anything in the doc that would do that. Is that available? (I know, it seems like I should be able to not have that need, but I've tried working around it every way I can think of [which, admittedly, I might not be thinking all that well today], and I can't think of any way.) Diane ===== ([EMAIL PROTECTED]) __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/
