🚀 go-pugleaf

With JDK 1.2.2  JBuilder 3.5

java.util.Hashtable h     = (java.util.Hashtable) v.firstElement();
java.util.Enumeration e = h.keys();
java.util.Collection c    = h.values();
java.util.Iterator i         = c.iterator();
myFunctionId(new Long(i.next().toString()));

Correction I used when upgrading to JBuilder4 JDK 1.3
java.util.Hashtable h     = (java.util.Hashtable) v.firstElement();
java.util.Enumeration e = h.keys();
java.util.Collection c     = h.values();
java.util.Iterator i          = c.iterator();
String iString                = i.next().toString();
// So I won't skip an iteration while degugging.. copy per se
writeLogEvent("iString is = to " + iString, ERROR);                  // Just
a log file so I can view what's going on
writeLogEvent("iString length is " + iString.length(), ERROR);   // Walla !!
This returns my Id of '0' + 5 whitespaces --  length = 6
myFunctionId(new Long(iString.trim()));                                  //
Use trim() to get rid of whitespaces and continue

I don't understand where the whitespace is coming from.

"Torsten Welches" <torsten.welches@who.cares.netcologne.de> wrote in message
news:3aa72d40$1_2@dnews...
>
> Daniel,
>
> I'm not sure if I understand your problem. *Where* is whitespace
> involved? Are you using something like "new Long("10 34");"?
> And what "length" are you referring to?
> Can you post some code?
>
> Torsten
>
> "Daniel Ray" <dray@inphact.com> wrote:
> >I have an application that I have been using new Long throughout my
> >application built with JBuilder 3.5 and JDK 1.2.2
> >I upgraded my JBuilder to v4. Everything compiles fine. Now the errors
show
> >up. I've noticed that where I use Long..and then
> >get its length...it contains extra whitespaces. I now have to use the
trim()
> >function to fix this. I'm not complaining, just want to
> >know if this is something new with the way Long is handled in 1.3
>