Yep, do it in the setup
public void setup(SourceResolver resolver, Map objectModel, String src,
Parameters par) throws ProcessingException, SAXException, IOException
{
super.setup(resolver,objectModel,src,par);
try
{
Source inputSource = resolver.resolveURI(super.source);
this.source =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warren,
Resurrecting an old thread: I hadn't noticed your reply back in March.
On 3/1/2011 5:46 AM, warrell harries wrote:
It doesn't make any difference - it's plain old HTTP despite the
jargon :)
Of course.
If you have already seen this
Hi Chris,
It doesn't make any difference - it's plain old HTTP despite the jargon :)
If you have already seen this
http://www.mail-archive.com/users@cocoon.apache.org/msg34182.html
then investigate the original Generator code at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warrell,
On 2/28/2011 6:41 AM, warrell harries wrote:
Please see recent discussion regarding proxying to another server. In
brief, I usually deploy a custom transformer based on the web service
proxy transformer but setting the user agent header
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I'm using Cocoon 2.1.11 with some pipelines that fetch data from another
webapp via Apache httpd which logs the requests with the User-Agent
being Java/whatever. I'm wondering if Cocoon offers the ability to
tweak the User-Agent string that is
