You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by WAS Online <wa...@ndrmobil.de> on 2000/09/20 10:48:11 UTC
build.xml in latest cvs update (20-09-2000)
hi there,
i have noticed the change in the latest build.xml that the .jar files
are now supposed to be part of the .war deployment file. (as it is
meant to be in the j2ee specification).
Since then I really was not able to get cocoon to work again... I really
feel kind of dump.
please tell me it is not my fault. the error message i get is:
org.apache.cocoon.components.language.LanguageException: Error
compiling _sitemap_xmap:
Line 0, column 0:
/usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_webapps/_cocoon/_sitemap_xmap.java:11:
Class org.apache.avalon.Configurable not found in import.
import org.apache.avalon.Configurable;
^
Line 0, column 0:
/usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_webapps/_cocoon/_sitemap_xmap.java:12:
Class org.apache.avalon.Configuration not found in import.
import org.apache.avalon.Configuration;
^
Line 0, column 0:
/usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_webapps/_cocoon/_sitemap_xmap.java:13:
Class org.apache.avalon.ConfigurationException not found in import.
import org.apache.avalon.ConfigurationException;
^
Line 0, column 0:
/usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_webapps/_cocoon/_sitemap_xmap.java:14:
Class org.apache.avalon.SAXConfigurationBuilder not found in import.
import org.apache.avalon.SAXConfigurationBuilder;
[...] a.s.o
i am pretty sure i have that avalon thing and everything else in the
tomcat classpath.
thanks,
jakob
Re: re build.xml in latest cvs update (20-09-2000)@1
Posted by Stefano Mazzocchi <st...@apache.org>.
Sebastien Sahuc wrote:
>
> Stefano Mazzocchi wrote :
>
> > Sebastien Sahuc wrote:
> > >
> > > WAS Online wrote :
> > >
> > > > Since then I really was not able to get cocoon to work again... I
> > really
> > > > feel kind of dump.
> > > > please tell me it is not my fault. the error message i get is:
> > >
> > > Not your fault, don't worry 'WAS Online' :-)
> > >
> > > > org.apache.cocoon.components.language.LanguageException: Error
> > > > compiling _sitemap_xmap:
> > > > Line 0, column 0:
> > > >
> > /usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_weba
> > > > pps/_cocoon/_sitemap_xmap.java:11:
> > > > Class org.apache.avalon.Configurable not found in import.
> > > > import org.apache.avalon.Configurable;
> > > > ^
> > >
> > > > i am pretty sure i have that avalon thing and everything else in the
> > > > tomcat classpath.
> > >
> > > Indeed, I believe the lastest change for making the perfect catalina
> > > integration broke something into the Engine :
> > >
> > > in the JavaLanguage it used to set the compiler classpath with the
> > System
> > > classpath (throught System.getProperty("java.class.path") ) whereas in
> > > the last version, it takes the classpath from the property set by the
> > > Servlet.init which in most case is null (when not used behind
> > Catalina,
> > > or when using the command line option).
> > >
> > > It would be easy to fix it by adding the System classpath, but I
> > believe
> > > that Stephano has removed this on purpose and I do understand him (you
> > > should not use the system classpath since you're in a servlet engine
> > > environment). The problem then arises with the command line option and
> > > when the Servlet container deals with more ClassLoader issues ( I know
> > > some Servlet container that might not be flexible enough to permits
> > the
> > > nice drag and drop feature of the whole cocoon war :-( )
>
> > Exactly, for now C2 works ONLY with Tomcat 4.0-dev (aka catalina).
>
> > The problem is there is no easy way to fix this due to compiler problems
> > with classloaders :/
>
> > yes servlet containers mostly suck on classloading issues, but for now
> > there is not much I can do (maybe allow JavaLanguage to use the system
> > classpath instead? any suggestion?)
>
> Why not get the classpath property from catalina, and if not present, get
> the system classpath from Ssytem.getProperty. So that in either case
> you'll get a classpath that should fit cocoon's need.
>
> The problem isn't resolved, faqr from it, but at least it would work with
> Catalina and other servlet engine by setting the system classpath
> correctly.
Ok, will do this, sounds ok.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
Re: re build.xml in latest cvs update (20-09-2000)@1
Posted by Sebastien Sahuc <ss...@imediation.com>.
Stefano Mazzocchi wrote :
> Sebastien Sahuc wrote:
> >
> > WAS Online wrote :
> >
> > > Since then I really was not able to get cocoon to work again... I
> really
> > > feel kind of dump.
> > > please tell me it is not my fault. the error message i get is:
> >
> > Not your fault, don't worry 'WAS Online' :-)
> >
> > > org.apache.cocoon.components.language.LanguageException: Error
> > > compiling _sitemap_xmap:
> > > Line 0, column 0:
> > >
> /usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_weba
> > > pps/_cocoon/_sitemap_xmap.java:11:
> > > Class org.apache.avalon.Configurable not found in import.
> > > import org.apache.avalon.Configurable;
> > > ^
> >
> > > i am pretty sure i have that avalon thing and everything else in the
> > > tomcat classpath.
> >
> > Indeed, I believe the lastest change for making the perfect catalina
> > integration broke something into the Engine :
> >
> > in the JavaLanguage it used to set the compiler classpath with the
> System
> > classpath (throught System.getProperty("java.class.path") ) whereas in
> > the last version, it takes the classpath from the property set by the
> > Servlet.init which in most case is null (when not used behind
> Catalina,
> > or when using the command line option).
> >
> > It would be easy to fix it by adding the System classpath, but I
> believe
> > that Stephano has removed this on purpose and I do understand him (you
> > should not use the system classpath since you're in a servlet engine
> > environment). The problem then arises with the command line option and
> > when the Servlet container deals with more ClassLoader issues ( I know
> > some Servlet container that might not be flexible enough to permits
> the
> > nice drag and drop feature of the whole cocoon war :-( )
> Exactly, for now C2 works ONLY with Tomcat 4.0-dev (aka catalina).
> The problem is there is no easy way to fix this due to compiler problems
> with classloaders :/
> yes servlet containers mostly suck on classloading issues, but for now
> there is not much I can do (maybe allow JavaLanguage to use the system
> classpath instead? any suggestion?)
Why not get the classpath property from catalina, and if not present, get
the system classpath from Ssytem.getProperty. So that in either case
you'll get a classpath that should fit cocoon's need.
The problem isn't resolved, faqr from it, but at least it would work with
Catalina and other servlet engine by setting the system classpath
correctly.
> [btw, my name is Stefano :)]
I knew that i'll fall in the trap !!! I saw from previous post that it's
not the first time someone is misspelling your name (both first name and
last name), and I thought I will never write your name in order not to
get it wrong, but I failed :-) Sorry again.
All the best,
Sebastien
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
> Missed us in Orlando? Make it up with ApacheCON Europe in London!
> ------------------------- http://ApacheCon.Com ---------------------
Re: build.xml in latest cvs update (20-09-2000)
Posted by Stefano Mazzocchi <st...@apache.org>.
Sebastien Sahuc wrote:
>
> WAS Online wrote :
>
> > Since then I really was not able to get cocoon to work again... I really
> > feel kind of dump.
> > please tell me it is not my fault. the error message i get is:
>
> Not your fault, don't worry 'WAS Online' :-)
>
> > org.apache.cocoon.components.language.LanguageException: Error
> > compiling _sitemap_xmap:
> > Line 0, column 0:
> > /usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_weba
> > pps/_cocoon/_sitemap_xmap.java:11:
> > Class org.apache.avalon.Configurable not found in import.
> > import org.apache.avalon.Configurable;
> > ^
>
> > i am pretty sure i have that avalon thing and everything else in the
> > tomcat classpath.
>
> Indeed, I believe the lastest change for making the perfect catalina
> integration broke something into the Engine :
>
> in the JavaLanguage it used to set the compiler classpath with the System
> classpath (throught System.getProperty("java.class.path") ) whereas in
> the last version, it takes the classpath from the property set by the
> Servlet.init which in most case is null (when not used behind Catalina,
> or when using the command line option).
>
> It would be easy to fix it by adding the System classpath, but I believe
> that Stephano has removed this on purpose and I do understand him (you
> should not use the system classpath since you're in a servlet engine
> environment). The problem then arises with the command line option and
> when the Servlet container deals with more ClassLoader issues ( I know
> some Servlet container that might not be flexible enough to permits the
> nice drag and drop feature of the whole cocoon war :-( )
Exactly, for now C2 works ONLY with Tomcat 4.0-dev (aka catalina).
The problem is there is no easy way to fix this due to compiler problems
with classloaders :/
yes servlet containers mostly suck on classloading issues, but for now
there is not much I can do (maybe allow JavaLanguage to use the system
classpath instead? any suggestion?)
[btw, my name is Stefano :)]
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
Re: build.xml in latest cvs update (20-09-2000)
Posted by Sebastien Sahuc <ss...@imediation.com>.
WAS Online wrote :
> Since then I really was not able to get cocoon to work again... I really
> feel kind of dump.
> please tell me it is not my fault. the error message i get is:
Not your fault, don't worry 'WAS Online' :-)
> org.apache.cocoon.components.language.LanguageException: Error
> compiling _sitemap_xmap:
> Line 0, column 0:
> /usr/local/tomcat/work/localhost_8080%2Fcocoon/_usr/_local/_tomcat/_weba
> pps/_cocoon/_sitemap_xmap.java:11:
> Class org.apache.avalon.Configurable not found in import.
> import org.apache.avalon.Configurable;
> ^
> i am pretty sure i have that avalon thing and everything else in the
> tomcat classpath.
Indeed, I believe the lastest change for making the perfect catalina
integration broke something into the Engine :
in the JavaLanguage it used to set the compiler classpath with the System
classpath (throught System.getProperty("java.class.path") ) whereas in
the last version, it takes the classpath from the property set by the
Servlet.init which in most case is null (when not used behind Catalina,
or when using the command line option).
It would be easy to fix it by adding the System classpath, but I believe
that Stephano has removed this on purpose and I do understand him (you
should not use the system classpath since you're in a servlet engine
environment). The problem then arises with the command line option and
when the Servlet container deals with more ClassLoader issues ( I know
some Servlet container that might not be flexible enough to permits the
nice drag and drop feature of the whole cocoon war :-( )
Sebastien
> thanks,
> jakob