Cass -
> good point. unfortunately i can't say for sure, but i think you'll
> debug it by trying to compile the files command line (at least that's
> how i did).
>
Alas, that was one of the first things I tried - the compilation works
perfectly, with no errors at all.
I am 99% sure this is a classloader issue. I have added more logging lines
and recompiled Cocoon, and the path and class name being passed to the
loader look correct. I am currently working through the layers of
classloader code, trying to see where things could be going wrong. Cocoon
is using a URLClassLoader, so I guess it is possible that the path is being
incorrectly resolved. Another faint possibility is that the repository path
is not being correctly added to the class loader search list. However,
since all of this works in other environments, and in other peoples' Solaris
environments, my main hope is that I'll find something to point to the
'real' issue, which is most likely to be some sort of configuration problem.
Regards,
Tim
---------------------------------------------------------------------
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]>
