Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common?

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common?

[EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1711587]

Sat, 17 October 2015 15:29

Eclipse User

Hi

in 1.7.1 I get 'Could not bind a reference of component EMFFormsViewService'

I suppose it is because EMFFormsViewService defines reference to ReportService from 'org.eclipse.emfforms.spi.common' bundle. This bundle is not included in 1.7.1

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1711604 is a reply to message #1711587]

Sun, 18 October 2015 04:36

Eclipse User

I also get "No view service of type 'org.eclipse.emf.ecp.edit.spi.DeleteService' found"
I suppose it is because of the same issue - missing some bundles?
'org.eclipse.emf.ecp.edit' is in my dependencies, the classes are there but not the service definition - it seems to be in some of the missing bundles.

Below are listed the bundles I defined as dependency to get EMF Forms working in RCP application:

org.eclipse.emf.common,
org.eclipse.emf.common.ui,
org.eclipse.emf.ecore,
org.eclipse.emf.ecp.application.e3,
org.eclipse.emf.ecp.application.e4,
org.eclipse.emf.ecp.common.ui,
org.eclipse.emf.ecp.core,
org.eclipse.emf.ecp.edit,
org.eclipse.emf.ecp.edit.swt,
org.eclipse.emf.ecp.ui,
org.eclipse.emf.ecp.ui.e4,
org.eclipse.emf.ecp.ui.rcp,
org.eclipse.emf.ecp.ui.view,
org.eclipse.emf.ecp.ui.view.editor.controls,
org.eclipse.emf.ecp.ui.view.swt,
org.eclipse.emf.ecp.validation,
org.eclipse.emf.ecp.view.context.locale,
org.eclipse.emf.ecp.view.control.multireference,
org.eclipse.emf.ecp.view.custom.ui.swt,
org.eclipse.emf.ecp.view.group.model.edit,
org.eclipse.emf.ecp.view.group.swt.embedded,
org.eclipse.emf.ecp.view.group.ui.swt,
org.eclipse.emf.ecp.view.horizontal.model,
org.eclipse.emf.ecp.view.horizontal.model.edit,
org.eclipse.emf.ecp.view.horizontal.ui.swt,
org.eclipse.emf.ecp.view.label.model,
org.eclipse.emf.ecp.view.label.model.edit,
org.eclipse.emf.ecp.view.label.ui.swt,
org.eclipse.emf.ecp.view.migrator,
org.eclipse.emf.ecp.view.model.provider.generator,
org.eclipse.emf.ecp.view.model.provider.xmi,
org.eclipse.emf.ecp.view.rule,
org.eclipse.emf.ecp.view.rule.model,
org.eclipse.emf.ecp.view.rule.model.edit,
org.eclipse.emf.ecp.view.swt.layout,
org.eclipse.emf.ecp.view.table.columnservice,
org.eclipse.emf.ecp.view.table.model,
org.eclipse.emf.ecp.view.table.model.edit,
org.eclipse.emf.ecp.view.table.ui.swt,
org.eclipse.emf.ecp.view.template.service,
org.eclipse.emf.ecp.view.unset,
org.eclipse.emf.ecp.view.util.swt,
org.eclipse.emf.ecp.view.validation,
org.eclipse.emf.ecp.view.vertical.model,
org.eclipse.emf.ecp.view.vertical.model.edit,
org.eclipse.emf.ecp.view.vertical.ui.swt,
org.eclipse.emf.ecp.workspace.core,
org.eclipse.emf.ecp.workspace.ui,
org.eclipse.emf.edit,
org.eclipse.emfforms.common,
org.eclipse.emfforms.core.services,
org.eclipse.emfforms.core.services.databinding.featurepath,
org.eclipse.emfforms.core.services.editsupport,
org.eclipse.emfforms.core.services.emf,
org.eclipse.emfforms.core.services.emfspecificservice,
org.eclipse.emfforms.core.services.locale.default,
org.eclipse.emfforms.localization,
org.eclipse.emfforms.swt.core.di,
org.eclipse.emfforms.swt.core.di.extension,
org.eclipse.emfforms.swt.core.plugin,
org.eclipse.emfforms.swt.treemasterdetail,
org.eclipse.emfforms.view.model.localization

[Updated on: Sun, 18 October 2015 04:47] by Moderator

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1711747 is a reply to message #1711604]

Mon, 19 October 2015 09:44

Eclipse User

could anyone give me a hint - is it something I can ignore, are those services not essential? or are they? is it because I haven't set the target platform?

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1711829 is a reply to message #1711747]

Tue, 20 October 2015 01:25

Eclipse User

Hi,

do you use a feature-based run/product config?

Best regards

Jonas

Am 19.10.2015 um 15:44 schrieb Klim Tow:
> could anyone give me a hint - is it something I can ignore, are those
> services not essential? or are they? is it because I haven't set the
> target platform?

--
--

Jonas Helming

Get professional Eclipse developer support:

http://eclipsesource.com/en/services/developer-support/

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1711891 is a reply to message #1711829]

Tue, 20 October 2015 05:20

Eclipse User

no I don't.. do you think it could be the cause?

I thought if the plugins are not there, then switching to feature-based config wouldn't make them appear anyway
if I switch to feature-based config, is setting of the target platform not needed?

where can I get the list of needed features? the example e4 application MakeItHappen is not feature based, and I cannot find information about it in the docs

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1711995 is a reply to message #1711891]

Tue, 20 October 2015 12:13

Eclipse User

the bundle org.eclipse.emfforms.spi.common has never exist, I was wrong

as far I can see, I have all the bundles are needed to run:

org.eclipse.emf.common,
org.eclipse.emf.common.ui,
org.eclipse.emf.ecore,
org.eclipse.emf.ecp.application.e3,
org.eclipse.emf.ecp.application.e4,
org.eclipse.emf.ecp.common.ui,
org.eclipse.emf.ecp.core,
org.eclipse.emf.ecp.edit,
org.eclipse.emf.ecp.edit.swt,
org.eclipse.emf.ecp.ui,
org.eclipse.emf.ecp.ui.e4,
org.eclipse.emf.ecp.ui.rcp,
org.eclipse.emf.ecp.ui.view,
org.eclipse.emf.ecp.ui.view.editor.controls,
org.eclipse.emf.ecp.ui.view.swt,
org.eclipse.emf.ecp.validation,
org.eclipse.emf.ecp.view.context.locale,
org.eclipse.emf.ecp.view.control.multireference,
org.eclipse.emf.ecp.view.custom.ui.swt,
org.eclipse.emf.ecp.view.group.model.edit,
org.eclipse.emf.ecp.view.group.swt.embedded,
org.eclipse.emf.ecp.view.group.ui.swt,
org.eclipse.emf.ecp.view.horizontal.model,
org.eclipse.emf.ecp.view.horizontal.model.edit,
org.eclipse.emf.ecp.view.horizontal.ui.swt,
org.eclipse.emf.ecp.view.label.model,
org.eclipse.emf.ecp.view.label.model.edit,
org.eclipse.emf.ecp.view.label.ui.swt,
org.eclipse.emf.ecp.view.migrator,
org.eclipse.emf.ecp.view.model.provider.generator,
org.eclipse.emf.ecp.view.model.provider.xmi,
org.eclipse.emf.ecp.view.rule,
org.eclipse.emf.ecp.view.rule.model,
org.eclipse.emf.ecp.view.rule.model.edit,
org.eclipse.emf.ecp.view.swt.layout,
org.eclipse.emf.ecp.view.table.columnservice,
org.eclipse.emf.ecp.view.table.model,
org.eclipse.emf.ecp.view.table.model.edit,
org.eclipse.emf.ecp.view.table.ui.swt,
org.eclipse.emf.ecp.view.template.service,
org.eclipse.emf.ecp.view.unset,
org.eclipse.emf.ecp.view.util.swt,
org.eclipse.emf.ecp.view.validation,
org.eclipse.emf.ecp.view.vertical.model,
org.eclipse.emf.ecp.view.vertical.model.edit,
org.eclipse.emf.ecp.view.vertical.ui.swt,
org.eclipse.emf.ecp.workspace.core,
org.eclipse.emf.ecp.workspace.ui,
org.eclipse.emf.edit,
org.eclipse.emfforms.common,
org.eclipse.emfforms.core.services,
org.eclipse.emfforms.core.services.databinding.featurepath,
org.eclipse.emfforms.core.services.editsupport,
org.eclipse.emfforms.core.services.emf,
org.eclipse.emfforms.core.services.emfspecificservice,
org.eclipse.emfforms.core.services.locale.default,
org.eclipse.emfforms.localization,
org.eclipse.emfforms.swt.core.di,
org.eclipse.emfforms.swt.core.di.extension,
org.eclipse.emfforms.swt.core.plugin,
org.eclipse.emfforms.swt.treemasterdetail,
org.eclipse.emfforms.view.model.localization

and I think those services are essential, so I cannot use EMF Forms

it seems I misunderstood the goal of EMF Forms - I thought it is qualified to build RCP applications that are not generated ECP Editors or whatever the goal is, but not the plain e4 RCP application, because it does not wire its services together in that environment... my fault

[Updated on: Tue, 20 October 2015 12:14] by Moderator

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1711997 is a reply to message #1711995]

Tue, 20 October 2015 12:25

Eclipse User

...sorry for many posts, I forgot to mention that starting example e4 application I get the same message:

!MESSAGE Could not bind a reference of component EMFFormsViewService. The reference is: Reference[name = Provider, interface = org.eclipse.emf.ecp.view.spi.provider.IViewProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addProvider, unbind = removeProvider]

it all happens in latest Mars1 Modeling Edition without any changes

that's why I think it is either broken (which I space out because no one else is issued but me) or it is not qualified for this kind of applications

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1712136 is a reply to message #1711997]

Wed, 21 October 2015 09:31

Eclipse User

"Could not bind a reference of component EMFFormsViewService" doesn't appear in 1.6.0 (mars-R)

"No view service of type 'org.eclipse.emf.ecp.edit.spi.DeleteService' found" appears both in 1.7.1 (mars-1) and 1.6.0

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1712224 is a reply to message #1712136]

Thu, 22 October 2015 04:49

Eclipse User

Hi Klim,
just to solve some misunderstanding:
"it seems I misunderstood the goal of EMF Forms - I thought it is qualified to build RCP applications that are not generated ECP Editors or whatever the goal is, but not the plain e4 RCP application, because it does not wire its services together in that environment"
you understood the goal of EMFForms correctly, we allow you to easily provide forms for your emf data.
Now for the Services:
!MESSAGE Could not bind a reference of component EMFFormsViewService. The reference is: Reference[name = Provider, interface = org.eclipse.emf.ecp.view.spi.provider.IViewProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addProvider, unbind = removeProvider]
There is a bug report for this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=402750
This is just a log message of DS, so as long as all your view models are used you can ignore this.
The DeleteService is a bit trickier:
It is used in order to correctly delete emf objects eg from a tree or a table.
In order to get rid of the log message, you must provide an instance of this service when instantiating the viewmodelcontext. BUT even if the log occurs we have a fallback in place so the elements still will get deleted.
We are currently working on a redesign of the service hierarchies so that we can omit such confusing situations. We plan to finish it for 1.8 .

And to answer you question:
org.eclipse.emfforms.spi.common.report - This is a bundle in org.eclipse.emfforms.common
See eclipse package name conventions:
https://wiki.eclipse.org/Naming_Conventions#Java_Packages

And you can find how to setup a feature based config in this tutorial:
http://eclipsesource.com/blogs/tutorials/getting-started-with-EMF-Forms/
Under "Try the layout in the demo application"

I hope this helps.
Cheers,
Eugen

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1712225 is a reply to message #1712224]

Thu, 22 October 2015 04:51

Eclipse User

thank you very much

I will try it all out

Re: [EMF Forms] 1.7.1: where is org.eclipse.emfforms.spi.common? [message #1712231 is a reply to message #1712225]

Thu, 22 October 2015 05:51

Eclipse User

the fallback DeleteService works, log messages are negligible

after removing programm arg -debugEMFForms is it possible to delete the objects from view /model

great!

Previous Topic:	Barcelona's Eclipse SDK not returning group model list
Next Topic:	[EMF Forms] RCP: Custom validator: no controls highlighting

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 08:30:43 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter