Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Refactoring : ServiceRegistry

Hello Camille,

 

Have you already committed some changes on that point?

I have recently faced bugs related to service registry (nightly of this week-end)  and wonder if this is related or not to that.

Is it possible that this refactoring work be not committed before October the 14th? We have validation on Papyrus 0.8.x for integration into TOPCASED 5.1.0 during two next weeks.

Thanks

raphaël

 

 

Raphaël Faudou

Atos

+33 534 363 289

+33 610 535 044

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de LETAVERNIER Camille
Envoyé : mardi 27 septembre 2011 16:19
À : mdt-papyrus.dev@xxxxxxxxxxx
Objet : [mdt-papyrus.dev] Refactoring : ServiceRegistry

 

Hello,

 

One of the difficult tasks in the refactoring concerns the ServiceRegistry. Currently, we need an active Papyrus Editor to get the ServiceRegistry (from core.utils). The problem is that we don’t always have access to this editor.

 

I’ve opened a Bugzilla task to discuss the best way of using or implementing the ServiceRegistry :

 

359075: [Refactoring] The access to the ServiceRegistry should not depend on the active Papyrus Editor

https://bugs.eclipse.org/bugs/show_bug.cgi?id=359075

 

 

Camille

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Back to the top