Cocoon 2.1
September 19th, 2003
Yesterday, I got me a fresh CVS copy of Cocoon 2.1, you know, just for fun. Since I haven't used Cocoon at work for quite some time now (hmm, almost 2 years I guess), I've only glanced at it once in a while. I'm still lurking on cocoon-dev though.
The first thing that hit me: 2 years ago, cocoon.war was already a healthy 6-8 MB. Now it has become 35 MB. Whoa! Would that mean we get 6 times the functionality?
Further on, the build went smoothly this time. Back in the days, you had to dig through some README.TXT and INSTALL.TXT to find the right command (something along the way of
My last pet peeve: no proxy support. Somewhere in the samples, there is an "aggregator" which fetches some RSS feeds (I think) to display. However, the HTTP connection times out, which makes me think that it doesn't go through the proxy. And I haven't found a clean way to get through, either.
Anyway, the demos looked spiffy, and there was lots of them.
Scary how much you miss though when only looking at the comments, and not at the code: I thought blocks were still a work-in-progress, but it seems they have been implemented already. Marc's apples are in there too. I'll certainly have to look closer at these.
Nice to see things have evolved so quick. If the control flow is now stabilized, maybe I can have a try at introducing Cocoon at the workplace (Koen, are you reading this?)
Update:Thanks to Bertrand's comment, I got the proxy working. I was trying to use
The first thing that hit me: 2 years ago, cocoon.war was already a healthy 6-8 MB. Now it has become 35 MB. Whoa! Would that mean we get 6 times the functionality?
Further on, the build went smoothly this time. Back in the days, you had to dig through some README.TXT and INSTALL.TXT to find the right command (something along the way of
ant -Dbuild.webapps=xxx install, not exactly intuitive). Now a ant war did the job perfectly. It got my PC busy for 25 minutes, but without a hitch. I hope there is a shortcut to compile while developing on the codebase, because I can't imagine coding with such a large turn-around time.My last pet peeve: no proxy support. Somewhere in the samples, there is an "aggregator" which fetches some RSS feeds (I think) to display. However, the HTTP connection times out, which makes me think that it doesn't go through the proxy. And I haven't found a clean way to get through, either.
Anyway, the demos looked spiffy, and there was lots of them.
Scary how much you miss though when only looking at the comments, and not at the code: I thought blocks were still a work-in-progress, but it seems they have been implemented already. Marc's apples are in there too. I'll certainly have to look closer at these.
Nice to see things have evolved so quick. If the control flow is now stabilized, maybe I can have a try at introducing Cocoon at the workplace (Koen, are you reading this?)
Update:Thanks to Bertrand's comment, I got the proxy working. I was trying to use
-Dhttp.proxy and -Dhttp.port, as I found somewhere, but it has to be -DproxyHost and -DproxyPort. Thanks Bertrand!
April 21st, 2008 at 10:17 PM yes yes, i read it :)
April 21st, 2008 at 10:17 PM Mmmm, nice to see you play again with this stuff! Some fast clarifications [blocks] - blocks are currently 'enabled' as a way of modularizing the build process - have a look at the ant xpatch (see http://wiki.cocoondev.org/Wiki.jsp?page=XPatchTaskUsage) task to understand part of the magic - since it is modular you should be able to cut down on your 25 build minutes by excluding some blocks from the build (see local.blocks.properties) - blocks still need to evolve into a runtime loading modular system... this is what we call 'real blocks' and which is quite actively discussed to date [apples] Comments welcome! [cocoon@work] Just come over to the GT man, and bring along Koen: http://www.orixo.com/events/gt2003/ at least you will be able to ware a nifty cocoon t-shirt to work (I just got to see a design review :-)) [proxy stuff] Happily expecting your fixes ;-)
April 21st, 2008 at 10:17 PM Regarding proxies, don't java system properties work, something like -DproxyHost=myproxy.blabla.com -DproxyPort=8080 or "http.proxyHost" and "http.proxyPort", I think some components use one and use the other. If you find the answer it would be cool to add it to the Cocoon Wiki How-tos! And yes, you do get six times the functionality: more than 45 blocks and counting ;-)
April 21st, 2008 at 10:17 PM Tom, try the following code to get through your firewall: java.util.Properties systemProperties = System.getProperties(); systemProperties.put("proxySet","true"); systemProperties.put("proxyHost","your proxy host"); systemProperties.put("proxyPort","8080"); System.setProperties(systemProperties); URL sourceURL = a URL object; java.net.URLConnection connection = sourceURL.openConnection(); String pwd = "domain.username:password"; B64 b64 = B64(); String encodedPwd = b64.encode(pwd); connection.setRequestProperty("Proxy-Authorization","basic "+encodedPwd); InputStream is = connection.getInputStream(); David