Boolean bindings in API files
Boolean bindings in API files
- Subject: Boolean bindings in API files
- From: Pascal Robert <email@hidden>
- Date: Wed, 09 Nov 2011 08:52:42 -0500
I have a question about boolean bindings in API files. If I add a binding with a Boolean type, when I call the component with that binding, the binding should not have quotes, e.g.:
<wo:AvailableParts isSubPart=false isNewBuild=true spec="$someObject" />
If I add quotes, I get:
While trying to set the field "isSubPart" on an object of type com.obzerv.fragments.AvailableParts we expected a boolean but received a java.lang.String with a value of false. This often happens if you forget to use a formatter.
Problem is: bindings of bundled WO components, like WOConditional, works fine with quotes. And the biggest problem is that reformatting the component in WOLips adds quotes, so I'm getting the exception if I forgot to remove the quotes.
So, why it works for bundled WO components but not for my own bindings? My API file content is this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wodefinitions>
<wo class="AvailableParts" wocomponentcontent="false"> <binding name="spec"/>
<validation message="'spec' is a required binding.">
<unbound name="spec"/>
</validation>
<binding defaults="Boolean" name="isNewBuild"/>
<validation message="'isNewBuild' is a required binding.">
<unbound name="isNewBuild"/>
</validation>
<binding name="transactionsForBuild"/>
<binding defaults="Boolean" name="isSubPart"/>
<validation message="'isSubPart' is a required binding.">
<unbound name="isSubPart"/>
</validation>
</wo>
</wodefinitions>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden