confusing IToolNativeTypeDelegate policy [message #631051] |
Tue, 05 October 2010 20:07  |
Eclipse User |
|
|
|
The default policy for a programmatically created module [
module = new EolModule();
try {
module.parse(eolSource);
} catch (URISyntaxException e) {
e.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
}
module.getContext().getModelRepository().addModel(emf);
] is to resolve only class path native types. Thus, something like [ http://www.eclipse.org/gmt/epsilon/doc/articles/call-java-fr om-epsilon/] cannot be reproduced. I had to use the following workaround: [
List<IToolNativeTypeDelegate> delegates = module.getContext().getNativeTypeDelegates();
delegates.add(new ExtensionPointToolNativeTypeDelegate());
module.getContext().setNativeTypeDelegates(delegates);
]
It seems there is no reason at all to not include ExtensionPointToolNativeTypeDelegate() by default.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03158 seconds