Hi CarstenFor static files that are just using a reader, this may be a good solution.
In the case of these system pipelines however, there is a sitemap/ flowscript etc. that has to be executed.
As for static files, they are currently being served for 2 blocks, Forms which has CForms Dojo Widgets, CSS and Images; Ajax which has more Widgets etc. plus it contains Dojo libs.
Due to a recent development at AOL, it could be possible to do without distributing Dojo from Cocoon :
http://ajaxian.com/archives/including-dojo-via-the-aol-cdn "Alex Russell has:constructed a couple of very small “wrapper” files that will let you include the “Ajax” build of Dojo from various versions through the cross-domain loader.
Including the latest stable Dojo couldn’t be simpler: <script src="http://download.dojotoolkit.org/dojo_0.3.1.js"></script> It’s also trivial to test out the latest 0.4.1 Release Candidate: <script src="http://download.dojotoolkit.org/dojo_0.4.1rc2.js"></script> " I have not tested this yet.My hopes are that CForms etc. will be compatible with Dojo 0.4.n very shortly :)
regards Jeremy On 6 Dec 2006, at 08:04, Carsten Ziegeler wrote:
I'm wondering if it would be better to use a resource servlet for serving resources instead of going through the sitemap? With 2.2 we can mount servlets at mount paths through the dispatcher servlet. So perhaps this is a way to go? (Just a rough idea) Carsten Jeremy Quinn wrote:Hi Guys I am trying to get support for the new Upload Progress Bar working in Cocoon 2.2. I need to add a new system pipeline to the top-level sitemap, like (and adjacent to) the one that handles : <map:match pattern="_cocoon/resources/*/**"> this is the snippet : <map:match pattern="_cocoon/system/*/**"> <map:select type="resource-exists"> <map:when test="system/{1}/sitemap.xmap"> <map:mount src="system/{1}/sitemap.xmap" uri- prefix="_cocoon/system/"/> </map:when> <map:otherwise> <map:mount src="resource://org/apache/cocoon/{1}/system/ sitemap.xmap" uri-prefix="_cocoon/system/{1}/"/> </map:otherwise> </map:select> </map:match> The purpose is to mount Block-Level system pipelines. I /think/ the place I make this change is in : /core/cocoon-webapp/src/main/webapp/sitemap.xmap (But TBH I am not sure) Next I am trying to get this compiled in, so that it is available for the 'cocoon-dist-samples' and everything else that may be built from this distribution. I have tried to compile this in, but it never becomes available to the samples. I tried running $ mvn package in both : core/cocoon-webapp/ dists/cocoon-dist-samples/ Neither results in the changes happening to the file at : dists/cocoon-dist-samples/target/cocoon-samples/sitemap.xmap TBH I find this new build system so deeply opaque, I do not know where to start solving this. What am I supposed to do ? Thanks for any suggestions regards Jeremy-- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
smime.p7s
Description: S/MIME cryptographic signature
