cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject RE: build failed on JavaFlow in current CVS HEAD
Date Thu, 29 Apr 2004 09:27:10 GMT
On Thu, 2004-04-29 at 11:21, H.vanderLinden@MI.unimaas.nl wrote:
> Thanks, that solved the problem.
> 
> Why on earth does it make a difference where a jar is located? :-(

Because class loaders are arranged in a hierarchy, a class can only see
classes from his loader or his parent loaders.

I don't know what's the problem in the below scenario though.

> 
> Bye, Helma
> 
> > -----Original Message-----
> > From: Juan Jose Pablos [mailto:cheche@che-che.com] 
> > Sent: Thursday, 29 April 2004 11:15
> > To: dev@cocoon.apache.org
> > Subject: Re: build failed on JavaFlow in current CVS HEAD
> > 
> > 
> > Hi,
> > H.vanderLinden@MI.unimaas.nl escribió:
> > > 
> > D:\cvs\cocoon-2.1\src\blocks\javaflow\java\org\apache\cocoon\component
> > > s\flow
> > > \java\ContinuationClassLoader.java:100: cann
> > > ot resolve symbol
> > > symbol  : method setRepository 
> > (org.apache.bcel.util.ClassLoaderRepository)
> > > location: class org.apache.bcel.Repository
> > >         Repository.setRepository(new ClassLoaderRepository(parent));
> > >                   ^
> > 
> > 
> > Try to move jakarta-bcel-20040329.jar from lib/core to 
> > lib/endorsed and 
> > try to compile again.
> > 
> > Cheers,
> > Cheche
> > 
-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


Mime
View raw message