On Thu, 2009-09-03 at 15:29 +0200, Andreas Hartmann wrote: > Thorsten Scherler schrieb: > > On Thu, 2009-09-03 at 13:23 +0200, Reinhard Pötz wrote: > >> Thorsten Scherler wrote: > >>> Hi all, > >>> > >>> our site is based on different blocks and one main webapp > >>> (cocoon-22-archetype-webapp). > >>> > >>> The problem we are facing is that developing within blocks is really > >>> rapid thanks to the rcl but all the code we have in the webapp needs to > >>> have a constant rebuild, which is a real pain. > >>> > >>> http://cocoon.apache.org/2.2/maven-plugins/maven-plugin/1.0/1358_1_1.html > >>> > >>> Is talking about the goals that are doing the rcl stuff, how can we > >>> "port" this to the webapp? > >>> > >>> Any hints and tips are welcome. > >> Why do you have to put Java code into the webapp at all? > > > > Not talking about the java code that is the bad thing. I am talking > > about normal xsl/sitemap changes. :( > > I use the webapp only as a container for the blocks, it doesn't contain > any code at all. There is a "welcome" block which is mounted at / as an > entry point.
Definitely a clean workaround. ;) How do you deal with the fact that the mount does not provide a pass-trough attribute anymore? I mean in 2.1 I can mount different maps which are looked into and if no match can be found there they are coming back to the parent sitemap and look for the next mount/match. That is a problem that we face in forrest with the switch to 2.2. > That works quite well, but the class loader incompatibilities (e.g. for > session attributes) are still a real PITA (cannot cast class Foo to Foo) :( How did you worked around that? salu2 -- Thorsten Scherler <thorsten.at.apache.org> Open Source Java <consulting, training and solutions> Sociedad Andaluza para el Desarrollo de la Sociedad de la Información, S.A.U. (SADESI)
