[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [wsvt-dev] Design of WSDL 1.2 Validator
- From: "Sakala, Adinarayana" <Adi.Sakala@xxxxxxxx>
- Date: Wed, 5 Nov 2003 18:04:03 -0500
- Delivered-to: firstname.lastname@example.org
- Thread-index: AcOUbaj0VcQZz/dIQMehprOIekKeGwPgjaGw
- Thread-topic: [wsvt-dev] Design of WSDL 1.2 Validator
Can you tell us,
- when the ant and commandline interface is going to be available?
- When the CVS repository is going to be populated?
we are looking to integrate the WSDL Validation tool
into one of our product, as part of this we will be spending next couple of
weeks looking at this tool. Since our tool is not currently based on Eclipse, initially
we are looking to include this functionality as a standalone.
BTW, I am also interested in contributing to this work.
Since this is my first time to deal with Eclipse projects, i definetly need
little help in getting started.
How are decisions about requirements, design etc are made in this project.
Is everything done via email or people who are active get together on conf calls.
If you could point me to any guidelines for contributing to this project that would
be very helpful.
200 West Street Waltham, MA 02451 USA
Tel: (781) 902-8161
Fax: (781) 902-8009
Making Software Work Together TM
From: Lawrence Mandel [mailto:lmandel@xxxxxxxxxx]
Sent: Friday, October 17, 2003 1:11 AM
Subject: Re: [wsvt-dev] Design of WSDL 1.2 Validator
Good tasks list Arthur. Here's an update on what you've listed.
1. The list of test assertions needs to be created from the WSDL 1.2
specification. This is something we can start now with the working draft
and modify as the specification is modified. (There is already a schema for
WSDL 1.2 available on the WSDL working group site.)
2. The test suite can be created as we create the test assertions document.
3. An interface based on the Abstract WSDL 1.2 model in the 2003/10/13
editors draft of the WSDL specification has been written and will be
available online in a few days as we move the CVS repository to the eclipse
4. As soon as the interface for WSDL 1.2 based on the abstract model is
available I'd like to get work started on a simple DOM implementation.
5. JUnit test cases should be written as functionality is added to both the
model and the validator.
6 + 7.Both an Ant task interface and a command line interface to the WSDL
validator have been written. The code for both should be online in a few
days as we move the CVS repository to the eclipse site. Both tasks have
their base functionality but still need functionality to be added for
specifying advanced options.
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.
WebSphere Studio Application Developer - XML Tools
Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920
Sent by: wsvt-dev@xxxxxxxxxxx
[wsvt-dev] 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
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 assertions.
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 interface.
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 Framework.
5. Create JUnit test cases
Pull all the above together into an automated test suite.
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 XmlValidate
7. Create Shell command: WSDLValidate
Make it invokable as a Java main().
-- Arthur Ryman
wsvt-dev mailing list