Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 1971 invoked from network); 16 Jun 2006 13:44:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jun 2006 13:44:24 -0000 Received: (qmail 87622 invoked by uid 500); 16 Jun 2006 13:44:19 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 87582 invoked by uid 500); 16 Jun 2006 13:44:18 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 87571 invoked by uid 99); 16 Jun 2006 13:44:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jun 2006 06:44:18 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=HTML_MESSAGE,NO_REAL_NAME,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [216.87.243.242] (HELO maili.wendysi.com) (216.87.243.242) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jun 2006 06:44:15 -0700 Received: from dublspm2.wendysi.com (unknown [216.87.244.68]) by maili.wendysi.com (Postfix) with ESMTP id E8BAD8FC9F for ; Fri, 16 Jun 2006 09:43:54 -0400 (EDT) Received: from dublspm2.wendysi.com (dublspm2.wendysi.com [127.0.0.1]) by localhost.wendysi.com (Postfix) with ESMTP id A66FD532F0 for ; Fri, 16 Jun 2006 09:43:54 -0400 (EDT) Received: from DUBLNS55.WENDYSI.COM (dublns55.wendysi.com [216.87.244.159])by dublspm2.wendysi.com (Postfix) with ESMTP id 9AD43532EFfor ; Fri, 16 Jun 2006 09:43:54 -0400 (EDT) In-Reply-To: To: axis-dev@ws.apache.org Subject: RE: [axis2] client development MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005 Message-ID: From: Mike_McAngus@wendys.com Date: Fri, 16 Jun 2006 09:43:51 -0400 X-MIMETrack: Serialize by Router on DUBLNS55/Wendys(Release 6.5.5|November 30, 2005) at06/16/2006 09:43:52 AM,Serialize complete at 06/16/2006 09:43:52 AM Content-Type: multipart/alternative; boundary="=_alternative 004B6D5B8525718F_=" X-imss-version: 2.040 X-imss-result: Passed X-imss-approveListMatch: *@wendys.com X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_alternative 004B6D5B8525718F_= Content-Type: text/plain; charset="US-ASCII" SoapUI also makes their source available. You could peruse it for ideas on dynamically creating service clients from WSDLs. Mike McAngus Associate Chief Engineer, Enterprise Architecture Wendy's International, Inc. One Dave Thomas Boulevard Dublin, OH 43017 Tony Dean wrote: Thanks, I will check this out as a testing tool. But, one of my main focuses is to be able to read a wsdl and invoke a given service with it's desired input programatically. The input may be simple and/or complex types and the service endpoint may be any style or use. From: Mike McAngus [we need a way to remove eddresses from this list so that spammers don't use this list to harvest eddresses] Sent: Thursday, June 15, 2006 10:55 AM To: axis-dev@ws.apache.org Subject: Re: [axis2] client development Tony, I don't see any replies so far. Have you looked at SoapUI ( http://www.soapui.org/ )? So far, it has been able to interact with all the Services I've had to investigate. Mike McAngus Associate Chief Engineer, Enterprise Architecture Wendy's International, Inc. One Dave Thomas Boulevard Dublin, OH 43017 Tony Dean wrote: Hi, I will preface this saying that I have not done much client development... spending much of my time developing web services themselves. Now, I have need to develop a client that can take an arbitrary wsdl on the fly and generate SOAP requests irregardless of the web service endpoint style (rpc/document, literal/encoded). The SOAP envelope request will need to be generated at runtime so that they process is truly dynamic. I was thinking of using something like wsdl4j to interpret the wsdl and then generate the payload accordingly. Is this the right approach? In your client samples you basically have a ServiceClient that can send OMElement structure in varying MEPs. Is there an API that I can use to tell you for instance that this request is an rpc request with such and such parameters. Or is this left up to the programmer to encode in the OMElement structure? Just looking for some insight and direction. Thanks for your time. Tony Dean SAS Institute Inc. 919.531.6704 tony.dean@sas.com SAS... The Power to Know http://www.sas.com --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org --=_alternative 004B6D5B8525718F_= Content-Type: text/html; charset="US-ASCII"
SoapUI also makes their source available.  You could peruse it for ideas on dynamically creating service clients from WSDLs.

Mike McAngus
Associate Chief Engineer, Enterprise Architecture
Wendy's International, Inc.
One Dave Thomas Boulevard
Dublin, OH 43017


Tony Dean wrote:

Thanks, I will check this out as a testing tool.  But, one of my main focuses is to be able to read a wsdl and invoke a given service with it's desired input programatically.  The input may be simple and/or complex types and the service endpoint may be any style or use.

From: Mike McAngus [we need a way to remove eddresses from this list so that spammers don't use this list to harvest eddresses]
Sent: Thursday, June 15, 2006 10:55 AM
To: axis-dev@ws.apache.org
Subject: Re: [axis2] client development

Tony,

I don't see any replies so far.

Have you looked at SoapUI ( http://www.soapui.org/ )?

So far, it has been able to interact with all the Services I've had to investigate.


Mike McAngus
Associate Chief Engineer, Enterprise Architecture
Wendy's International, Inc.
One Dave Thomas Boulevard
Dublin, OH 43017




Tony Dean wrote:

Hi,

I will preface this saying that I have not done much client development... spending much of my time developing web services themselves.  Now, I have need to develop a client that can take an arbitrary wsdl on the fly and generate SOAP requests irregardless of the web service endpoint style (rpc/document, literal/encoded).  The SOAP envelope request will need to be generated at runtime so that they process is truly dynamic.  I was thinking of using something like wsdl4j to interpret the wsdl and then generate the payload accordingly.  Is this the right approach?  In your client samples you basically have a ServiceClient that can send OMElement structure in varying MEPs.  Is there an API that I can use to tell you for instance that this request is an rpc request with such and such parameters.  Or is this left up to the programmer to encode in the OMElement structure?  Just looking for some insight and direction.

Thanks for your time.

Tony Dean
SAS Institute Inc.
919.531.6704
tony.dean@sas.com

SAS... The Power to Know
http://www.sas.com


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
--=_alternative 004B6D5B8525718F_=--