[otj-users] Strange problem in very simple example / track id 137

[Olaf Otto]

Hi Stephan!

I supplied the arguments you suggested to the vm-args section of the 
junit run configuration in eclipse,
but the problem persists.

To make sure there was no misunderstanding, here is the stacktrace and 
the parameters i used.

btw: I would be interested in running ot-applications on the command 
line - how could that be achieved?

Kind regards,
Olaf


------- begin trace ---------

java.lang.NoSuchMethodError: 
de.tuberlin.cs.olafmdaa.otj.jpa.Person.getde$tuberlin$cs$olafmdaa$otj$jpa$Family_OT$Tag()S
    at 
de.tuberlin.cs.olafmdaa.otj.jpa.Family._OT$liftTo$Parent(Family.java:13)
    at de.tuberlin.cs.olafmdaa.otj.jpa.Family.setParent(Family.java:22)
    at 
de.tuberlin.cs.olafmdaa.otj.jpa.OtPersistenceTest.test(OtPersistenceTest.java:11)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59)
    at 
org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98)
    at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79)
    at 
org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87)
    at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77)
    at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42)
    at 
org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88)
    at 
org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
    at 
org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
    at 
org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
    at 
org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
    at 
org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
    at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
    at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
    at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
    at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
    at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

------------- / end trace ------------


-Dosgi.framework.extensions=org.objectteams.eclipse.transformer.hook
-Dosgi.hook.configurators.include=org.objectteams.eclipse.transformer.hook.HookConfigurator
-Dot.equinox=1
-Dosgi.classloader.lock=classname


>   


Stephan Herrmann wrote:

> Hi,
>
>
>   
>>> I have written  a very simple team, role, baseclass and testcase (pasted
>>> at the bottom of the message), which fails with the following exception:
>>>       
>
>   
>> this seems to be a technical, JUnit-related problem. Running your test()
>> method as regular main-method works fine.
>>     
>
> I just now see that we currently don't ship the OTDT with the support for
> JUnit which we actually have. For the time being, could you please try running
> the test with the following vmargs:
>   -Dosgi.framework.extensions=org.objectteams.eclipse.transformer.hook
>   -Dosgi.hook.configurators.include=org.objectteams.eclipse.transformer.hook.HookConfigurator
>   -Dot.equinox=1
>   -Dosgi.classloader.lock=classname
> This should enable the byte code weaving required to execute OT/J code.
> Normally, there should of course be a simple means in the UI to achieve the
> same effect without directly specifying such low-level details.
> I just filed http://trac.objectteams.org/ot/ticket/137 for tracking this.
> 	
> best,
> Stephan
>