Alex - I have read your Modules presentation about twenty times so far as well as any other documentation I could find on Modules and Application Domains. I'm pretty sure I understand everything so far.
Pedro - The ValueObject is only being used by this particular module - not by the application (Or any other module). Ian - All other modules work fine with the exchange data. Note that the exchange data and this value object are two different things. I am NOT passing this value object as part of the exchange data. The VO gets created from a remoteObject call. All the above being said, I think I have found my problem. The click event was handled in the renderer. This works fine in an application but does not seem to in a module. By moving the click handler to the datagrid component, the error disappears. This problem crept in whilst I was moving my monolithic app to a series of modules. Thanks for taking the time to push me in the right direction. Steve If anyone can enlighten me as to why click events in item renderers work differently in modules than applications, please do. --- In [email protected], Ian Thomas <i...@...> wrote: > > As Pedro says - my guess would be that you are passing a DetailData > object from one module to the other when you haven't loaded the > modules in the same ApplicationDomain (or from one compiled .swf to > another, if you're not using modules). > > Take a look at the documentation for ApplicationDomain. > > HTH, > Ian > > On Thu, Apr 30, 2009 at 6:18 PM, Pedro Sena <sena.pe...@...> wrote: > > > > > > Are you using modules? > > > > On Thu, Apr 30, 2009 at 2:17 PM, valdhor <valdhorli...@...> > > wrote: > >> > >> > >> Hmmm. Looks like I misspoke. now I get... > >> > >> Type coercion failed. Cannot convert > >> Model.ValueObjects::detaild...@11c0a941 to Model.ValueObjects.DetailData. > >> > >> What is the difference between a > >> > >> Model.ValueObjects::DetailData > >> > >> and a > >> > >> Model.ValueObjects.DetailData > >> >
