Finding reason for IParser.NullImpl usage [message #716190] |
Tue, 16 August 2011 16:18 |
Christian Pelster Messages: 23 Registered: January 2010 |
Junior Member |
|
|
Hi all,
currently I'm struggeling with a failing mwe2 workflow, the output looks like this:
0 [main] INFO org.eclipse.xpand2.Generator - No meta models configured, using JavaBeans as default.
327265 [main] ERROR mf.mwe2.launch.runtime.Mwe2Launcher - Problems running workflow workflow.MyAdminDslClientGenerator: null
java.lang.RuntimeException: Problems running workflow workflow.MyAdminDslClientGenerator: null
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:99)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:73)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:64)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:55)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Launcher.run(Mwe2Launcher.java:74)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Launcher.main(Mwe2Launcher.java:35)
Caused by: java.lang.NullPointerException
at org.eclipse.xtext.resource.XtextResource.updateInternalState(XtextResource.java:212)
at org.eclipse.xtext.resource.XtextResource.doLoad(XtextResource.java:152)
at org.eclipse.xtext.linking.lazy.LazyLinkingResource.doLoad(LazyLinkingResource.java:69)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1511)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1290)
at org.eclipse.xtext.mwe.Validator.validate(Validator.java:65)
at org.eclipse.xtext.mwe.Reader.invokeInternal(Reader.java:165)
at org.eclipse.emf.mwe.core.lib.AbstractWorkflowComponent.invoke(AbstractWorkflowComponent.java:126)
at org.eclipse.emf.mwe.core.lib.Mwe2Bridge.invoke(Mwe2Bridge.java:34)
at org.eclipse.emf.mwe.core.lib.AbstractWorkflowComponent.invoke(AbstractWorkflowComponent.java:201)
at org.eclipse.emf.mwe2.runtime.workflow.AbstractCompositeWorkflowComponent.invoke(AbstractCompositeWorkflowComponent.java:35)
at org.eclipse.emf.mwe2.runtime.workflow.Workflow.run(Workflow.java:19)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:97)
... 5 more
with debugging I found out that the problem is that for some reason a Parser.NullImpl is used (after a series of successfull Mwe2Parser calls) in XTextResource.doLoad().
I have no idea why suddenly the NullParserImpl is used and where to start to look for the problem, any hints?
Regards,
Pelle
[Updated on: Tue, 16 August 2011 16:20] Report message to a moderator
|
|
|
|
|
|
|
Re: Finding Reason for IParser.NullImpl usage [message #716211 is a reply to message #716207] |
Tue, 16 August 2011 17:05 |
Christian Pelster Messages: 23 Registered: January 2010 |
Junior Member |
|
|
Hi,
one additional hint, maybe it helps, this is the callstack when the NullParserImpl gets injected:
LazyLinkingResource(XtextResource).setInjectedParser(IParser) line: 133
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
SingleMethodInjector$2.invoke(Object, Object...) line: 72
SingleMethodInjector.inject(Errors, InternalContext, Object) line: 91
MembersInjectorImpl<T>.injectMembers(T, Errors, InternalContext) line: 99
ConstructorInjector<T>.construct(Errors, InternalContext, Class<?>) line: 94
ConstructorBindingImpl$Factory<T>.get(Errors, InternalContext, Dependency<?>) line: 111
FactoryProxy<T>.get(Errors, InternalContext, Dependency<?>) line: 56
InjectorImpl$4$1.call(InternalContext) line: 758
InjectorImpl.callInContext(ContextualCallable<T>) line: 804
InjectorImpl$4.get() line: 754
XtextResourceFactory.createResource(URI) line: 19
and the URI at XtextResourceFactory.createResource(URI) line: 19 points to my model file.
Regards,
Pelle
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02911 seconds