Re: External libraries in the bootclasspath (was: Version Conflict with bcel?)

2006-04-13 Thread Ilya Neverov
Hi, I think we can follow standardized way in this case. On 4/11/06, Stepan Mishura <[EMAIL PROTECTED]> wrote: > There are no other opinions but I believe this issue needs broader attention > so I'd like to start another thread. > > Harmony has a number of external libraries on the bootclasspath

Re: External libraries in the bootclasspath (was: Version Conflict with bcel?)

2006-04-12 Thread Mikhail Loenko
Actually I cannot right now estimate performance impact, so we might want to find another solution Thanks, Mikhail 2006/4/12, Soeren Strassfeld <[EMAIL PROTECTED]>: > > > We can load those libraries by a dedicated class loader so that they > > will be invisible for apps but visible for our 'bridg

Re: External libraries in the bootclasspath (was: Version Conflict with bcel?)

2006-04-11 Thread Soeren Strassfeld
We can load those libraries by a dedicated class loader so that they will be invisible for apps but visible for our 'bridge' classes Thanks, Mikhail Hi, So you are able to run two different versions of one class within the one jvm instance? This is cool, and of course much more elegant tha

Re: External libraries in the bootclasspath (was: Version Conflict with bcel?)

2006-04-11 Thread Mikhail Loenko
We can load those libraries by a dedicated class loader so that they will be invisible for apps but visible for our 'bridge' classes Thanks, Mikhail 2006/4/11, Stepan Mishura <[EMAIL PROTECTED]>: > There are no other opinions but I believe this issue needs broader attention > so I'd like to start

External libraries in the bootclasspath (was: Version Conflict with bcel?)

2006-04-11 Thread Stepan Mishura
There are no other opinions but I believe this issue needs broader attention so I'd like to start another thread. Harmony has a number of external libraries on the bootclasspath: ICU4C, Xerces/Xalan. What if an app. uses the same library but another version? What if library versions are not compat

Re: Version Conflict with bcel?

2006-04-10 Thread Soeren Strassfeld
On 4/10/06 Stepan Mishura wrote: On 4/9/06, Soeren Strassfeld wrote: > > Hi Stepan, > > first, I did a simple xsl Transformation: > > TransformerFactory f = TransformerFactory.newInstance(); > Transformer t = f.newTransformer(new StreamSource(new > FileInputStream("foo.xsl"))); > t.transform(new

Re: Version Conflict with bcel?

2006-04-09 Thread Stepan Mishura
On 4/9/06, Soeren Strassfeld wrote: > > Hi Stepan, > > first, I did a simple xsl Transformation: > > TransformerFactory f = TransformerFactory.newInstance(); > Transformer t = f.newTransformer(new StreamSource(new > FileInputStream("foo.xsl"))); > t.transform(new StreamSource(new FileInputStream("f

Re: Version Conflict with bcel?

2006-04-09 Thread Stepan Mishura
On 4/9/06, Soeren Strassfeld wrote: > > > Hi Stepan, > > works fine, thanks! > > Anyway, overriding the bootclasspath seems very dangerous to me, as > not all libraries keep upward/downward compatibility. Hi, Soeren, I agree with you that it would be better to use appropriate xalan library. But

Re: Version Conflict with bcel?

2006-04-09 Thread Soeren Strassfeld
Hi Stepan, first, I did a simple xsl Transformation: TransformerFactory f = TransformerFactory.newInstance(); Transformer t = f.newTransformer(new StreamSource(new FileInputStream("foo.xsl"))); t.transform(new StreamSource(new FileInputStream("foo.xml")),new StreamResult(System.out)); (foo.x

Re: Version Conflict with bcel?

2006-04-08 Thread Soeren Strassfeld
Hi Stepan, works fine, thanks! Anyway, overriding the bootclasspath seems very dangerous to me, as not all libraries keep upward/downward compatibility. Could be interesting to see how the xml api behaves with a new bcel in the bootclasspath, will do some tests on that! Thanks, Soeren Stepa

Re: Version Conflict with bcel?

2006-04-08 Thread Stepan Mishura
On 4/8/06, Soeren Strassfeld wrote: > > Hi List, > > the latest Harmony snapshot ships a version of xalan.jar, which seems to > contains > an old version of Jakarta bcel. > When I try to run my bcel based App, I get a NoSuchMethodError: > > org/apache/bcel/Repository.lookupClass(Ljava/lang/Class;)L

Version Conflict with bcel?

2006-04-08 Thread Soeren Strassfeld
Hi List, the latest Harmony snapshot ships a version of xalan.jar, which seems to contains an old version of Jakarta bcel. When I try to run my bcel based App, I get a NoSuchMethodError: org/apache/bcel/Repository.lookupClass(Ljava/lang/Class;)Lorg/apache/bcel/classfile/JavaClass; I checked