the first code example in this thread is the correct way. If I remember correctly the problem was related to loaderContext. so you might try setting applicationDomain to same as the module that loads other modules.

sorry for late answer..

Well, this is solved now.
The problem was not with the fabrication..but the way I handled variables in modules.

Fabrication works very well. thanks

Yeah I have debugged. It goes like this:
without defining router --> module notification body is correct, but fails to route it.

defining router to be applicationRouter --> module notification body is undefined, but routing works.
i.e. notification is sent and received, notification body is undefined. (still works well for the first module)

So everything in modules works stand-alone, but routing notifications between modules only
happens with the first module.

I think the router is somehow causing the problem.
Looks that I can set it only for the first module.
Should I configure router differently than in case of just one module?

I have mainly extended the flash module example code to have more than one module,
loading is done in a similar fashion with as3-only loader.

I have also noted that flex examples use UID for multimodules,
should I generate some UID for flash modules as well?

all tips are welcome..

Hi just found there is a fabrication section,

I have a minor problem with multiple flash modules.
Seems that only the first module that is loaded into the shell works, so I can't get notification bodies from
the rest of the modules. The notifications seem still to trigger.

If I don't define router, routeNotifications won't go between modules (I use wildcard for recipient).
When I define it, only the first module that is loaded works.

Any pointers to the right direction are appreciated!

:

var module:FlashApplication = navModuleLoader.content as FlashApplication;
module.router = applicationRouter;
module.defaultRouteAddress = applicationAddress;

ps. fabrication is a very, very nice utility! thanks