Ivan Rubin Ayma wrote:
> Vadim,
>
> So the problem should be my environment, which is not the best, but is
> simple.
> I'm using JBuilder to run Tomcat and Cocoon with jars.
> I've included on the project all the tomcat jars and the
> web-apps/cocoon/WEB-INF/lib/*.jar, where the avalon framework is
> located.
>
> I think the compilation of my component can't be the cause. I'm
> compiling it with JBuilder's compiler.
I would not recommend that. JBuilder's compiler has native hooks for its debugger.
Unfortunately, the binaries it has produced or run from its JVM have been
known to be flaky. (The VM will crash if any significant load is placed on
the system).
> More than one Component class? from where? I'm just using tomcat 4 jars
> and cocoon 2 jars...
Where are they installed?
> Different ClassLoaders? I don't quietly understand that, doesn't Cocoon
> use the Java ClassLoader of the virtual machine running it? I see a
> components.classloader package in cocoon, that's the class loader it
> uses? Can the cause be that that classloader is not compatible with the
> class loader of the virtual machine (JBuilder's VM) running it?
There is a whole ClassLoader heirarchy. Tomcat 4 has all the server libraries
loaded in a classloader that is separate from the servlet libraries. Internally,
Cocoon creates a classloader and has the parent point back to the servlet
classloader.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
