This content has been marked as final. Show 4 replies
httpService works fine from Modules. Can you also send the code in which you load the module.
I'll send it when I get home. Basically, the only real difference I can see from how you were trying to replicate it was that I set the url directly in the module tag like this: <mx:ModuleLoader url="clubmod.swf">.
I'm not the only one who had this problem. There was another guy on flexcoders who ran across this here: http://tech.groups.yahoo.com/group/flexcoders/message/86823. Someone told him to try putting a dummy httpService in the main application, and that if that worked, it meant it was a "shared code" problem, or a "class collision" whatever that means.
Anyway, I tried putting a dummy httpService in the main app, and it worked. So now I have a work around, but I can't understand why it worked or why I had the problem in the first place.
Class collision problem occurs when you are trying to load two modules and bot of them using httpservice. In such cases their definitions don't match.
By adding it to the main app, the definition which gets loaded as part of the main app domain is used for both modules, so they work fine.
Hope it makes it somewhat clear.
I initially encountered the problem when trying to load a single module into an application. There were no other modules, but there were three httpServices in the module. When I couldn't get that to work, I created a new project with a stripped down application and module, with only one httpService. It still didn't work until I added the dummy httpService to the application.
Whatever the problem is, this should be added to the documentation, because I'm sure that lots of people using modules are likely to load more than one module with an httpService.