Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 50701 invoked from network); 14 May 2004 20:58:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 May 2004 20:58:03 -0000 Received: (qmail 32245 invoked by uid 500); 14 May 2004 20:58:15 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 31962 invoked by uid 500); 14 May 2004 20:58:13 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 31933 invoked by uid 98); 14 May 2004 20:58:13 -0000 Received: from rdeanna@mmm.com by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(192.28.4.49):. Processed in 0.097375 secs); 14 May 2004 20:58:13 -0000 X-Qmail-Scanner-Mail-From: rdeanna@mmm.com via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(192.28.4.49):. Processed in 0.097375 secs) Received: from unknown (HELO sulu2.mmm.com) (192.28.4.49) by hermes.apache.org with SMTP; 14 May 2004 20:58:13 -0000 Received: from hi-arches.mmm.com ([143.122.30.115]) by sulu2.mmm.com (8.12.10/8.12.9) with ESMTP id i4EKvgvs006898 for ; Fri, 14 May 2004 15:57:43 -0500 (CDT) Subject: Re: any issues with Holder classes? ... In the words of Roseanne Rosanna-Dana ... never mind! :) To: axis-user@ws.apache.org X-Mailer: Lotus Notes Release 5.0.3 March 21, 2000 Message-ID: From: rdeanna@mmm.com Date: Fri, 14 May 2004 14:57:41 -0600 X-MIMETrack: Serialize by Router on HI-Arches/HI-HealthInfo/3M/US(Release 6.0.2CF1|June 9, 2003) at 05/14/2004 02:57:42 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N All, I believe it was my issue. I had exposed a pre-existing Java class as a Web Service using Axis tools: 1) Java2WSDL - to generate the WSDL then 2) WSDL2Java - to generate the stubs/skeletons It appears that....... If your original Java method had a "holder" argument, the Java2WSDL creates a "holder" parameter in the message "Request"...rather than an additional parameter in the message "Response". I modified the generated WSDL by: 1) removing the "holder" parameter in the Request 2) adding a string as an additional parameter in the Response. Then I re-ran WSDL2Java. This resulted in the parameter being represented as a javax.xml.rpc.holders.StringHolder argument in the method signature of the stubs and skeletons. Everything ran great using both a Java and C# client!!! Thanks again, Bob |---------+-----------------------------> | | rdeanna@mmm.com | | | | | | 05/14/2004 01:19 | | | PM | | | Please respond to | | | axis-user | | | | |---------+-----------------------------> >-----------------------------------------------------------------------------------------------------------------------------| | | | To: axis-user@ws.apache.org | | cc: | | Subject: any issues with Holder classes? | >-----------------------------------------------------------------------------------------------------------------------------| Hello, I have been using Axis for a couple of weeks now and it runs great!!! I have created about 15 Web Services without any issues...until the following: In my latest WebService, I have a method that receives a String Holder as one of its 3 arguments. I set the value of the StringHolder and print it out within Axis...and it looks fine. But when I print out the value in my client (both an Axis client and C# client), the value is null. The return value (also a string) of the method, is received by both clients just fine. Are there any know issues with holder classes, or String Holders in particular? Thanks in advance and fantastic job!!! Bob