www.capeclear.com is the Cape Clear corporate site. www.capescience.com is the developer resources site sponsored by Cape Clear.
Anne -----Original Message----- From: Aleksander Slominski [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 3:54 PM To: [EMAIL PROTECTED] Subject: CapeScience SOA Editor URL [Re: Have doubts about Doc/Lit with axis hi, there are some problems with URLs such as one provided in the press release: http://www.capeclear.com/news/press_releases/reports/print/soaeditor_print.h tm as this http://www.capeclear.com/integration/soa/ does not seem work: this URL seems to work OK: http://www.capescience.com/soa/download.shtml alek ps. it is a bit confusing CapeScience vs CapeClear but seems to be the same thing though ... Dario Di Minno wrote: > I had problems too, but I solved them with the help of the "SOA Editor", > a wsdl editor and validator that you can download for free at > www.capeclear.com > because it returned some warnings in my "not-so-perfect" wsdl files!! > so I used it > to fix my wsdl files. Try it! > > Dario > > > > [EMAIL PROTECTED] ha scritto: > >>Dave, I had a lot of problems too, specially with 1.2 beta, so I reverted >>back to 1.1. I know I have seen a lot that makes its support of doc/lit >>look inadequate, but once I finally got the right WSDL, it did work. I >>have a java client that can call it and a .NET program that can. The >>trick seems to be getting the right WSDL. If you look back at the last >>message Anne Thomas Manes sent me with WSDL, that WSDL worked. Perhaps >>you can modify it to meet your needs? Just an idea. Good luck. >> >> >> >> >>"David Thielen" <[EMAIL PROTECTED]> >>04/26/2004 09:09 AM >>Please respond to >>[EMAIL PROTECTED] >> >> >>To >><[EMAIL PROTECTED]> >>cc >> >>Subject >>RE: Have doubts about Doc/Lit with axis >> >> >> >> >> >> >>I tried and tried and tried to get doc/literal to work - and finally gave >>up. I think it just has too many problems still. >> >>- dave >> >> >>-----Original Message----- >>From: Jim Murphy [mailto:[EMAIL PROTECTED] >>Sent: Monday, April 26, 2004 6:40 AM >>To: [EMAIL PROTECTED] >>Subject: Re: Have doubts about Doc/Lit with axis >> >>Everything you have looks good to me - in terms of valid WSDL and >>conforming SOAP request message. I wonder: what do you get when you >>replay the "xsd:anyURI" type with xsd:string? I don't think it should >>make a difference but...everything else looks so generic I'm at a loss >>to suggest anything else! >> >>Good luck, >> >>Jim Murphy >>Mindreef, Inc. >> >> >> >>cagerhon wrote: >> >> >>>Dear All, >>> >>>I have some problems with axis 1.2 beta sending Doc/Lit messages. >>> >>>I am using the wsdl below to generate client stub and produce messages >>> >>> >>to >>send >> >> >>>to server, >>>but axis seems not able to find the correct method to invoke or may >>>get null value in the parameter of "cccOp" method of >>> >>> >>"APortTypeSOAPBindingImpl" >> >> >>>class. >>> >>>the message on the wire looks like this: >>><?xml version="1.0" encoding="UTF-8"?> >>><soapenv:Envelope >>> >>> >>xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >> >> >>>xmlns:xsd="http://www.w3.org/2001/XMLSchema" >>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> >>> <soapenv:Body> >>> <ccc xmlns="abcde"> >>> <add>http://ibm.com.tw/test/me</add> >>> </ccc> >>> </soapenv:Body> >>></soapenv:Envelope> >>> >>>does any one know how to do the right Doc/Lit programming with axis 1.2 >>> >>> >>beta? >> >> >>>or is there anything wrong with my way? >>>Any asnwer will be very appriciated. >>> >>>Thanks in advance. >>> >>> >>>Sincerely, >>>Hong >>> >>> >>>Ps. below is the wsdl I am using. >>> >>><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >>>xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" name="" >>>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" >>>xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="abcde"> >>> >>> <wsdl:types> >>> <xsd:schema targetNamespace="abcde" >>>xmlns:xsd="http://www.w3.org/2001/XMLSchema"> >>> >>> <xsd:complexType name="aType"> >>> <xsd:sequence> >>> <xsd:element name="add" type="xsd:anyURI"/> >>> </xsd:sequence> >>> </xsd:complexType> >>> <xsd:element name="ccc" type="abcde:aType"/> >>> >>> </xsd:schema> >>> </wsdl:types> >>> >>> <wsdl:message name="ccc"> >>> <wsdl:part name="parameters" element="abcde:ccc"/> >>> </wsdl:message> >>> >>> <wsdl:portType name="APortType"> >>> <wsdl:operation name="cccOp"> >>> <wsdl:input name="ccc" message="abcde:ccc"/> >>> </wsdl:operation> >>> </wsdl:portType> >>> >>> <wsdl:binding name="APortTypeSOAPBindingImpl" type="abcde:APortType"> >>> <wsdlsoap:binding style="document" >>>transport="http://schemas.xmlsoap.org/soap/http"/> >>> <wsdl:operation name="cccOp"> >>> <wsdlsoap:operation soapAction=""/> >>> <wsdl:input> >>> <wsdlsoap:body use="literal"/> >>> </wsdl:input> >>> </wsdl:operation> >>> </wsdl:binding> >>> >>> <wsdl:service name="AService"> >>> <wsdl:port binding="abcde:APortTypeSOAPBindingImpl" name="A"> >>> <wsdlsoap:address >>> >>> >>location=http://localhost:8080/my/services/A/> >> >> >>> </wsdl:port> >>> </wsdl:service> >>></wsdl:definitions> >>> >>> >>> >>> >> >> >> >> >> > -- The best way to predict the future is to invent it - Alan Kay