DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32541>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32541





------- Additional Comments From [EMAIL PROTECTED]  2004-12-09 14:36 -------
Differences are not about including XML response once or doing it multiple
times, it's about features. Anyway, you can't do asynchronous HTTP calls (the
results wouldn't be in the outgoing document, or in the right order), and they
can't be nested, so it makes no sense sending multiple request.

I looked at the Proxy Generators... HttpProxyGenerator provides some of the
functionalities of the HTTP[Request/Include]Transformer, but not all. For
example, it can't send SOAP call; it's why WebServiceProxyGenerator was created.
But then, another problem comes in mind; both proxies don't allow the user to
manually set request header, or authentication information. It could be a real
problem when you want to access some secure servers or when the server filters
request on the User-Agent header.

The transformer I submitted does all these things in one component, that's the
beauty! But I agree with you on merging generators and transformer altogether
into one component. It would be far more elegant instead of having multiple
generators/transformers when one would be enough. And both transformer and a
generator could use that component. I'm willing to investigate this way and
maintaining the component (if I am allowed, of course). I suggest renaming
HTTPIncludeTransformer to HTTPRequestTransformer and we could put it in the 2.2
branch, in a block or in the scratchpad area and let the users use both
HttpProxyGenerator or HTTPRequestTransformer for now. I think both have their 
place.

WDYT?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.

Reply via email to