Stefano Wrote:
> > we currently have two of them: one in the trunk and another one in a > > block. Also, it seems that the one in the trunk is broken.
<snip/>
> > I would like to move the proxy-related samples into the proxy block and > > also remove the one from the trunk. > > > > Anybody against this?
Are you talking HttpProxyGenerator vs. WebServiceProxyGenerator? If so, I'd like to double check to see if all of the functionality of the WSPG is in the HTTPPG before having the WSPG go away. The old WSPG would always GET a resource. The WSPG's docs said you could use <map:parameter name="wsproxy-method" value="post"/> if you wanted the proxy to POST to the URL instead. It didn't actually do that, so I added some stuff to the WSPG to allow POST.. it would be nice to not lose that functionality.
<snip/>
I think there were big changes coming to the WSPG from Hussayn Dabbous ([EMAIL PROTECTED]). He was working with a committer to add support for
proxying the existing session (for single sign-on).
Geoff Howard
