Have you turned on -keep to see what the generated binding code looks like for the class that's failing? This is probably a bug in the binding codegen. You need to look at what's different from the files that worked. Check to see if it's due to your bindable property being named "item" or being typed as XML. Change the binding expression to be less complicated perhaps? What if you wrote a simple function that did the ternary expressions and just passed in a parameter that doesn't do any e4x drilldown?
matt On 9/18/08 8:48 AM, "Guilherme Blanco" <[EMAIL PROTECTED]> wrote: Nope... It didn't work. BUT.... I know how to remove the errors, but then my component will not work. My Form is just and extension of mx Form + new methods The ServiceForm adds a a component (one core.rpc.Service instance) and adds all methods that relates the children (FormItems) and Service request. Later, my ServiceEditForm adds another core.rpc.Service instance, which is responsable to retrieve the item to be editted + other handy methods. If I remove the core.rpc.Service object of ServiceForm, everything works fine. Both instances do not have the same ID. It's weird, because I have a lot of classes that was already extending the Service Form and worked VERY WELL. Maybe because all other classes were including only FormItems? And that's the only place that includes something different? Any ideas are VERY appreciated. Thanks in advance, On Thu, Sep 18, 2008 at 12:27 PM, Michael Schmalle <[EMAIL PROTECTED] <mailto:teoti.graphix%40gmail.com> > wrote: > [Bindable] protected var _item:XML; > > public function set item(value:XML):void > { > this._item = value; > } > > public function get item():XML > { > return this._item; > } > > There is a problem with this; > > The way you have written it makes the protected _item bindable. > > Try this; > > > > protected var _item:XML; > > [Bindable] > public function set item(value:XML):void > { > this._item = value; > } > > public function get item():XML > { > return this._item; > } > > > Mike > > > -- > Teoti Graphix, LLC > http://www.teotigraphix.com > > Teoti Graphix Blog > http://www.blog.teotigraphix.com > > You can find more by solving the problem then by 'asking the question'. >
