Skip to content
master
Switch branches/tags
Code

Latest commit

…g.apache.logging.log4j-log4j-core-2.17.1

Bump log4j-core from 2.15.0 to 2.17.1 in /neoemf-core
ad16ac1

Git stats

Files

Permalink
Failed to load latest commit information.

NeoEMF

Build Status CodeCov Codacy Maven Central Javadoc Plugin Licence Javadocs

Check out our wiki for further information on the installation, usages, supported backends, code examples, developer resources, etc.

What Is NeoEMF?

NeoEMF is developed by the Nantes Modeling Group, Naomod. NeoEMF aims at handling large EMF models in an efficient and scalable way.

NeoEMF is a multi-backend framework developed to allow an easy integration of custom backends depending on user needs.

Main Features

NeoEMF comes with some features depending on the backend used:

  • Lazy-loading mechanism: A model is loaded part by part while needed

  • Caching: NeoEMF relies on database caches to retrieve EObjects But in some situation where time performance is important this is not enough and it is possible to use application-level caches to speed up information loading

  • Auto-commit: For the backend having restrictions on transaction sizes it is possible to use the auto-commit feature to split large transaction into several small ones

  • Dirty saving: Handle large models that haven’t been persisted to avoid memory overhead

Why Should I Use NeoEMF?

NeoEMF is fully EMF compliant, that means there is no modification to do to use it with existing EMF based applications.

Additionally, NeoEMF can be plugged with several persistence solutions and is configurable to fit the best your needs (custom caches, in-memory resources, auto-commit,…).

In addition, NeoEMF provides a query API to perform optimized OCL queries over models and reify the results as navigable models.

Usage

Latest Release

The most recent release is NeoEMF 2.0.1, released October 12, 2020. - Javadoc: neoemf - Eclipse Plugin: neoemf

To add a dependency on NeoEMF using Maven, use the following:

<dependencies>
  <dependency>
    <groupId>org.atlanmod.neoemf</groupId>
    <artifactId>neoemf-core</artifactId>
    <version>2.0.1</version>
  </dependency>

  <dependency>
    <groupId>org.atlanmod.neoemf</groupId>
    <artifactId>neoemf-io</artifactId>
    <version>2.0.1</version>
  </dependency>
</dependencies>

Supported Implementations

All native implementations are located under the neoemf-data artifact. To add the dependency of the specific implementation you want to use, simply use:

<dependency>
  <groupId>org.atlanmod.neoemf</groupId>
  <artifactId>neoemf-data-{name}</artifactId>
  <version>2.0.1</version>
</dependency>

Where {name} is any of: * Blueprints: - TinkerGraph : blueprints-core - Neo4j: blueprints-neo4j (requires blueprints-core) * MapDB : mapdb * BerkeleyDB: berkeleydb * HBase: hbase * MongoDB: mongodb (beta)

Snapshots

Snapshots are automatically build from the master and are available through Maven using 2.0.2-SNAPSHOT. - Javadoc: neoemf - Eclipse Plugin: neoemf

Installation

Dedicated pages are available in our wiki for the installation and the build.

Update Site

The simplest way to install NeoEMF is to use the update-site that is available here. Install the NeoEMF Persistence Framework component, which provides NeoEMF core classes and utils. Select the backend specific implementation(s) you want to plug in NeoEMF.

Local Build

You can build locally NeoEMF by following the instructions in the Build section. It is then possible to install NeoEMF from the local built update-site, or by importing the generated plugins.

Benchmarks

A full benchmarks description is available at here.

Issues

If you experience issues installing or using NeoEMF, you can submit an issue on github or contact us at neoemf@googlegroups.com

Known issues:

  • Only Oxygen plugins are fetched (the compatibility is not ensured for previous Eclipse versions)

  • The Eclipse plugins cannot be built if Maven can not access internet (it is needed to fetch Oxygen p2 repositories)

  • Sometimes the plugin build crashes and/or freezes during p2 index fetching from Oxygen repositories. It is generally sufficient to cancel the build (ctrl-c) and to relaunch it.

Credits

Performance problems and memory leaks are diagnosed with Java Profiler