cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24402] - [PATCH] XML posting from SourceWritingTransformer by using an enhanced HTTPClientSource
Date Mon, 17 Nov 2003 08:59:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24402>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24402

[PATCH] XML posting from SourceWritingTransformer by using an enhanced HTTPClientSource





------- Additional Comments From danielf@nada.kth.se  2003-11-17 08:59 -------
This patch has similar functionality as
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24391, see also
http://xml.com/pub/a/2003/11/12/cocoon-eai.html.
I have not yet gone into the details of bug 24391, but it seem to have some
login and retry functionality that my patch lacks.

I think it would be a good idea to merge the two proposals. I would prefer
puting as much functionality as possible in the HTTPClientSource, this would
give as one implementation of web service functionality that can be used in
various contexts, e.g. generators, transformers and flowscripts. Now there are a
couple of components that implements partly overlapping functionality: the
generators in the proxy block, the xsp soap language, the CIncludeTransformer
and the here discussed transformers.

For the transformer part I have no strong opinions, I put the functionality into
the SourceWritingTransformer, as it seemed to be the place for handling of
modifyable sources, and as I think there are to many transformers already (but I
guess that is a completly different question). A seperate transformer is ok for
me as well.

WDYT?

Mime
View raw message