Perhaps. However, I am attempting to use PureMVC multi-core and the
constants I want to use simple define my notification names. Even
thought they are included only in the module code, for some reason the
names are "undefined" when PureMVC attempts to register my commands
when the module PureMVC initializes.  I have found a work around by
placing the notification constants in a common library. It isn't the
best work around, but I need to make some progress.

In the Java world, I am used to getting ClassNotFound exceptions when
messing with class loader and isolation issues (at least Java will
blow chunks if it can't find something verses failing silently). The
only equivalent I can find in AS3 is Application domain. It doesn't
seem to matter if I load the module in the current domain though
(Application.currentDomain). Oh well...any other thoughts? Is this
situation analogous to a Java classloader isolation problem?


--- In [email protected], Alex Harui <aha...@...> wrote:
>
> If the app references a class in a module, it defeats the whole
purpose of modules.  That class will still be linked into the main app.
> 
> Also note that the order that classes get their static initialized
is "random" so be careful if static are anything other than simple values.
> 
> From: [email protected] [mailto:[email protected]]
On Behalf Of Jim Boone
> Sent: Thursday, January 08, 2009 8:46 AM
> To: [email protected]
> Subject: [flexcoders] Module blues...am I going crazy??
> 
> 
> Hi,
> 
> I am attempting to convert an app to use modules but I am seeing
> strange behavior. For example, say I have a constant that I refer to
> as (see Constants class below):
> 
> Constants.something
> 
> in my code. You would expect it to resolve to the string "someThing".
> Unfortunately, after being loaded as a module, Constants.something is
> undefined, not "someThing"!! Is there something magic about static
> constants when they are used in modules? Has anyone ever seen this
> issue?
> 
> Jim
> ---------------
> package blah{
> 
> public class Constants
> {
> public static const something:String = "someThing";
> 
> }
> 
> }
>


Reply via email to