Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 2292 invoked by uid 500); 27 Nov 2002 21:22:00 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 2269 invoked from network); 27 Nov 2002 21:21:59 -0000 Message-ID: <3DE5381C.9070305@hist.umn.edu> Date: Wed, 27 Nov 2002 15:24:44 -0600 From: Tony Collen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-users@xml.apache.org, cocoon-dev@xml.apache.org Subject: [Summary] WebServiceProxyGenerator & wsproxy-method parameter Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi list(s), After almost a week of pounding my head on the cement, I've figured out what's been going on with the WSPG. Consider the following pipeline: Alright, simple enough, correct? The only "odd" thing about this is that is uses the wsproxy-method parameter, which I used according to samples/webserviceproxy/README.txt. For some reason however, even though I told the WSPG to POST to the servlet, it refused. Here's the (very verbose) output from my debug servlet I wrote: 1 [PostServlet] doGet() called 2 [PostServlet] Passing request and response to doPost() 3 [PostServlet] doPost() called 4 [PostServlet] Getting parameter "Mode" from request. 5 [PostServlet] Mode is null! 6 [PostServlet] Sending some XML anyway. 7 [PostServlet] Done sending XML. Exiting. The following output leads me to the following two conclusions: 1) Even though I'm telling the WSPG to use POST on the remote service, it's not (Line 1). 1a) I can't see anywhere in the WSPG code where it's getting the wsproxy-method configuration parameter :) 2) When the WSPG copies over the request parameters, somehow the POST parameters are either not being copied over, or they're being stomped on somehow. Basically, the WSPG is not proxying the POST parameters correctly (Lines 4 and 5). For now, I'll file a bug. Ivelin, perhaps we can work together to get this functioning correctly... mostly because I need it to work correctly to get my job done :) If anything I'll submit a patch to add some more useful debug logging to the WSPG. Tony --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: