You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/10/01 08:11:49 UTC

DO NOT REPLY [Bug 23536] - Addition to 23269 bug (JSP compilation fail) in Cocoon

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23536>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23536

Addition to 23269 bug (JSP compilation fail) in Cocoon





------- Additional Comments From joerg.heinicke@gmx.de  2003-10-01 06:11 -------
I might be not that familiar with Java, but this description sounds a bit
tangled up. So please correct me, if I'm wrong:

1.
> 2001-09-30 20:37:44 Error compiling file: D:\Tom 
> cat\work\Standalone\localhost\cocoon\samples\jsp\/welcome_jsp.java     [javac] 
> Compiling 1 source file
>     [javac] javac: invalid flag: D:\Tom
>     [javac] Usage: javac <options> <source files>
>     [javac] where possible options include:
>     [javac]   -g                        Generate all debugging info
> ...................................
> But without Cocoon all ok!
> 
> If Tomcat installed to path without spaces - C:\Tomcat\.., for example, all ok.

You said when using path without spaces everything is ok. But the above path IS
without spaces. Or do you have it installed at "C:\Tom cat" ???

2. Forking. If Cocoon does not force Tomcat to fork for compiling the JSP, how
should this be bad, if Tomcat has both options? Ok, there could be a bug in
Tomcat when the JVM is not forked.

3. Synchronized. As far as I know this is for serializing the block execution,
so that it can't be executed parallelly. I simply guess that you aren't
requesting the JSP multiple times in parallel. So how should the synchronized
have any influence? Shell the JSP be compiled multiple times? Ok, there are
includes and forwards. More important: How should this be related to path names? 

At the mentioned bug 23269 the reporter hasn't been providing the root cause for
the failure until now, so we can't do anything. At least the last time I tried
everything was ok with the sample JSPs in Cocoon. I'm using Tomcat 4.1.24.

Joerg