Hi Daniel,
I was already starting to create a parametrizable BlockSource and
BlockConnection, when Alexander got the idea of creating an
InputSource that would be less invasive to the blocks-fw code.
How do you think should a postable source work? Don't you think
something like a transformer world be a better fit? This way you
could create XML from your request using the request generator, hand
it to a proxy-transformer which will create the Http-Request or the
Block-Request and return the results? The only problem would be
accessing non-xml resources.
Lars
Am 25.10.2006 um 13:39 schrieb Daniel Fagerstrom:
While your input module can be usable in its own right I think that
we should make the block protocol postable. Besides that it
simplify reusing form handling as you describe above. I think that
it is generally useful to make it possible to let blocks contain
web services that can be called through the block protocol and be
used as some webapp internal web services.
To achieve this the o.a.c.blocks.util.BlockCallHttpServletRequest
needs to be extended with input handling and
o.a.c.blocks.components.BlockSource need to implement
ModifiableSource and o.a.c.blocks.BlockProtocol needs to take care
of the input.
I extended the HttpClientSource to be postable long time ago
(http://issues.apache.org/jira/browse/COCOON-871) as part of some
code for handling web service calls within pipelines. I never
applied the patch as we had some disagreement about if it was a
good idea to use web services from Cocoon in this way.
The critique was mainly about my extension of the
SourceWritingTransformer, I still think it would be a good idea to
have postable sources and especially to make the block protocol
postable.
/Daniel
--
Lars Trieloff
visit http://www.mindquarry.com/
