Hi IMO, the easier way for event coplet communication, is to use the cl:link transformer. The portal engine, from the CVS at least since Dec 14th, came with a new sample that shows how to synchronized 2 coplets. A <cl:link coplet="MyCoplet-1" path="attributes/MyAttribute" value="MyValue"/> transform into a anchor that create an event that put 'MyValue' in the attribute 'MyAttribute' of the coplet 'MyCoplet-1'. Laurent
________________________________________ De�: Stefan Eichenhofer [mailto:[EMAIL PROTECTED] Envoy�: mercredi 17 d�cembre 2003 11:20 ��: [EMAIL PROTECTED] Objet�: events in the portal engine Hi all, one more portal-question: How does a coplet subsribe itself to events? I've created a simple "Hello World" coplet class (implementing CopletAdapter) and successfully registered it into the portal. This is working so far, but now i want the coplet to be informed if another coplet creates an event. What i can see from the URICopletAdapter is that the coplet has to implement the Interface Subscriber. But how is the connection to DefaultEventManager established? The DefaultEventManager calls the getEventType() and inform() methods of the URICopletAdapter class, but where does it get the information to do so? thnx for help! stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
