Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Texo/Troubleshooting

< Texo
Revision as of 15:30, 27 May 2010 by Mtaal.springsite.com (Talk | contribs) (New page: __TOC__ == Class not managed by this ModelResolver == You encounter an issue like this when making use of Texo runtime functionality: <source lang="java"> org.eclipse.emf.texo.Library is ...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Class not managed by this ModelResolver

You encounter an issue like this when making use of Texo runtime functionality:

org.eclipse.emf.texo.Library is not managed by this ModelResolver
    at org.eclipse.emf.texo.utils.Check.isNotNull(Check.java:66)
    at
org.eclipse.emf.texo.model.ModelResolver.getModelDescriptor(ModelResolver.java:263)
    at
org.eclipse.emf.texo.model.ModelResolver.getModelObject(ModelResolver.java:208)
    at
org.eclipse.emf.texo.xml.ModelEMFConverter.createTarget(ModelEMFConverter.java:134)
    at
org.eclipse.emf.texo.xml.ModelEMFConverter.convert(ModelEMFConverter.java:86)
    at org.eclipse.emf.texo.xml.ModelXMLSaver.write(ModelXMLSaver.java:72)

To solve this: when you make use of certain parts of Texo at runtime you need to be sure that you have 'touched' the generated ModelPackage classes in your code somewhere. A generated ModelPackage automatically initializes itself when you refer to it in your code (see the generated INSTANCE static member).

Back to the top