Closed istvanrath closed 11 years ago
More specifically, the issue can be reproduced with https://github.com/ujhelyiz/EMF-IncQuery-Examples/blob/master/bodymodel/bodymodel.incquery/src/bodymodel/ymca/ymca.eiq, query handsAreClose_buggy
I can reproduce the issue. I even tried it with another domain, and get the same error. I tried to use the emf objects in the java method's body and it worked well, I only get the error, if I use them as attributes in the java method. As the processing of the attributes for the interpreter is our code, the bug is likely to be ours, so I'll continue working on it.
2012/10/1 Istvan Rath notifications@github.com
More specifically, the issue can be reproduced with https://github.com/ujhelyiz/EMF-IncQuery-Examples/blob/master/bodymodel/bodymodel.incquery/src/bodymodel/ymca/ymca.eiq, query handsAreClose_buggy
— Reply to this email directly or view it on GitHubhttps://github.com/ujhelyiz/EMF-IncQuery/issues/312#issuecomment-9027207.
Actually the attribute is correctly encapsulated in a context object for the xbase. It seems that the interpreter does not use the given classloader when it handles these attributes.
2012/10/1 András Ökrös okrosa@gmail.com
I can reproduce the issue. I even tried it with another domain, and get the same error. I tried to use the emf objects in the java method's body and it worked well, I only get the error, if I use them as attributes in the java method. As the processing of the attributes for the interpreter is our code, the bug is likely to be ours, so I'll continue working on it.
2012/10/1 Istvan Rath notifications@github.com
More specifically, the issue can be reproduced with https://github.com/ujhelyiz/EMF-IncQuery-Examples/blob/master/bodymodel/bodymodel.incquery/src/bodymodel/ymca/ymca.eiq, query handsAreClose_buggy
— Reply to this email directly or view it on GitHubhttps://github.com/ujhelyiz/EMF-IncQuery/issues/312#issuecomment-9027207.
The error originates from the XbaseInterpreter's following method: protected Object invokeOperation(JvmOperation operation, Object receiver, List
2012/10/1 András Ökrös okrosa@gmail.com
Actually the attribute is correctly encapsulated in a context object for the xbase. It seems that the interpreter does not use the given classloader when it handles these attributes.
2012/10/1 András Ökrös okrosa@gmail.com
I can reproduce the issue. I even tried it with another domain, and get the same error. I tried to use the emf objects in the java method's body and it worked well, I only get the error, if I use them as attributes in the java method. As the processing of the attributes for the interpreter is our code, the bug is likely to be ours, so I'll continue working on it.
2012/10/1 Istvan Rath notifications@github.com
More specifically, the issue can be reproduced with https://github.com/ujhelyiz/EMF-IncQuery-Examples/blob/master/bodymodel/bodymodel.incquery/src/bodymodel/ymca/ymca.eiq, query handsAreClose_buggy
— Reply to this email directly or view it on GitHubhttps://github.com/ujhelyiz/EMF-IncQuery/issues/312#issuecomment-9027207.
What is the problem with reflection? Based on the error message (" ... on instance:null"), I suspect that some object is not being passed where it should be.
Most of it seems right, the attribute value is the correct emf object implementation as it should be. I came up with one more idea during lunch, I'll try it out now.
2012/10/2 Istvan Rath notifications@github.com
What is the problem with reflection? Based on the error message (" ... on instance:null"), I suspect that some object is not being passed where it should be.
— Reply to this email directly or view it on GitHubhttps://github.com/ujhelyiz/EMF-IncQuery/issues/312#issuecomment-9065999.
The fix of the #346 issue should fix this as well. The bug is still present in the system, but should be unreachable. I set this issue to resolved now.
Closing.
I have noticed that the evaluation of check() expressions can have problems in interpreted mode. For instance, the
stretchedArm
pattern from https://github.com/ujhelyiz/EMF-IncQuery-Examples/blob/master/bodymodel/bodymodel.incquery/src/bodymodel/ymca/ymca.eiq throws the following exception in interpreted mode (while it works flawlessly in generated mode):