outerthought :: Marc, himself, his blogs, and you reading them

maandag 28 april 2003

Just watching...

Just sitting outside, having a drink, just watching the world pass by...It really has been, and keeps on being, a splendid way to pick up interesting people :-)

This evening my new favourite information game (to be combined with real working in fact) gave me this, adding these two:

to my list of things I will read when old-fashion-traveling (aprox 9 hours: car-train-boat-bus-subway) to London on the day they are cleaning the Chunnel and thus are not operating the EuroStar (sigh)

10:40:29 PM

Cocoon Apples

Bertrand looks in his crystal ball and sees what this year will bring...

So I got into the example of the much cited wiki-page, and have been poking around a bit in the code here and there, a lot more to investigate, and hopefully be doing it soon...

I've somewhat set the original existential feelings asside and went in through the door of pragmatics... still I'ld have to conclude that I'm missing some more application-object oriented contracts in the whole of Cocoon... and it's quite well reflected by the /* FIXME */ remarks lingering in the code here and there... How are we to 'address' business objects that need to be influencing the cocoon pipeline?

See, if your pipeline needs to mingle itself with some xml or xslt there is the wealth of cocoon: and whatnot stuff to declare in the @src's of the sitemap... if what needs to be sliced in is a true Java Object (be it bean, form-model, js wrapper object, continuation,...) then suddenly the nice and obvious addressing scheme is to be replaced with mysterious (i.e. conspired behind the controlling back of the sitemap) strings as Map keys into (pick randomly one out of) Environment, ObjectModel, Request and Session... [and euh, "bean-dict" and "kont" are quite inspirationless choices indeed :-)]

It's too vague as an idea, but maybe some source of the kind object: could be giving access to an object space declared by the sitemap (for reading and writing).... of course current sources are quite targetted to being wrappers around inputstreams...

Or am I trying to compare apples with pears?

Another thing that strikes me is that in most examples to date the pipelines become application-technique-specific... that might be logical at first glance, yet still I'ld like to see some mechanism to easily reuse application-agnostic pipes in different application-controllers: say have one WoodyForm, that together with it's (one) publication pipe gets reused in two distinct use cases, one handled by flowscript, and one by actions?

Mmm, Maybe just the definition of clever <map:resource>'s should tackle that?Just have to sit and think some more...

In the mean time, actively hoping Betrand's ball is right...

10:30:00 PM