Where ever you are using the class just use the full qualified name for the
calss.
for eg. use com.example.product.element.YesNo
This should resolve the ambiguity.
Best Regards,
Nikhil Tuli.
Associate Software Engineer,
Fidelity Business Services India Pvt. Ltd.,
7th Floor, Tower D,
Uni TechWorld, Sector 39,
Gurgaon - 122 001.
Phone (India) : +91 124 283 3209
Phone (US): 8 804 4395
"il n'y a rien tel que noir ou blanc, toutes sont différentes dégradés de gris"
"Any comments or statements made in this email are not necessarily those of
Fidelity Business Services India Pvt. Ltd. or any of the Fidelity Investments
group companies. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged
material. If you have received this in error, please contact the sender and
delete the material from any computer. All e-mails sent from or to Fidelity
Business Services India Pvt. Ltd. may be subject to our monitoring procedures."
_____
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of
Justin Patrin
Sent: Friday, June 08, 2007 6:36 AM
To: [email protected]
Subject: [flexcoders] Ambiguous class usage in generated code
I have a YesNo class in the com.example.element package which
implements a generic YesNo component. I then have a YesNo class in the
com.example.product.element package which has package specific code.
This works just fine if I am not using bindings. However, if I use a
{} binding in the MXML of the package YesNo I get a generated code
error saying that the usage of class YesNo is ambiguous.
It looks like the code generator is incorrectly assuming that all
classes used will have different names and importing the generic
YesNo, causing this error.
Any easy fix would be to include the package in the class use I would
think.
Anyone know a workaround which does not involve changing the name of
the extended class?
--
Justin Patrin
