Victoria Vitaver wrote:
And to figure out which bits of it arnt compiling I just comment things
out until I get it to compile again. This surely is not the most optimal
method of debugging, especially since I'm quite sure lucene at some
stage does know EXACTLY why my xsp (or rather _xsp.java at that stage)
is not compiling.
there is a reason we moved away from this abomination in 1.4 ;)
Is it possible to somehow see the actual java compile errors of the xsp
somehow/somewhere?
If 'yes': where ?
cocoon transforms the xsp with an xsl into java files and puts them into
the work directory of your container, either tomcat/work or tmp/ for
jetty, iirc
If 'they should be comming up on the error page' : what could I be
mucking up that's preventing this very useful information from reaching me?
it's not your fault :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
