[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wsvt-dev] Design of WSDL 1.2 Validator
- From: Ganga Sah <ganga_sah@xxxxxxxxx>
- Date: Thu, 16 Oct 2003 23:25:39 -0700 (PDT)
- Delivered-to: firstname.lastname@example.org
> I'm going to second Arthur's call for volunteers. We
> are looking for help
> on many parts of the validator. This is a great
> opportunity to get involved
> in a project that provides a real benefit to the Web
> services community.
I am new to this list but I have done some hands on
existing wsvt(wsi) test tool. I have good programming
experience in using JAX-RPC(SOAP/WSDL) in Axis and Sun
JWSDP implementations. I have also written a B2BTest
tool using XML schema based testCase definition, JAXB
for XML/Java binding and test results marshalled as
XML report with a stylesheet. I use elipse platform
and am familiar for eclipse EMF/XSD tools.
I would like to voluteer to work on this projectbut
may need help to get started.
Thanks in advance.
> Lawrence Mandel
> Software Developer
> WebSphere Studio Application Developer - XML Tools
> Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920
> Sent by:
> Design of WSDL 1.2
> 10/16/2003 12:07 Validator
> Please respond to
> I'd like to get this work going since the WSDL 1.2
> is shaping up nicely.
> Here are some tasks that I suggest we work on:
> 1. Create a list of test assertions.
> The approach to validation for WSDL 1.2 is to rely
> on XML Schema as much as
> possible. The schema for WSDL 1.2 will contain as
> many checks as possible.
> However, not all checks can be expressed in XML
> schema. For example, checks
> involving more than one WSDL document are beyond the
> scope of XML schema. A
> WSDL document may import or include other WSDL
> documents and there are many
> checks for import and include to be valid. There are
> also many other checks
> on single documents that cannot be expressed in XML
> schema. Therefore, we
> should compile a list of test assertions that our
> validator will check
> beyond those expressible in XML schema. It would
> also be a good idea to
> explicitly list the checks we expect to be handled
> by XML schema and verify
> that the official WSDL schema incorporate those
> checks. The WS-I test tools
> used a nice XML format for listing the test
> assertions. I suggest we use
> that format.
> 2. Create a test suite.
> We should create a set of WSDL documents that
> include both valid and
> invalid cases. Every test assertion should have at
> least one test case that
> satisfies it and one that violates it. Any test case
> may cover more than
> one test assertion. This test suite will be a little
> unstable until the
> WSDL schema settles down, but we can probably
> migrate our test suite to new
> versions of the schema using an XSLT. I expect only
> fairly small changes
> from now on.
> 3. Define an interface for coding the test
> I suggest we create a Java interface that closely
> matches the abstract
> model used in the WSDL spec. We should code all the
> test assertions using
> this interface. Note that this interface only needs
> to provide read access
> to the WSDL documents.
> 4. Develop one or more implementations of the WSDL
> We need to define at least one implementation of the
> interface. I suggest
> we do a simple DOM implementation initially.
> However, we may also want to
> do others, e.g. one using the Eclipse Modelling
> 5. Create JUnit test cases
> Pull all the above together into an automated test
> 6. Create Ant task: WSDLValidate
> We should make the validator available as an Ant
> task. This should be
> analogous to the XML Schema validator Ant task
> 7. Create Shell command: WSDLValidate
> Make it invokable as a Java main().
> -- Arthur Ryman
> wsvt-dev mailing list
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search