This page contains archived (old) FAQ entries which are no longer relevant to the current EMF version.
For the latest, see EMF FAQ.
- EMF documentation, EMF Wiki Category
- EMF Query FAQ, EMF Validation FAQ, EMF Transaction FAQ
- XSD FAQ
- GMF FAQ
I want to use EMF, SDO, or XSD 2.1.x in my standalone project, or include only a working subset of the code. What libraries (jar files) do I need in my CLASSPATH?
Eclipse Modeling Framework (EMF) provides the infrastructure to run the generated models and
dynamic model based on existing ecore files.
It also provides XMI/XML serialization and deserialization.
The following jars can be used in standalone mode. Jars are found under the plugins directory of your Eclipse installation - there will be a release number appended to the plugin name, e.g. org.eclipse.emf.common_2.1.0.
Add to the following jars to your CLASSPATH or copy them into your project. This includes, but is not limited to:
- org.eclipse.emf.common/runtime/common.resources.jar (needed at runtime, not at compile time)
- org.eclipse.emf.ecore/runtime/ecore.resources.jar (needed at runtime, not at compile time)
- org.eclipse.emf.ecore.xmi/runtime/ecore.xmi.jar (requires SAX parser - see note below)
Service Data Objects (SDO) is an API specification in the format of Java interfaces and the EMF implementation that requires the EMF jars above and the following jars to be used in standalone mode:
XML Schema Infoset Model (XSD) is a reference library for use with any code that manipulates XML schemas and requires the EMF jars above and the following jars to be used in standalone mode:
- org.eclipse.xsd/runtime/xsd.resources.jar (needed at runtime, not at compile time)
NOTE: If using ecore.xmi or any of the XSD jars, you will require a SAX parser such as
For more information on working outside Eclipse, see the question "How do I use EMF in standalone applications (such as an ordinary main)?".