Re: problem with WebServiceProxyGenerator

2003-07-02 Thread Tony Collen (UMN IMAP)
Tony Collen wrote:

snip;

Does anybody know if commons-httpclient has changed recently?
It looks like a bit of stuff that the WSPG uses is currently marked as 
deprecated in commons-httpclient, which could be the cause of our 
problems here. I'll put working on this on my plate ASAP.

Tony

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


problem with WebServiceProxyGenerator

2003-07-01 Thread Hübner, Stefan
Title: problem with WebServiceProxyGenerator






Hello out there,


I'm developing a webapp with cocoon-2.1m2 and want to use the wsproxy. but wsproxy doesn't work, instead it throws an IllegalArgumentException host parameter is null. the configuration is quite simple and should be correct - as far as the documentation is up to date.

map:generator name=wsproxy logger=webapp.wsproxy pool-grow=2 pool-max=16 pool-min=2 src="">




map:generate type=wsproxy src="" href="http://localhost:8080/comnetSkat/login.skat">http://localhost:8080/comnetSkat/login.skat

 map:parameter name=wsproxy-method value=POST/

/map:generate



here's a snippet of the stack trace

ERROR (2003-07-01) 17:12.05:452 [access] (/comnetCocoon/login.skat) Thread-10/CocoonServlet: Internal Cocoon Problem

org.apache.cocoon.ProcessingException: Error invoking remote service: java.lang.IllegalArgumentException: host parameter is null: java.lang.IllegalArgumentException: host parameter is null

 at org.apache.cocoon.generation.WebServiceProxyGenerator.fetch(WebServiceProxyGenerator.java:278)

 at org.apache.cocoon.generation.WebServiceProxyGenerator.generate(WebServiceProxyGenerator.java:158)

 at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processXMLPipeline(AbstractProcessingPipeline.java:545)

 at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:489)

...

Caused by: java.lang.IllegalArgumentException: host parameter is null

 at org.apache.commons.httpclient.HttpConnection.init(HttpConnection.java:227)

 at org.apache.commons.httpclient.HttpConnection.init(HttpConnection.java:148)

 at org.apache.commons.httpclient.SimpleHttpConnectionManager.getConnection(SimpleHttpConnectionManager.java:123)

 at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:548)

 at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:476)

 at org.apache.cocoon.generation.WebServiceProxyGenerator.fetch(WebServiceProxyGenerator.java:251)



so, what's going wrong here? i would be glad, if anybody could give an answer.



thanks you very much in advance.



stefan hübner



ps: I tried the HttpProxyGenerator, but this one doesn't fit my needs, because it passes only those parameters to the remote service which I configure in the sitemap - am I wrong?




Re: problem with WebServiceProxyGenerator

2003-07-01 Thread Joerg Heinicke
There seems to be a real problem with WebServiceProxyGenerator:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg27925.html

Joerg

Tony Collen wrote:
Hübner, Stefan wrote:

Hello out there,

I'm developing a webapp with cocoon-2.1m2 and want to use the wsproxy. 
but wsproxy doesn't work, instead it throws an 
IllegalArgumentException host parameter is null. the configuration 
is quite simple and should be correct - as far as the documentation is 
up to date.

map:generator name=wsproxy logger=webapp.wsproxy pool-grow=2 
pool-max=16 pool-min=2 
src=org.apache.cocoon.generation.WebServiceProxyGenerator/


[snip/]

so, what's going wrong here? i would be glad, if anybody could give an 
answer.


Well, Looking at the source to commons-httpclient at 
http://jakarta.apache.org/commons/httpclient/xref/org/apache/commons/httpclient/HttpConnection.html, 
it looks like the 'host' which is being passed to the constructor is 
null.  Obviously, it's very strange this is happening.  I'll try to dig 
into the WSPG code today and see if I find anything...

Does anybody know if commons-httpclient has changed recently?

Tony


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: problem with WebServiceProxyGenerator

2003-07-01 Thread Tony Collen
Joerg Heinicke wrote:
There seems to be a real problem with WebServiceProxyGenerator:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg27925.html
Yeah, It's looking that way :(

I've noticed posts from other people asking about this, too -- no replies.

I'm a little short on time this afternoon, I'll try to dig into it tonight after class...

Tony

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: problem with WebServiceProxyGenerator

2003-07-01 Thread Lenz, Evan
I have been periodically scanning the list for almost a year, hoping that
someone would take this bull by the horns, i.e. wsproxy in general. At SU
Law, we are currently supporting legacy ASP pages through use of the
HTMLGenerator and hard-coded GET params in sitemap.xmap. I have really been
looking forward to a better approach, especially since it would be nice to
just allow our Web developer to use her ASP skills to develop forms,
surveys, etc. (provided that they generate well-formed output) and know we
can integrate them into our Cocoon-based Web site in a solid and
maintenance-friendly way.

Other features needed to make WebServiceProxyGenerator feature-complete, at
least for us, include:

  * Remote HTTP authentication support
  * Reverse redirects, a la Apache's ProxyPassReverse directive [1]

Good luck to whomever tries to fix the issues with WebServiceProxyGenerator!
You can count me as another user eagerly awaiting to see progress in this
area.

Thanks,

Evan Lenz
Content Management Architect
Seattle University School of Law

[1] http://httpd.apache.org/docs/mod/mod_proxy.html#proxypassreverse


 -Original Message-
 From: Tony Collen [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, July 01, 2003 12:08 PM
 To: [EMAIL PROTECTED]
 Subject: Re: problem with WebServiceProxyGenerator
 
 Joerg Heinicke wrote:
  There seems to be a real problem with WebServiceProxyGenerator:
 
  http://www.mail-archive.com/[EMAIL PROTECTED]/msg27925.html
 
 Yeah, It's looking that way :(
 
 I've noticed posts from other people asking about this, too -- no replies.
 
 I'm a little short on time this afternoon, I'll try to dig into it tonight
 after class...
 
 
 Tony
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: problem with WebServiceProxyGenerator

2003-07-01 Thread Tony Collen
Lenz, Evan wrote:
I have been periodically scanning the list for almost a year, hoping that
someone would take this bull by the horns, i.e. wsproxy in general. At SU
Law, we are currently supporting legacy ASP pages through use of the
HTMLGenerator and hard-coded GET params in sitemap.xmap. I have really been
looking forward to a better approach, especially since it would be nice to
just allow our Web developer to use her ASP skills to develop forms,
surveys, etc. (provided that they generate well-formed output) and know we
can integrate them into our Cocoon-based Web site in a solid and
maintenance-friendly way.
A year?!  Yoink.  I had some mods to the WSPG a while ago and I know it was working correctly.  I 
don't think they were that long ago, though.

Other features needed to make WebServiceProxyGenerator feature-complete, at
least for us, include:
  * Remote HTTP authentication support
  * Reverse redirects, a la Apache's ProxyPassReverse directive [1]
I do know the HttpProxyGenerator was intended as a replacement for the WSPG, but as previous posts 
have mentioned, the newer proxygenerator doesn't contain all of the functionality of the WSPG yet. 
It would be nice to get all of the functionality merged into one nice component (which has the added 
bonus of working correctly ;) )

Tony

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: problem with WebServiceProxyGenerator

2003-07-01 Thread Lenz, Evan
 A year?!  Yoink.  I had some mods to the WSPG a while ago and I know it
 was working correctly.  I
 don't think they were that long ago, though.

Sorry, I didn't mean to imply that it had been completely broken for a year,
but just that for whatever reason it has never been up to snuff for what we
wanted to use it for.

  Other features needed to make WebServiceProxyGenerator feature-complete,
 at
  least for us, include:
 
* Remote HTTP authentication support
* Reverse redirects, a la Apache's ProxyPassReverse directive [1]
 
 I do know the HttpProxyGenerator was intended as a replacement for the
 WSPG, but as previous posts
 have mentioned, the newer proxygenerator doesn't contain all of the
 functionality of the WSPG yet.
 It would be nice to get all of the functionality merged into one nice
 component (which has the added
 bonus of working correctly ;) )

Yes, that sounds good to me!

Evan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



src URL handling problem with WebServiceProxyGenerator

2003-06-19 Thread Philippe Remels
Hi,

I can't get the WebServiceProxyGenerator neither the sample nor any test I can imagine.
It always fails with the same error :

org.apache.cocoon.ProcessingException: Error invoking remote service: 
java.lang.IllegalArgumentException: host parameter is null: 
java.lang.IllegalArgumentException: host parameter is null

It looks like the parsing of the URL specified in 
map:generate type=proxy src=http://test.somewhere.net/myWebService/
fails to extract the host:port info.

I have the feeling I just miss something as nothing works not even the sample.
Can anyone help ?
Thanks

Philippe

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]