Hi everyone!
Thanks so much for the replies! For those interested, I finally solved
the problem. I finally was able to figure out that my characters()
method was being called twice. It took me a while to figure this
out...I know some of you are wondering why I did not know that to begin
with but this is code I inheirited from someone else so it was taking me
sometime to figure out what was going on. I did a lot of searching on
the Net and found out some parsing implementations actually call the
characters() method more than once.
This is where I was getting the NumberFormatException. So, at the
beginning of my characters() method, I added the following code:
String elementValue = new String(ch,start,length).trim();
if( elementValue != null && !elementValue.equals("") )
{
//perform my high speed logic!!
}
Thanks again so much for the responses! Each of you definitely helped
get me thinking in the right direction!
Cheers!
Blaine
On Sat, 2002-05-18 at 15:58, David Rosenstrauch wrote:
> At 03:44 PM 5/17/2002 -0700, you wrote:
> >If you still get the exception, I would start looking at those silly little things
>like lowercase "o" and "l" instead of zero and one. I've seen little things like
>this reduce experienced programmers to tears.
> >
> >Not really. But they did get *awfully* frustrated. 8^}
> >
> >Tomm
>
>
> Slightly off-topic, but I ran into this writ large recently. Was merging several
>thousand individual flat files into a single database and kept running into things
>like that - years like "l999" (lower case "l"), "20000" instead of 2000, etc.
>
> It turned a merge task that should have taken 5 minutes into an entire day of data
>scrubbing.
>
> It was horrible! I still have nightmares! :-)
>
>
> DR
>
>
>
> To change your membership options, refer to:
> http://www.sys-con.com/java/list.cfm
To change your membership options, refer to:
http://www.sys-con.com/java/list.cfm
