This content has been marked as final.
Show 3 replies
-
1. Re: rich:select problem or bug
bleathem Jun 11, 2013 2:19 AM (in response to wish79)I take it your #{outsourcedBacking.addOutSourcedBean.type.id} is a primitive? I'm curious, if you change it to it's equivalent object, do you still experience this problem?
-
2. Re: rich:select problem or bug
wish79 Jun 11, 2013 3:49 AM (in response to bleathem)You are right , but what if still i want the value to be primitive is there any other soluation.
-
3. Re: rich:select problem or bug
bleathem Jun 11, 2013 11:06 AM (in response to wish79)The problem is the primitive doesn't have a concept of null. So you can't not-set it - this is pervasive through your application, not just in the view. If you need to distinguish between an empty/unset and a zero value, then you'll need to sue an object.