| --- | --- |
| Bugzilla Link | 289977 |
| Status | NEW |
| Importance | P3 normal |
| Reported | Sep 21, 2009 05:03 EDT |
| Modified | Oct 24, 2009 15:01 EDT |
| Version | 2.0 |
| Reporter | Radomil Dvorak |
Description
The current implementation has done partly job in this direction, supported by org.eclipse.m2m.internal.qvt.oml.runtime.util.OCLEnvironmentWithQVTAccessFactory class,\
which is internal.
The factory class expects a set of Module objects, representing the libraries to access in OCL.\
The user should not have to deal with module loading, also there is no API to achieve this, but\
rather pass set of module URIs. All the complexity of module resolution and loading should be \
done behind the scene.
| --- | --- | | Bugzilla Link | 289977 | | Status | NEW | | Importance | P3 normal | | Reported | Sep 21, 2009 05:03 EDT | | Modified | Oct 24, 2009 15:01 EDT | | Version | 2.0 | | Reporter | Radomil Dvorak |
Description
The current implementation has done partly job in this direction, supported by org.eclipse.m2m.internal.qvt.oml.runtime.util.OCLEnvironmentWithQVTAccessFactory class,\ which is internal.
The factory class expects a set of Module objects, representing the libraries to access in OCL.\ The user should not have to deal with module loading, also there is no API to achieve this, but\ rather pass set of module URIs. All the complexity of module resolution and loading should be \ done behind the scene.
This functionality should be exposed as API.