Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Today's Messages (on)  | Unanswered Messages (off)

Forum: EMF "Technology" (Ecore Tools, EMFatic, etc)
 Topic: [EMFForms]Trouble with Table Control domain model reference
Re: [EMFForms]Trouble with Table Control domain model reference [message #1741674 is a reply to message #1741173] Sat, 27 August 2016 02:36
Bill Kinahan is currently offline Bill KinahanFriend
Messages: 2
Registered: August 2016
Junior Member
Thanks Eugen, that helps a bit until I attempt to add columns, it looks like the column specifications fail EMFForms validation with the following error reported for each column: "Domain model reference is unresolvable. Failed on domain model Feature: myFieldName"

This happens when I use the generate columns feature in the control browser in the editor and when I attempt to do it manually.

When I run the app, the columns appear, but I do get an additional column titled Validation Status. Is there any way to prevent that from getting added?

I'm probably overloading this thread, but I have two other things I'm seeing which are puzzling.

First, when I open an element for editing, it appears that the width of the tabbed panel is only slightly wider that the tab title which causes the controls to be rendered in a very narrow space. When I edit a property and move to edit another, the panel resizes and consumes the full editing pane as it is supposed to.

Second, I'm seeing different behavior when I run the app as an e4 product vs an e3 product. When running as e4, I don't get the option to add repositories and when I attempt to connect to the local server I get an exception stating the workbench has not yet been created. I also do not see the narrow controls as I describe in the previous paragraph.

Perhaps these topics deserve their own thread?
Forum: OM2M
 Topic: Writing IPU plugins for non ip enabled technologies (Zwave, ZigBee)
Re: Writing IPU plugins for non ip enabled technologies (Zwave, ZigBee) [message #1741678 is a reply to message #1741518] Sat, 27 August 2016 07:09
Klemen Petrovcic is currently offline Klemen PetrovcicFriend
Messages: 30
Registered: November 2015
Member
Hi Yoshida,

Yes, I created two sample plugins for these two technologies. For the Zwave technology I used the zwave4j library, for the ZigBee technology I used the Xbee library. Since the OneM2M specifications don't specify the mapping for these two technologies I implemented two custom IPU plugins, with only basic functionality.

[Updated on: Sat, 27 August 2016 08:51]

Report message to a moderator

Forum: EMF
 Topic: NoSuchElementException while traversing CDOResource.getAllContents()
Re: NoSuchElementException while traversing CDOResource.getAllContents() [message #1741675 is a reply to message #1741671] Sat, 27 August 2016 05:26
Eike Stepper is currently offline Eike StepperFriend
Messages: 6213
Registered: July 2009
Senior Member
The stack trace of the NullPointerException suggests that there's something wrong with the nsURIs in your Ecore file. Does it contain nested EPackages? If so, Are their nsURIs changed (compared to their first registration in the repository)?
Re: NoSuchElementException while traversing CDOResource.getAllContents() [message #1741679 is a reply to message #1741675] Sat, 27 August 2016 07:21
Alexander Nehmer is currently offline Alexander NehmerFriend
Messages: 7
Registered: January 2016
Junior Member
The nsURIs in the Ecore file are the evolved ones, e.g. masterdata6 whereas in the CDO repo the appropriate nsURI would be masterdata5. I increment them with every Edapt based release as suggested by Edapt.
The curious thing is: when I do
session.getPackageRegistry().getEPackage("masterdata6")

I get as expected
null

But when I do
session.getPackageRegistry().getEPackage("masterdata5")

this NPE posted above occurs.
Re: NoSuchElementException while traversing CDOResource.getAllContents() [message #1741680 is a reply to message #1741679] Sat, 27 August 2016 07:59
Eike Stepper is currently offline Eike StepperFriend
Messages: 6213
Registered: July 2009
Senior Member
Without a test case that I can run in order to reproduce the problem I'm running out of ideas. Can you provide such a test case? Please have a look at the subclasses of AbstractCDOTest. If you can't expose your model or code to the public you can also send it to me privately.
Re: NoSuchElementException while traversing CDOResource.getAllContents() [message #1741682 is a reply to message #1741680] Sat, 27 August 2016 09:23
Alexander Nehmer is currently offline Alexander NehmerFriend
Messages: 7
Registered: January 2016
Junior Member
I tracked down the problem further more. Sorry that I oversaw this in a previous debugging session.
in org.eclipse.emf.cdo.internal.common.model.CDOPackageUnitImpl.loadPackageFromGlobalRegistry(String packageURI) there is a call to
EPackage.Registry.INSTANCE.getEPackage(packageURI); //packageURI = masterdata5

Because the EPackage.Registry.INSTANCE is only populated with the Ecore based model classes (all with nsURI = masterdata6)
the getEPackage(packageURI) finds for masterdata5 only a EPackageDescriptor which leads to a subsequent call to
ePackageDescriptor.getEPackage();

that gets the EPackage in org.eclipse.emf.ecore.plugin.RegistryReader.getEPackage() via
Class<?> javaClass = CommonPlugin.loadClass(element.getDeclaringExtension().getContributor().getName(), element.getAttribute(attributeName));

what gets the evolved model package class with then the new nsURI masterdata6 that is then queried in CDOPackageRegistryImpl. But there it is not present as there is only masterdata5.

That's why the NPE vanishes if I put the Edapt metamodel packages in the EPackage.Registry.INSTANCE.

The NoSuchElementException always occurs at the same point, i.e. at loading the same element (I looked into the repo via the repo web browser). It's an object with a EReference to the evolved model class, i.e. that class I introduced an new EAttribute in masterdata6 in comparison to masterdata5.

While traversing the collection the call to org.eclipse.emf.internal.cdo.view.AbstractCDOView.createObject(CDOID id) seems to cause the problem, because if I place a conditional breakpoint at line 1831 if the problematic object is about to be created the breakpoint is hit
1831    int originalCount = objectCreationCounter;
1832    InternalCDORevision revision = getRevision(id, true);
1833    if (revision == null)
1834    {
1835     throw new ObjectNotFoundException(id, this);
1836    }

If I place a conditional breakpoint at line 1833 the NoSuchElementException occurs.

Any ideas? Nevertheless I'll continue to look into the problem.
Forum: Papyrus
 Topic: Marte profile( Papyrus problem)
Re: Marte profile( Papyrus problem) [message #1741684 is a reply to message #1740924] Sat, 27 August 2016 11:19
Raoudha Saida is currently offline Raoudha SaidaFriend
Messages: 13
Registered: June 2016
Junior Member
Hi Carsten,
I tried using your method to extend MARTE profile with new classes.
Why you do the import of MARTE profile within the new created profile? I couldn't find the option "using the UML packages import mechanism"
Could you help me please.
Re: Marte profile( Papyrus problem) [message #1741687 is a reply to message #1741684] Sat, 27 August 2016 14:43
Carsten Pitz is currently offline Carsten PitzFriend
Messages: 24
Registered: May 2015
Location: Germany
Junior Member
Quote:
Why you do the import of MARTE profile within the new created profile?

I do not know if it is strictly required, but I find it helpful as annotation. It documents which packages are altered.

Quote:
I couldn't find the option "using the UML packages import mechanism"
Could you help me please.

Ups, that feature is well hidden Wink
Right click on the profile's enntry within the model explorer. Choose "New Child". In the "New Child" dialog choose "Package import".
Open the "Properties" view on the newly created package import. Choose the "Advanced" tab (on the left side of the view's window). Then edit the "Imported Package" to point to the package to be imported.

/Carsten

[Updated on: Sat, 27 August 2016 14:44]

Report message to a moderator

Forum: Model Driven Health Tools
 Topic: A problem in Mac version,Thanks
A problem in Mac version,Thanks [message #1741677] Sat, 27 August 2016 06:32
pans pan is currently offline pans panFriend
Messages: 5
Registered: July 2016
Junior Member
Dear Sean:
I so sorry trouble you again.
I found these files in plugins folder.
In Win version,It is worked.
But in Mac version, It still messaged "Unable to create CDA project, No available CDA document in workspace!"
So what can i do?
thank you for your help.
jun
Re: A problem in Mac version,Thanks [message #1741686 is a reply to message #1741677] Sat, 27 August 2016 12:02
Sean Muir is currently offline Sean MuirFriend
Messages: 11
Registered: September 2015
Junior Member
jun - currently the tooling expects some base projects in the workspace - we have an approach where this will not be necessary but have not finished implementation
use the attached project set file to pull in the projects
The wizard looks for clinical documents to constrain;
thanks
sean
Re: A problem in Mac version,Thanks [message #1741688 is a reply to message #1741686] Sat, 27 August 2016 14:51
pans pan is currently offline pans panFriend
Messages: 5
Registered: July 2016
Junior Member
Dear Sean:
Sorry to trouble you again. Can you help me again? Thanks.
I import projects.
But many errors:
Description Resource Path Location Type
Bundle 'org.openhealthtools.mdht.emf.runtime' cannot be resolved MANIFEST.MF /org.openhealthtools.mdht.uml.cda/META-INF line 25 Plug-in Problem
Bundle 'org.openhealthtools.mdht.uml.term.core' cannot be resolved MANIFEST.MF /org.openhealthtools.mdht.uml.term.models/META-INF line 6 Plug-in Problem
currentNode cannot be resolved to a variable CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 37 Java Problem
declareXSI cannot be resolved to a variable CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 33 Java Problem
doc cannot be resolved CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 35 Java Problem
DOMDocumentHandlerImpl cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 262 Java Problem
DOMDocumentHandlerImpl cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 294 Java Problem
DOMDocumentHandlerImpl cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 326 Java Problem
DOMDocumentHandlerImpl cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 392 Java Problem
DOMElementHandler cannot be resolved CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 40 Java Problem
DOMElementHandler cannot be resolved to a type DataTypeElementHandler.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 25 Java Problem
DOMElementHandler cannot be resolved to a type PartElementHandler.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 24 Java Problem
FACTORY cannot be resolved to a variable AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 70 Java Problem
FleXMLLoadImpl cannot be resolved to a type CDALoadImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 19 Java Problem
FleXMLResource cannot be resolved to a type CDAResource.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 23 Java Problem
FleXMLResource cannot be resolved to a type CDAResource.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 30 Java Problem
FleXMLResource cannot be resolved to a type CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 62 Java Problem
FleXMLResource cannot be resolved to a type CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 73 Java Problem
FleXMLResource cannot be resolved to a type CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 74 Java Problem
FleXMLResource cannot be resolved to a variable CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 262 Java Problem
FleXMLResource cannot be resolved to a variable CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 294 Java Problem
FleXMLResource cannot be resolved to a variable CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 326 Java Problem
FleXMLResource cannot be resolved to a variable CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 392 Java Problem
FleXMLResourceFactoryImpl cannot be resolved to a type CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 36 Java Problem
FleXMLResourceFactoryImpl cannot be resolved to a type CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 74 Java Problem
FleXMLResourceImpl cannot be resolved to a type CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 27 Java Problem
FleXMLResourceSet cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 201 Java Problem
FleXMLResourceSet cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 213 Java Problem
FleXMLResourceSet cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 230 Java Problem
FleXMLResourceSet cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 200 Java Problem
FleXMLResourceSet cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 212 Java Problem
FleXMLResourceSet cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 213 Java Problem
FleXMLResourceSet cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 229 Java Problem
FleXMLResourceSet cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 230 Java Problem
FleXMLSaveImpl cannot be resolved to a type CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 21 Java Problem
Initializer cannot be resolved AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 68 Java Problem
Initializer cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 1012 Java Problem
Initializer cannot be resolved to a type AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 26 Java Problem
Initializer cannot be resolved to a type AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 27 Java Problem
Initializer cannot be resolved to a type AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 67 Java Problem
Initializer cannot be resolved to a type AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 78 Java Problem
Initializer cannot be resolved to a type AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 80 Java Problem
Initializer cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 1012 Java Problem
Initializer cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 1021 Java Problem
Initializer cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 1024 Java Problem
keepDefaults cannot be resolved to a variable CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 28 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved AnnotationBasedInitializer.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 21 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDALoadImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 16 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAResource.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 15 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 21 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 22 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 23 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 24 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 25 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 18 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 18 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 81 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 82 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 83 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 84 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 85 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved CDAXSITypeProvider.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 30 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved DataTypeElementHandler.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 18 Java Problem
The import org.openhealthtools.mdht.emf cannot be resolved PartElementHandler.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 18 Java Problem
The method aboutToLoadDOM(Document) of type new DOMDocumentHandlerImpl(){} must override or implement a supertype method CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 264 Java Problem
The method aboutToLoadDOM(Document) of type new DOMDocumentHandlerImpl(){} must override or implement a supertype method CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 296 Java Problem
The method aboutToLoadDOM(Document) of type new DOMDocumentHandlerImpl(){} must override or implement a supertype method CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 328 Java Problem
The method aboutToLoadDOM(Document) of type new DOMDocumentHandlerImpl(){} must override or implement a supertype method CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 394 Java Problem
The method basicCreateResource(URI) of type CDAResourceFactoryImpl must override or implement a supertype method CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 62 Java Problem
The method createResource(URI) of type CDAResourceFactoryImpl must override or implement a supertype method CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 73 Java Problem
The method createResourceSet() from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 438 Java Problem
The method createResourceSet() from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 522 Java Problem
The method createResourceSet() from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 578 Java Problem
The method createResourceSet(EClass) from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 252 Java Problem
The method createResourceSet(EClass) from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 284 Java Problem
The method createResourceSet(EClass) from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 316 Java Problem
The method createResourceSet(EClass) from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 348 Java Problem
The method createResourceSet(EClass) from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 360 Java Problem
The method createResourceSet(EClass) from the type CDAUtil refers to the missing type FleXMLResourceSet CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 374 Java Problem
The method createResourceSet(String) from the type CDAUtil refers to the missing type FleXMLResourceSet Validate.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/validate line 108 Java Problem
The method createXMLHelper() is undefined for the type CDAResourceImpl CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 42 Java Problem
The method createXMLHelper() is undefined for the type CDAResourceImpl CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 47 Java Problem
The method createXMLLoad() of type CDAResourceImpl must override or implement a supertype method CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 41 Java Problem
The method createXMLSave() of type CDAResourceImpl must override or implement a supertype method CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 46 Java Problem
The method put(String, Resource.Factory) in the type Map<String,Resource.Factory> is not applicable for the arguments (String, CDAResourceFactoryImpl) CDAXMLProcessor.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 50 Java Problem
The method put(String, Resource.Factory) in the type Map<String,Resource.Factory> is not applicable for the arguments (String, CDAResourceFactoryImpl) CDAXMLProcessor.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 51 Java Problem
The method saveTypeAttribute(EClass) of type CDASaveImpl must override or implement a supertype method CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 32 Java Problem
The method shouldSaveFeature(EObject, EStructuralFeature) of type CDASaveImpl must override or implement a supertype method CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 27 Java Problem
The method shouldThrow(Exception) of type CDALoadImpl must override or implement a supertype method CDALoadImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 25 Java Problem
toDOM cannot be resolved to a variable CDASaveImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 34 Java Problem
Type mismatch: cannot convert from CDALoadImpl to XMLLoadImpl CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 42 Java Problem
Type mismatch: cannot convert from CDASaveImpl to XMLSaveImpl CDAResourceImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 47 Java Problem
XSITypeHandler cannot be resolved to a type CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 42 Java Problem
XSITypeProvider cannot be resolved CDAResourceFactoryImpl.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/internal/resource line 44 Java Problem
XSITypeProvider cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 141 Java Problem
XSITypeProvider cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 160 Java Problem
XSITypeProvider cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 176 Java Problem
XSITypeProvider cannot be resolved CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 188 Java Problem
XSITypeProvider cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 141 Java Problem
XSITypeProvider cannot be resolved to a type CDAUtil.java /org.openhealthtools.mdht.uml.cda/src/org/openhealthtools/mdht/uml/cda/util line 160 Java Problem
There is no 'javacSource' build entry and the project has Java compliance preferences set build.properties /org.openhealthtools.mdht.uml.hl7.datatypes line 1 Plug-in Problem
There is no 'javacSource' build entry and the project has Java compliance preferences set build.properties /org.openhealthtools.mdht.uml.hl7.rim line 1 Plug-in Problem
There is no 'javacSource' build entry and the project has Java compliance preferences set build.properties /org.openhealthtools.mdht.uml.hl7.vocab line 1 Plug-in Problem
Unused import: csv helloworld.py /test_python/src line 4 PyDev Problem
Unused import: math helloworld.py /test_python/src line 4 PyDev Problem
Unused import: string helloworld.py /test_python/src line 4 PyDev Problem
Unused import: sys helloworld.py /test_python/src line 4 PyDev Problem
Forum: C / C++ IDE (CDT)
 Topic: MSP430GCC (XPG) Problem
MSP430GCC (XPG) Problem [message #1741685] Sat, 27 August 2016 11:46
Robert Ty is currently offline Robert TyFriend
Messages: 9
Registered: June 2012
Junior Member
Hi,

I'm using MSP430GCC (XPG plugin) with Kepler without problems.Everything is
ok.

Now I switched to Neon. I tried to transfer one of my MSP430 projects , just
to see if it works with Neon.

Unfortunately I run into a problem. The MSP430 target HW selection window is empty.
Even if I try to generate a new project, same thing. Refer to picture.

It's possibly a problem of my personal settings and has nothing to do with Neon.

Can anybody help please?

Thank you.

Regards

Robert

[Updated on: Sat, 27 August 2016 11:48]

Report message to a moderator

 Topic: MSVC++ unwanted includes in Project Explorer
MSVC++ unwanted includes in Project Explorer [message #1741690] Sat, 27 August 2016 17:13
Vladimir Grishchenko is currently online Vladimir GrishchenkoFriend
Messages: 85
Registered: July 2009
Member
I'm experimenting with MSVC++ toolchain and CDT 8.8.1 on Mars and it seems that out of the box it assumes Visual Studio 2012. I have both 2012 and 2013 but I want to use the latter with the CDT internal builder. I think I got most of it working, first I modified the INCLUDE, LIB, and PATH variables under Environment in the project properties so that 2013 compiler and linker are invoked, and I then added 2013 include folders under Paths and Symbols. One last piece of the puzzle is how to get rid of the default 2012 entries under Includes, as they do show up in the Project Explorer which is confusing. They seem to be hard-coded in the toolchain and sticky. As far as I can tell this is just a cosmetic issue as both the indexer and the compiler are now using 2013 includes and libraries, but it is annoying nonetheless. Is there an easy way to fix it?

PS: Also GNU C/C++ names don't make whole lot of sense when MSVC++ toolchain is selected, but I get it.

index.php/fa/26898/0/
index.php/fa/26899/0/

[Updated on: Sat, 27 August 2016 17:14]

Report message to a moderator




Current Time: Sat Aug 27 17:14:45 GMT 2016

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

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