[kaffe] Character encoder/ClassLoader initialization

2005-01-13 Thread Guilhem Lavaux
Hi, It seems that when we don't use iconv there are some problems in initializing the EncodingManager. CharToByteConverter.getEncoder needs ClassLoader.getSystemResource which needs ClassLoader.staticData. However staticData is not yet initialized because getEncoder is called while

Re: [kaffe] Character encoder/ClassLoader initialization

2005-01-13 Thread Dalibor Topic
Guilhem Lavaux wrote: Salut Guilhem, hallo Helmer, The initialization loop can be broken either: * by getting rid of AppClassLoader which is the source of the loop: it uses URLClassLoader. I'd say let's go for that one. Then kaffe.lang.PrimordialClassLoader can go as well [1], I guess. cheers,

Re: [kaffe] Character encoder/ClassLoader initialization

2005-01-13 Thread Helmer Krämer
Guilhem Lavaux [EMAIL PROTECTED] wrote: Hey, It seems that when we don't use iconv there are some problems in initializing the EncodingManager. CharToByteConverter.getEncoder needs ClassLoader.getSystemResource which needs ClassLoader.staticData. However staticData is not yet initialized

Re: [kaffe] Character encoder/ClassLoader initialization

2005-01-13 Thread Dalibor Topic
Helmer Krämer wrote: Guilhem Lavaux [EMAIL PROTECTED] wrote: It seems that when we don't use iconv there are some problems in initializing the EncodingManager. CharToByteConverter.getEncoder needs ClassLoader.getSystemResource which needs ClassLoader.staticData. However staticData is not yet