OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Using non-SOAP XML-Vocabularies in Web-Services

[ Lists Home | Date Index | Thread Index ]

I am a tester at BEA.
We just released a beta of "WebLogic Workshop", which does just that.
I don't know the exact URL, but you can find it somewhere under 

If you send me your WSDL, I can see that it (or something substantially 
similiar) gets incorporated into our test suite.


-Wayne Steele

>From: Gabriel Vögler <gvoegler@web.de>
>To: <xml-dev@lists.xml.org>
>Subject: [xml-dev] Using  non-SOAP  XML-Vocabularies in Web-Services
>Date: Fri, 1 Mar 2002 12:30:41 +0100
>I am writing a thesis about Web-Services and E-Procurement.. I built a
>JAXM-based prototype which gives back catalogues. I decided to not use the
>SOAP-encoding, because there exist xml-standards for catalogues (e.g.
>www.bmecat.org)  and I wanted to use these standards directly. Many 
>on this list seems to confirm the opinion, that the SOAP-encoding is not a
>good solution if industry-standards already exist.
>My problem is, that many Web-Service tools doesn't work well with my
>prototype. Many of them are designed for RPC and SOAP-encoded  based
>Web-Services. I have an handwritten WSDL-file (DOC-style) for my service,
>but many tools fail to generate proper proxy-code. But if can't generate
>proxy-code one advantage of  Web-Services is lost...
>Does anybody knows some tools which can help to build SOAP-clients for
>Web-Services which don't use SOAP-encoding?

MSN Photos is the easiest way to share and print your photos: 


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS