[FLEX-26425] Inconsistent behaviour in the Module domain with ApplicationDomain.hasDefinition and ApplicationDomain.getDefinition

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: Adobe Flex SDK 4.1 (Release)
• Component/s: Modules
• Environment: Affected OS(s): Windows; Affected OS(s): Windows; Browser: Other (specify version); Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 13/Jan/11 05:36
• Updated: 26/Jan/11 10:31

Description

Steps to reproduce:
1. Create a new project in FlashBuilder 4 using the attached test case zip file.
2. The project contains a simple SWC in the libs folder with just one class in it: MissingClass. That class gets compiled into the module, but using "external" in the compiler settings instead of "merged into code".
3. Run AppDomainTestModule.mxml and click on the "Load Module" button to load.
4. Copy the the debug output for reference. Now move the domain.getDefinition call (line 37) above the domain.hasDefinition calls. and rerun the AppDomainTestModule.mxml.

Actual Results:
The trace output from running AppDomainTestModule.mxml is as follows:
Current Domain: [object ApplicationDomain]
–
hasDefinition:
ModuleWithMissingClass: false
ModuleWithMissingClass: true
getDefinition:
ModuleWithMissingClass: null

Expected Results:
There should be three expected results here as I see it:

1. The domain.hasDefinition call should return consistent results each time.
2. The domain.getDefinition call should return either a valid reference or throw an error, to return null is strange.
3. When the domain.getDefinition call is made prior to the hasDefinition call a VerifiyError is thrown, this is inconsistent with the behaviour mentioned in 2.

Workaround (if any):
None.