On 1/19/07, Adam Lally (JIRA) <[email protected]> wrote:
[ https://issues.apache.org/jira/browse/UIMA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466072] Adam Lally commented on UIMA-193: --------------------------------- Lev, The patch fixes testUTF8WithSignature. However, testUTF16NoSignature is failing! Intrestingly, testUTF16WithSignature has never had any problem, even before your patch. What's going on? At first I thought that the test files might just be swapped (so that the test named "NoSignature" was actually using the file that did have a signature, and vice versa). But I checked and the test files seem OK. So what's going on? Did you try this test case with Sun Java 1.4, and did it work for you?
I tried all the test with both Sun's Java 1.4.2 and 1.5.0 - everything works fine for me after fixing the initial problem in testUTF8WithSignature and testUTF16WithSignature (with current patch). However, I would like to modify the patch a little bit to make sure it will work with all future releases of Sun's Java. -- Lev
PEAR Encoding Test gives NullPointerException under Sun Java 1.4.2 > ------------------------------------------------------------------ > > Key: UIMA-193 > URL: https://issues.apache.org/jira/browse/UIMA-193 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework > Environment: Sun Java 1.4.2_12 > Reporter: Adam Lally > Assigned To: Adam Lally > Fix For: 2.1 > > Attachments: PearEncodingTest.patch > > > java.lang.NullPointerException > at org.apache.uima.pear.util.PearEncodingTest.testUTF8WithSignature( PearEncodingTest.java:54) > 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:324) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run( JUnit3TestReference.java:128) > 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
