cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Henne <>
Subject Re: More on Debugging Cocoon2 in VAJ
Date Mon, 20 Aug 2001 10:36:40 GMT

"Kaufman, Noah" wrote:
>         The problem we're having is that Cocoon 2 works fine with Tomcat
> outside of the debugger, but when we run Cocoon 2 in the debugger it
> craps out with the following error:  "The sitemap handler's sitemap is
> not available."  which means absolutely nothing to us, since it then
> tells you to look in the Cocoon 2 log for more information - of which
> there is none.

regarding C2 and VAJ you have to keep in mind a few things:

- The sitemap consists of a generated and compiled Java class
- VAJ is able to load these classes if you add the work/cocoon directory to
the "extra classpath", however, you won't be able to debug them and reloading
won't work (which means to restart the servlet engine for every change vou
make to the sitemap)
- cocoon uses it's own classloader for the generated stuff. This means that
this classloader won't find the classes living inside VAJ

There are several way to make Cocoon work inside VAJ anyway, but they all
involve some drawbacks. The solution we went with (prior to giving up on VAJ
in favor of NetBeans) looks like this:

1) Add the IBM IDE Utility classes to your workspace
2) Replace the C2 code that compiles the generated code with code that
actually perfoms an IMPORT into the VAJ workspace
3) Update the xsp.xsl logicsheet so that the timestamp of generated Classes is
set not in a static initializer, but in the consuructor. This is necessary due
to the fact that VAJ won't re-execute static blocks when it reloads a class.

Please let me know if you want to take that route - I can provide you with the
necessary changes to the cocoon code.

Joerg Henne

To unsubscribe, e-mail:
For additional commands, email:

View raw message