[#SDK-13460] mxmlc compile errors using custom component in MXML

Flex SDK

mxmlc compile errors using custom component in MXML

Created: 10/22/07 11:44 AM Updated: 05/29/08 05:59 PM

Component/s:

Unspecified - Compiler

Security Level:

Public (All JIRA Users )

Severity:	Non Functioning
Reproducibility:	Every Time
Discoverability:	Low
Milestone:	SDK Moxie RC0
Affected OS(s):	All OS Platforms - All
Steps to Reproduce:	« Hide Steps to reproduce: 1.Use mxmlc to compile the AMP codebase (available in flashfarm) 2. Notice the compile errors in EpisodesScreenLayout.mxml: D:\philo\AMP\dev\AMP\com\adobe\amp\view\pods\episodes\EpisodesScreenLayout.mxml(36): Error: Implicit coercion of a value of type com.adobe.amp.view.pods.shared.hybridlist:HybridListHeaderBar to an unrelated type Object. <hybridlist:HybridListHeaderBar D:\philo\AMP\dev\AMP\com\adobe\amp\view\pods\episodes\EpisodesScreenLayout.mxml(36): Error: Comparison between a value with static type Object and a possibly unrelated type com.adobe.amp.view.pods.shared.hybridlist:HybridListHeaderBar. <hybridlist:HybridListHeaderBar D:\philo\AMP\dev\AMP\com\adobe\amp\view\pods\episodes\EpisodesScreenLayout.mxml(36): Error: Implicit coercion of a value of type com.adobe.amp.view.pods.shared.hybridlist:HybridListHeaderBar to an unrelated type Object. <hybridlist:HybridListHeaderBar Actual Results: Compile errors Expected Results: No compile errors Workaround (if any): Programmatically add the custom component instead of using declarative MXML tags. Show » Steps to reproduce: 1.Use mxmlc to compile the AMP codebase (available in flashfarm) 2. Notice the compile errors in EpisodesScreenLayout.mxml: D:\philo\AMP\dev\AMP\com\adobe\amp\view\pods\episodes\EpisodesScreenLayout.mxml(36): Error: Implicit coercion of a value of type com.adobe.amp.view.pods.shared.hybridlist:HybridListHeaderBar to an unrelated type Object. <hybridlist:HybridListHeaderBar D:\philo\AMP\dev\AMP\com\adobe\amp\view\pods\episodes\EpisodesScreenLayout.mxml(36): Error: Comparison between a value with static type Object and a possibly unrelated type com.adobe.amp.view.pods.shared.hybridlist:HybridListHeaderBar. <hybridlist:HybridListHeaderBar D:\philo\AMP\dev\AMP\com\adobe\amp\view\pods\episodes\EpisodesScreenLayout.mxml(36): Error: Implicit coercion of a value of type com.adobe.amp.view.pods.shared.hybridlist:HybridListHeaderBar to an unrelated type Object. <hybridlist:HybridListHeaderBar Actual Results: Compile errors Expected Results: No compile errors Workaround (if any): Programmatically add the custom component instead of using declarative MXML tags.
Language Found:	English
Bugbase Id:	none
Triaged:	Yes
Regression:	No
QA Owner:	Kristen Sindac
Resolved by:	Paul Reilly
Confirmed Version:	SDK Moxie RC0 - Next Build
Participants:	Brian Riggs, Joel Huff, Jono, Kristen Sindac, Paul Reilly, Peter Flynn and Robert Vollmar (Adobe)
JDK:	Sun 1.4.x

All

Comments

Sort Order:

[ Permlink | « Hide ]

Jono - [10/23/07 01:43 PM ]

Could also be MXMLC of course, Brian doesn't know.

[ Permlink | « Hide ]

Peter Flynn - [10/24/07 07:29 PM ]

Brian has reported this actually occurs with Java 1.5 as well. It is a major issue for his team.

[ Permlink | « Hide ]

Peter Flynn - [10/29/07 04:23 PM ]

I can reproduce this in my FB dev environment running Java 1.4.2

[ Permlink | « Hide ]

Jono - [10/31/07 04:55 PM ]

I'll take a look, though it was filed to ASC.

[ Permlink | « Hide ]

Brian Riggs - [11/09/07 10:10 AM ]

Additional comment from Edwin van Rijkom:

The class that MXMLC was choking on, is an AS defined component inheriting from an MXML defined component. On merging the AS code with the MXML code, removing the inheritance, the compiler seems to recover.

Seems - because this bug is inconsistent: we may just have had 'good luck' on the latest build.

It might be good to forward the 'AS defined classes inheriting from MXML defined classes may cause MXMLC problems' hunch to the Flex team for investigation. I think we may well have 30+ classes doing this without any problems, but there seems to be a yet undefined context where this breaks the compiler, when running on Windows.

[ Permlink | « Hide ]

Jono - [11/10/07 05:47 PM ]

I could not repro this with Flex M3, because I could not compile it due to airglobal incompatibilities. Switching to the latest flex sdk from mainline, latest AIR, latest MXMLC -- everything works, I even watched some MyToons.

It is difficult to be sure that I am reproducing this in 100% the same way you are, but I am able to compile AMP entirely from this changelist, including using MXML tags rather than programmatic instantiation.

I had to make a few changes for compatibility:
   DRMAuthenticator: "event.text" -> (presumably) "event.detail"
   AMP-app.xml: Updated to latest schema.
   NetworkMonitor: monitor.acceptableStatuses -> monitor.acceptableStatusCodes
   ClientId: import flash.data.*;
   ClientLogManager: conn = new SQLConnection(true); -> conn = new SQLConnection();
   EncryptedHashStorage: import flash.filesystem.EncryptedLocalStore; -> import flash.data.EncryptedLocalStore;

I may have missed one file.

My setup: FB Plugin 187248 to Eclipse 3.2.2; Windows XP; Flex SDK pointed at mainline; latest AIK as of 10 November in Flex SDK installed.

[ Permlink | « Hide ]

Brian Riggs - [11/29/07 12:08 PM ]

Still seeing this with the latest builds (Flex Builder 189092, Flex SDK 189154, AIR 112807ap).

[ Permlink | « Hide ]

Robert Vollmar (Adobe) - [11/29/07 05:24 PM - edited ]

Able to reproduce in Builder build 189289 + SDK build 189147, on the Mac. I'll try to break it down into a simpler case.

[ Permlink | « Hide ]

Paul Reilly - [12/11/07 08:34 AM ]

This should be fixed in mainline by change 190636.

[ Permlink | « Hide ]

Kristen Sindac - [12/17/07 05:23 PM ]

confirmed error does not happen in RC0 build 190958