Hi,

I would like to know whether there is a port of the AS3 StartupManager utility to Java MultiCore Version?

Thanks,

Arkady.

Thanks Cliff,

That's exactly what I am doing right now. I had to make my MessageVO have a reference the ContactVO. I just wanted to double check whether there is a better solution.

Thanks again.

Arkady.

Thanks for the try, Ondina. 

My scenario is different from what you've described. First of all the messages are retrieved not based on authorId. The collection of messages returned contains messages from different authors. Moreover, they are retrieved from a different server than list of contacts (authors). At any point in time a status of one of the authors may change and then as a result the collection of messages will have to be re-rendered to show the correct status icon for that author. But regardless of how these two collections are retrieved, only the messages collection is assigned as a data provider for the List component. The list component is using ItemRenderer for rendering each message in the list. So ItemRenderer has to access the authors list (proxy) to find the status and name of the author. My question is how to access proxies from the ItemRenderer?

Best regards,

Arkady.

I have a different question on usage of ItemRenderers with pMVC. In my case, I have a list control that displays messages from different users. The requirement is to show an icon indicating message author's status and author's name at the beginning of each message (IM-like UI). The message VO doesn't contain author's status or name - it contains only author's id and message text. The author's name and status can be retrieved using ContactsProxy's getContactById() method that returns a ContactVO object containing contact's id, first/last name, status, etc. So it seems like the only solution is from ItemRenderer to get a reference to the application facade and from it to ContactsProxy to retrieve the required data. On the other hand, it feels like a violation of pMVC principles, since ItemRenderer is a view component and view components should not access proxies directly.

Could you please explain what is the correct approach?

Thanks,

Arkady.