Hi Michael- Many Thanks to AT for the valuable insight
I found a REST (resource centric) implementation using HTTP transport located at https://wadl.dev.java.net/ where each resource has GET and POST methods e.g. <resources ...> <method name="GET" ..> <request> <param name="appid" type="xsd:string"/> https://wadl.dev.java.net/wadl20061109.pdf using 'simple types' xsd:string as suggested by at as far as url-encoding http://www.blooberry.com/indexdot/html/topics/urlencoding.htm you can either write your own converter or use some manner of XSLT transformer as described http://www.mnot.net/webdesc/ HTH Martin ----- Original Message ----- Wrom: XIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPK To: <axis-user@ws.apache.org> Sent: Friday, March 14, 2008 9:45 AM Subject: Re: Easy way to determine URL? > Thanks, > > That is the answer I was looking for. > > My next question is how can I generate some sample code to give to the > people who want to use my services? > > For my simple messages I will include a URL in the samples. > For the more complex examples I will include javascript and visual > basic samples. > Are there any other samples I should generate? > > I anticipate that some people's responses to my request is that the > .wsdl is good enough. But I want to take it one step further. I am > trying to make the use of my services easy for a programmer who has > never used web services. > > -- > Michael Potter > > On Fri, Mar 14, 2008 at 7:19 AM, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > Are you asking how to use the REST interface and submit your > > parameters using url encoding? > > > > That's only possible when using simple types. > > > > Anne > > > > > > > > On Thu, Mar 13, 2008 at 7:50 PM, Michael Potter <[EMAIL PROTECTED]> wrote: > > > Martin, > > > > > > I don't think I have any problem with the transport. > > > > > > I am trying to figure out what I should use for a url to test the service: > > > > > > Would you expect this to work?: > > > > > > http://localhost:8080/axis2/services/ClientStuff/updateClientAddress?CltNum= A&SitCod=B&AddTyp=C&AddrL1=D&CityCd=E&ZipCod=F&StatCd=G&FonNum=H&StatAr=I&Cn tryC=J > > > > > > If so, I will try harder to make that work. If not, please propose > > > something for me to try. > > > > > > -- > > > Michael Potter > > > > > > > > > > > > On Thu, Mar 13, 2008 at 3:14 PM, Martin Gainty <[EMAIL PROTECTED]> wrote: > > > > Mike- > > > > > > > > whatever algorithm you're using > > > > if the transport is not http then you'll need to reconfigure the transport > > > > to accept a valid URL for that transport (HTTP/TCP/SMTP) > > > > http://ws.apache.org/axis2/1_3/transport_howto.html > > > > > > > > does this conform to your understanding? > > > > M- > > > > > > > > > > > > ----- Original Message ----- > > > > Wrom: YLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXU > > > > To: <axis-user@ws.apache.org> > > > > Sent: Thursday, March 13, 2008 12:56 PM > > > > Subject: Easy way to determine URL? > > > > > > > > > > > > > Axis2 Crew, > > > > > > > > > > I find it tedious to figure out what to use for a URL to use to test > > > > > an axis2 webservice. > > > > > Is there some tool that we can use that will "split out" a sample URL? > > > > > > > > > > Of particular problem are webservices such as the one below that has > > > > > nested variables and webservices with arrays of variables. > > > > > > > > > > Can anyone tell me how to handle the nested variables and arrays of > > > > variables? > > > > > > > > > > Maybe it is not possible to use a URL for these more complex cases? > > > > > > > > > > <wsdl:operation name="updateClientAddress"> > > > > > <wsdl:input message="axis2:updateClientAddressInputs"> > > > > > </wsdl:input> > > > > > <wsdl:output message="axis2:ClientAddress"> > > > > > </wsdl:output> > > > > > </wsdl:operation> > > > > > > > > > > > > > > > <wsdl:message name="updateClientAddressInputs"> > > > > > <wsdl:part name="part0" element="tns:updateClientAddressInputsGroup"> > > > > > </wsdl:part> > > > > > </wsdl:message> > > > > > <wsdl:message name="ClientAddress"> > > > > > <wsdl:part name="part0" element="tns:ClientAddressArray"> > > > > > </wsdl:part> > > > > > </wsdl:message> > > > > > > > > > > <xs:element name="updateClientAddressInputsGroup" > > > > > type="updateClientAddressInputsGroupType"/> > > > > > <xs:complexType name="updateClientAddressInputsGroupType"> > > > > > <xs:sequence> > > > > > <xs:element name="ClientNumber" type="ClientNumberType"/> > > > > > <xs:element name="ClientAddress" type="ClientAddressType"/> > > > > > </xs:sequence> > > > > > </xs:complexType> > > > > > <xs:complexType name="ClientNumberType"> > > > > > <xs:sequence> > > > > > <xs:element name="CltNum" type="xs:string"/> > > > > > </xs:sequence> > > > > > </xs:complexType> > > > > > <xs:complexType name="ClientAddressType"> > > > > > <xs:sequence> > > > > > <xs:element name="SitCod" type="xs:string"/> > > > > > <xs:element name="AddTyp" type="xs:string"/> > > > > > <xs:element name="AddrL1" type="xs:string"/> > > > > > <xs:element name="CityCd" type="xs:string"/> > > > > > <xs:element name="ZipCod" type="xs:string"/> > > > > > <xs:element name="StatCd" type="xs:string"/> > > > > > <xs:element name="FonNum" type="xs:string"/> > > > > > <xs:element name="StatAr" type="xs:string"/> > > > > > <xs:element name="CntryC" type="xs:string"/> > > > > > </xs:sequence> > > > > > </xs:complexType> > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
