Re: [papyrus-rt-dev] Bug from Papyrus

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

I'm not on Oxygen. I recreated the dev environment to make sure I was on Neon.1. I have installed in my dev environment a few extras such as:

a) CDT

b) CMake Editor

c) Dynamic Languages Toolkit - ShellEd IDE

d) Ecore Diagram Editor (SDK)

I don't think any of these should be relevant. b) and c), strictly speaking, are not necessary, but it's a pain not to have them. But I couldn't do without a) and d). 

My launch configuration is set to use "all workspace and enabled target plug-ins".

I do have some unrelated projects in my workspace, but I close them before launching. I do however keep the Papyrus-RT test bundles open. These shouldn't cause any trouble, should they? I would expect that the dev environment should work as smoothly as possible with whatever we have in the repo.

In any case, the error is a very Papyrus-specific error. "Registry should be started before" ??? What sort of thing can cause Papyrus to raise that?

I may change my launch configuration as you suggest, but that has the drawback that if something new is added, you have to remember to manually update the launch configuration, and in the past I fell for that. It's very easy to forget to update this.

--

Ernesto Posse

Zeligsoft

On Wed, Nov 2, 2016 at 12:09 PM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Nope, I’ve never seen that.

On the latest Papyrus-RT master with the latest Papyrus Neon.2 nightly, I get only the usual “Xyz is already registred [sic] elementtype [sic] but it is not binded [sic] yet” errors.

Are you perhaps mixing Papyrus master (Oxygen) content with Papyrus-RT?  Or do you have test bundles in your run-time launch configuration?

Now that we have a Papyrus-RT RCP, I simulate an RCP launch by launching the Papyrus-RT product with all of the (non-test) Papyrus and Papyrus-RT features selected, not using plug-ins to define the launch configuration.  Maybe that could help you to eliminate some bad interaction?

Christian

On 1 November, 2016 at 16:11:17, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:

Whenever I launch a runtime instance from the development environment I am getting a lot of exceptions from Papyrus like this one:

!MESSAGE Unexpected Error

!STACK 0

org.eclipse.papyrus.infra.core.services.BadStateException: Registry should be started before. (Service= 'org.eclipse.papyrus.infra.services.viewersearch.impl.ViewerSearchService', state= registered)

at org.eclipse.papyrus.infra.core.services.ServicesRegistry.getService(ServicesRegistry.java:406)

at org.eclipse.papyrus.infra.core.utils.AbstractServiceUtils.getService(AbstractServiceUtils.java:117)

Has anyone else experienced this?

--

Ernesto Posse

Zeligsoft

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev