cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <>
Subject Re: Preparing the new dojo-rsrc build
Date Thu, 11 Sep 2008 14:35:41 GMT
Hi All

Ironically, it turns out that after further testing, the current state  
of all of the CDNs for Dojo 1.1.1 are not suitable for Cocoon.

Unfortunately, whoever did the build, neglected the extra step of  
making sure full L10N support was added. Dojo ends up with defaults  
that do not match the output of icu4j and breaks number validation on  
a very wide range of locales.

Exasperating .....

I am talking to some guys at Dojo about it, to see if they can  
redeploy 1.1.1 or at least change their release policy to make sure  
this does not happen with 1.2.

regards Jeremy

On 11 Sep 2008, at 09:06, Robin Wyles wrote:

>>> By default I would prefer not to have to rely on an external  
>>> service to run any part of my application, so with that in mind  
>>> option 3 seems most sensible to me. Also, I imagine option 1 would  
>>> make development without a network connection difficult.
>> I hope that if you read my response to Hussayn earlier in this  
>> thread that you will understand my reasoning for going (initially  
>> at least) with the first scenario.
>> Because in production, you would be unlikely to serve Dojo from a  
>> jar, your usecase of developing offline is IMHO the only case for  
>> distributing a full Dojo with Cocoon.
>> I hope you will find that the build script I provide for making a  
>> Dojo Jar, makes the job so easy, you will not find it a barrier to  
>> offline development.
> I would be more inclined to put the whole app behind Apach Httpd,  
> and use mod_cache to cache the static resources once they had been  
> served from Cocoon - I've used this approach in the past and it has  
> worked well. This of course means that all required dojo resources  
> would need to be bundled into my webapp. As long as there is a  
> fairly easy way to build my own dojo.jar I'll be satisfied I think!
> Robin

View raw message