RE: [corona-dev] Collaboration Event not easy to setup

["Everitt, Glenn" <Glenn.Everitt@xxxxxxxxxxxxx>]

I believe the code as of today requires an EventRouter to be defined inside of every ContextContainer that you want to send CollaborationEvents.  No EventRouter defined in the ContextContainer no CollaborationEvents.

It seems that if the EventRouter Uri ever changed it would require updates to every ContextContainer using it.

Glenn Everitt

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Friday, October 27, 2006 6:49 AM
To: Corona development
Subject: RE: [corona-dev] Collaboration Event not easy to setup

Are you proposing that a collaboration event router is required each Context Container (or Project Context Container)?

This would make sense since our collaboration framework has significantly less value when an event router is missing.

However, just because an event router is defined in the Context Container, does not ensure that events are being distributed.  The event router is a separate plugin that may not have been installed.

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Friday, October 27, 2006 2:43 AM
To: Corona development
Subject: Re: [corona-dev] Collaboration Event not easy to setup

Recently I have added a validation when PC is opened. When you open a PC 
and there is no event router defined, there is an error message 
displayed saying that the PC definition is missing the event router and 
the collaboration events won't work. So, people will be aware that if 
they do not have event router defined, it won't work!

The two more possible solutions could be:
1. send to the same server where the PC definition is, but to port 4700.
2. add a configuration property with default router

But I think the best solution is to say that event router definition is 
required.

Marcin

Everitt, Glenn napisał(a):

> The EventRouter method handleEvent calls the suppressSend method which 
> looks at a list of remote EventRouter uri's and decides whether to 
> "really" publish the Collaboration Event. The list of remote 
> EventRouter uri's is placed into the CollaborationEvent (ProjectEvent) 
> by the ProjectEventFactory and it uses information in the 
> ProjectContextContainer to set the remote EventRouter uri's but if 
> your container doesn't have any uri's listed no CollaborationEvent 
> (ProjectEvent) will be sent. I think we should always send to the 
> "default" EventRouter uri and if remote EventRouter uri's are 
> specified also send to them. I'm not sure how someone creating a 
> ProjectContextContainer is supposed to know to set the remote 
> EventRouter uri to get CollaborationEvents sent.
>
> Is there an easy way to determine the "default" EventRouter for User 
> or a ProjectContextContainer? I'm not sure I want the 
> ProjectEventFactory to set the default EventRouter. It seems like the 
> "client" EventRouter should have a way to find and set the default 
> remote EventRouter uri
>
> Comments?
>
> Glenn Everitt
>
> The contents of this e-mail are intended for the named addressee only. 
> It contains information that may be confidential. Unless you are the 
> named addressee or an authorized designee, you may not copy or use it, 
> or disclose it to anyone else. If you received it in error please 
> notify us immediately and then destroy it.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>corona-dev mailing list
>corona-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/corona-dev
>  
>
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.