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
|
