Mailing-List: contact poi-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Users List" <poi-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Fri, 12 Jan 2007 13:01:25 -0500
From: "Andrew J. Miller" <ajmiller@fstrf.org>
Subject: WARN. Unread -1 bytes of record 0x7d
To: POI Users List <poi-user@jakarta.apache.org>
Message-id: <45A7CCF5.6000500@fstrf.org>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)

This is more of a request/suggestion than a bug report... 

The same files that caused the "Worksheet/WORKSHEET" issue a month or 
two ago (excel files generated by Crystal Reports) also have a bad habit 
or triggering this println on line 98 of 
org.apache.poi.hssf.record.RecordInputStream.java (a hundred or so times 
for the file I am using)...  Simply opening the file in excel and 
re-saving it prevents the issue from returning.  The same can be said 
for files that are modified by POI and saved, the warning goes away...  
AFAIK, nothing happens outside of one or multiple warnings being printed 
to the console.  The file is still processed and nothing breaks...

Outside of the obvious explanation (like "it prints because the booleans 
are true"), does anyone know why this warning is being thrown?  What 
does it mean and what can a casual POI user like myself do with a file 
that has a negative amount of unread bytes after the 125th record?  Can 
it be changed to use a logger allowing control of what is printed to a 
console?

I should probably mention that I am using POI 3.0 alpha3 and not the 2.5 
release so this just may be a "feature" of the alpha release...
Andy

---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
Mailing List:     http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta Poi Project:  http://jakarta.apache.org/poi/