Re: about TestPersistence && TestFailSave

[Marcel Ruff <ruff at swand.lake.de>]

Cyrille Giquello wrote:

> Hi Marcel,
>
> That's not a big job,
> just a cut & paste from TestFailSave.java to TestPersistence2.java
>
> Perhaps U can give me some idea or guide line to well finish the hack.
> At first I had more stuff, like erasing persistence message between 
stop &
> start to see what xmlBlaster's classes & drivers say,
> but it add confuse for reading the log...
> So, for this version I cut this strange operation. I can put them back,
> depends of what you'll answer...

Thanks for your testcase, i have added it to CVS!

If you have more such nice ideas, we are happy to receive your
contributions.


>
> =======================
>
> Just another things, that should be posted to some java list... It's 
about a
> strange error from the JVM I'm running (java version "1.2.2"
> Classic VM (build JDK-1.2.2_008, green threads, nojit) ).
> I built testsuite and run the test for 3 or 4 times, then I get this 
error,
> with build and with TestRunner.
>
> The log for build.sh testsuite (I don't put log for TestRunner because to
> many lines) :
>
> [mad at zbox xmlBlaster]$ ./build.sh testsuite
> Searching for build.xml ...
> Buildfile: /mnt/hdb1/xmlBlaster/build.xml
>
> prepare:
>
> prepare-src:
>
> xmlBlaster:
> Converting idl...
>      [java] The args attribute is deprecated. Please use nested arg 
elements.
>
>      [copy] Copying 39 files to /mnt/hdb1/xmlBlaster/build/src/xmlBlaster
>     [javac] Compiling 39 source files to 
/mnt/hdb1/xmlBlaster/build/classes
> java.lang.ClassCastException: sun.tools.tree.NullExpression
>         at
> 
sun.tools.javac.BatchEnvironment.setExemptPackages(BatchEnvironment.java:317)
>
>         at
> 
sun.tools.javac.BatchEnvironment.isExemptPackage(BatchEnvironment.java:284)
>         at 
sun.tools.java.Environment.isExemptPackage(Environment.java:73)
>         at 
sun.tools.java.Environment.isExemptPackage(Environment.java:73)
>         at 
sun.tools.java.Environment.isExemptPackage(Environment.java:73)
>         at sun.tools.java.Imports.resolve(Imports.java:132)
>         at sun.tools.javac.SourceClass.basicCheck(SourceClass.java:1079)
>         at
> 
sun.tools.java.ClassDeclaration.getClassDefinition(ClassDeclaration.java:137)
>
>         at sun.tools.javac.Main.compile(Main.java:504)
>         at java.lang.reflect.Method.invoke(Native Method)
>         at
> org.apache.tools.ant.taskdefs.Javac.doClassicCompile(Javac.java:478)
>         at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:332)
>         at org.apache.tools.ant.Target.execute(Target.java:142)
>         at org.apache.tools.ant.Project.runTarget(Project.java:818)
>         at org.apache.tools.ant.Project.executeTarget(Project.java:532)
>         at org.apache.tools.ant.Project.executeTargets(Project.java:506)
>         at org.apache.tools.ant.Main.runBuild(Main.java:420)
>         at org.apache.tools.ant.Main.main(Main.java:149)
>     [javac] error: An exception has occurred in the compiler; please 
file a
> bug report (http://java.sun.com/cgi-bin/bugreport.cgi).
>     [javac] 1 error
>
> BUILD FAILED
>
> /mnt/hdb1/xmlBlaster/build.xml:171: Compile failed, messages should 
have been
> provided.
>
> Total time: 12 seconds

No idea, but JDK 1.2.2 sometimes behaved strange.
I would recommend to change to JDK 1.3.1 or better,
there are many performance improvements as well.

Marcel

--
Marcel Ruff
mailto:ruff at swand.lake.de
http://www.lake.de/home/lake/swand/
http://www.xmlBlaster.org