cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [RT] Rethinking the SourceResolver concept
Date Mon, 20 Oct 2003 05:47:00 GMT
Dean Cording wrote:
>
> The inability of a sitemap to resolve relative references outside
> of itself
> is the biggest bugbear I have with Cocoon.  The ability the have
> a hierarchy
> of sitemaps allows me to modularise my applications very nicely but not
> being able to refer to a pipeline in another sitemap, except by
> an absolute
> reference, completely destroys the advantage of doing so.
>
> Here is an example from my current Cocoon application:
>
> The application consists of a number of different areas of
> functionality and
> each area is being developed by separate developers.  It makes
> sense take a
> modular approach and use separate directories and sitemaps for each
> functional area so that each developer can work independantly from the
> others and so that all files for a particular function are easily
> identifiable.  By having a directory hierarchy and automounting sitemaps,
> everything is sweet.
>
> However, a number of screens contain a particular collection of list boxes
> that require some complex processing to produce.  Rather that have each
> developer reimplement this, a common module has been developed and each
> developer uses cinclude to incorporate the XML to implement the
> listboxes in
> the appropriate place in their screen code.  The problem is that
> because the
> common code is in a separate sitemap it cannot be referenced to using a
> relative cocoon: reference, only an absolute reference from the
> Cocoon root.
>
> This becomes a problem when I need to run a second copy of the application
> on the same server, say as a training or testing system.  Ideally I should
> just be able to make a copy of my original application and give it a
> different root directory name.  The problem is that this copy now contains
> absolute references to pipelines in the original.
>
> Their are a number of workarounds (separate copies of Cocoon for instance)
> but they all lead to design ugliness.
>
This answer might be a little bit odd, but with the real blocks of Cocoon
2.2
you can exactly do what you want without the ugliness.

Carsten


Mime
View raw message