Sure. I'll let you follow up by making the changes Brennan suggests to make it work more easily with Ant.
On 9/20/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Anne, Could we consider this template.wsdl as a donation? :) i can check it into samples -- dims On 9/20/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > A fully automatic transformation utility is not realistic. Unless you > adopt and specify standard naming conventions, a utility would not be > able to determine which element should be used for the input message > and which should be used for the output message. If your schema > defines multiple root elements (indicating different operations), the > utility would have no way of determining which elements go with which > operation. > > Hence this will be a manual process. > > You best bet is to take a WSDL template (I've attached one) and fill > in the blanks following the instructions Martin provides below. If you > are using a WSDL editor, the process is even easier. > > Note that in your situation, you already have the schema that the > instructions indicate you must "create or infer". I suggest that you > simply include the schema in the WSDL. Your primary task is figuring > out which element you should use for your input message and which > element you should use for your output message. > > I've specified a few generic names for the various artifacts in the > WSDL (e.g., name="interface" for the portType. You can replace these > names with more descriptive names if you like, but you need to make > sure you change the names consistently (e.g. the "type" attribute in > the binding must reference the Qname of the portType). All the > attribute values that are enclosed in brackets must be changed to > specify the appropriate namespaces, file locations, etc. > > Anne > > On 9/20/06, Martin Gainty <[EMAIL PROTECTED]> wrote: > > > > > > http://blog.springframework.com/arjen/archives/2006/07/27/xslt-that-transforms-from-xsd-to-wsdl/ > > > > where the steps are > > > > start with the XML messages, > > create or infer a schema from that, > > copy all the defined elements in messages, > > create operations from the messages > > create a portType from the operations > > create a binding from the portType > > create a service from the binding > > M- > > ********************************************************************* > > This email message and any files transmitted with it contain confidential > > information intended only for the person(s) to whom this email message is > > addressed. If you have received this email message in error, please notify > > the sender immediately by telephone or email and destroy the original > > message without making a copy. Thank you. > > > > > > > > > > > > ----- Original Message ----- > > From: Shawn McKisson > > To: [email protected] > > Sent: Wednesday, September 20, 2006 2:56 PM > > Subject: XSD -> WSDL tool wanted > > > > > > > > > > I have an XSD that I would like to convert to WSDL. Does Axis provide any > > tools to facilitate this? If not, does anyone have any suggestions on where > > to find something? > > > > > > > > --shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- 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]
