Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [CDO]: What's the general behaviour of Defs when attributes are changed?
[CDO]: What's the general behaviour of Defs when attributes are changed? [message #426289] Mon, 22 December 2008 12:19 Go to next message
Andre Dietisheim is currently offline Andre DietisheimFriend
Messages: 131
Registered: July 2009
Senior Member
Hi Eike, Hi all!

I tied the packages attribute of the definition to its inner instance in
CDOPackageManagerDef (packages added to the def are passed to the
CDOPackageRegistry instance if it's already running). I now wonder
what's the general idea behind this. What wold this be applied to for
ex. CDOSession?

1) Would the CDOSession be deactivated and restarted with the new
connector is changed?

2) Or would it only matter as soon as the def is requested to deliver
its instance? it would deactivate the current instance, create a new one
and activate it?

I opt for the second approach.
To my opinion I'd like to stick to the 2nd approach in general. I
believe that stick to the same behaviour is what makes an API well
formed, it acts the way you are used to.

Any ideas on this?
Re: [CDO]: What's the general behaviour of Defs when attributes are changed? [message #426302 is a reply to message #426289] Mon, 22 December 2008 17:40 Go to previous message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6483
Registered: July 2009
Senior Member
André,

I would also prefer approach 2, at least initially. It is way simpler
and seems to cover the majority of use cases.
Approach 1 has more implications than obvious at a first glance: for
instance, the connector of a session could stay the same but its
dependencies could change (i.e. transitive dependencies)...

Cheers
/Eike

----
http://thegordian.blogspot.com



André Dietisheim schrieb:
> Hi Eike, Hi all!
>
> I tied the packages attribute of the definition to its inner instance
> in CDOPackageManagerDef (packages added to the def are passed to the
> CDOPackageRegistry instance if it's already running). I now wonder
> what's the general idea behind this. What wold this be applied to for
> ex. CDOSession?
>
> 1) Would the CDOSession be deactivated and restarted with the new
> connector is changed?
>
> 2) Or would it only matter as soon as the def is requested to deliver
> its instance? it would deactivate the current instance, create a new
> one and activate it?
>
> I opt for the second approach.
> To my opinion I'd like to stick to the 2nd approach in general. I
> believe that stick to the same behaviour is what makes an API well
> formed, it acts the way you are used to.
>
> Any ideas on this?


Previous Topic:[CDO] Modify an existing emf Project(UML2) to CDO
Next Topic:Teneo Ant problem
Goto Forum:
  


Current Time: Mon Feb 24 09:23:07 GMT 2020

Powered by FUDForum. Page generated in 0.01806 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top