Frederick, thank you for you reply.
Are you saying, that all I need to do is to modify the wsdl by hand and even though ARS would generate the kind of wsdl you're describing our partner would be able to consume our web service? In other words since I've created forms that reflects the wsdl of the web service of our partner, I could basically take the wsdl I posted here, modify it slightly and ask him to use it to consume our web service? Is this that simple? Yes, you're right. I've left out a few sections for clarity. Thanks Mark On Feb 9, 6:55 pm, "Grooms, Frederick W" <frederick.w.gro...@xo.com> wrote: > I don't believe you will ever get ARS to create a WSDL in that exact format > as the system will create a type for a complexType structure instead of > embedding it. Most every system I have seen creates named type structures. > > i.e. The structure in your example: > <xsd:element name="InterfaceDoc"> > <xsd:complexType> > <xsd:sequence> > ... > > ARS will create something like: > <xsd:element name="InterfaceDoc" type="InterfaceDocType" /> > <xsd:complexType name="InterfaceDocType"> > <xsd:sequence> > ... > > And your enumerated value type of fields: > <xsd:element name="URGENCY" nillable="true" minOccurs="0"> > <xsd:simpleType> > <xsd:restriction> > <xsd:simpleType> > <xsd:restriction base="xsd:string"> > <xsd:whiteSpace value="preserve"/> > </xsd:restriction> > </xsd:simpleType> > <xsd:enumeration value=""/> > <xsd:enumeration value="0"/> > <xsd:enumeration value="1"/> > <xsd:enumeration value="2"/> > </xsd:restriction> > </xsd:simpleType> > </xsd:element> > > will be something like: > <xsd:element name="URGENCY" nillable="true" minOccurs="0" > type="URGENCYtype"/> > <xsd:simpleType name="URGENCYtype"> > <xsd:restriction base="xsd:string"> > <xsd:enumeration value=""/> > <xsd:enumeration value="0"/> > <xsd:enumeration value="1"/> > <xsd:enumeration value="2"/> > </xsd:restriction> > </xsd:simpleType> > > (FYI: Your example is missing the message, portType, binding, and service > sections, but you may have left those out on purpose for the list.) > > Any application working with web services should understand named types. If > it doesn't you could always take the WSDL that ARS generates and modify it by > hand (and send it to them as a file). > > Fred > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Mark Milke > Sent: Wednesday, February 09, 2011 9:45 AM > To: arsl...@arslist.org > Subject: Re: Web Services Question > > Hi Tristan, > > I frankly can't imagine how a form would look like to force ARS to get > me the exact WSDL. I tried to do it manually, but I'm not getting the > results. I'll check out BMCDN though. > > Mark > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Tristan Roppel > Sent: Wednesday, February 09, 2011 8:30 AM > To: arsl...@arslist.org > Subject: Re: Web Services Question > > Hello, > > If you have the wsdl description file as well, i think, there is an open > source tool for generating the form in Remedy. > Look at BMCDN ? > > Cheers > > Tristan > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug11www.wwrug.comARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
