You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by Arthur Ryman <ry...@ca.ibm.com> on 2006/02/01 03:01:09 UTC
WSDL 2.0 Validator Ant Task: WODEN-4
FYI,
I created a JIRA issue [1] for this item. Please review and add your
requirements.
[1] https://issues.apache.org/jira/browse/WODEN-4
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
----- Forwarded by Arthur Ryman/Toronto/IBM on 01/31/2006 08:53 PM -----
Arthur Ryman/Toronto/IBM
01/30/2006 11:05 PM
To
woden-dev@ws.apache.org
cc
woden-dev@ws.apache.org
Subject
Re: M3
Lawrence,
OK, I'll add these items to JIRA. For iteration 1 of the Ant task I
propose the following:
1. always do validation since its a validatation task
2. add a boolean to set fail-on-error
3. add a boolean to set verbose output
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Lawrence Mandel/Toronto/IBM@IBMCA
01/29/2006 06:34 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
Subject
Re: M3
Sounds good Arthur. I think you've got a good start on the Ant task. We'll
need to integrate Woden features and properties, a way to contribute a URI
resolver (the framework is not yet in place), trip fail-on-error, and
possibly a way to use caching and specify an alternate implementation.
Lawrence Mandel
Arthur Ryman <ar...@gmail.com>
01/28/2006 03:10 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
Subject
Re: M3
Lawrence,
OK. I'll contribute it. At present it just reads and validates a fileset
of WSDL documents.
I suggest we use JIRA to capture requirements for the Ant task. I can
create an enhancement request and people can comment on it. This would
give us some simple documentation. Does this make sense?
On 1/22/06, Lawrence Mandel <lm...@ca.ibm.com> wrote:
Woden does not yet contain an Ant task. I was going to add this to our
task list. Please contribute your Ant task. I will add a task to create a
command line interface to Woden as well.
Thanks,
Lawrence Mandel
Arthur Ryman/Toronto/IBM@IBMCA
01/20/2006 09:39 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
woden-dev@ws.apache.org
Subject
Re: M3
Lawrence,
Yes, I wrote an Ant task just to automate my testing. Is there an Ant task
in Woden? If not, I can contribute it. The testcases I am using are from
the W3C test suite.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Lawrence Mandel/Toronto/IBM@IBMCA
01/20/2006 05:11 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
Subject
Re: M3
Hi Arthur,
Looks like you're running an Ant task to test Woden. Did you author an Ant
task for Woden? Can you contribute your test cases so we can see if we can
reproduce these problems?
The Woden test suite does include the W3C WSDL test cases and I did not
see these error messages when running the test suite.
Thanks,
Lawrence Mandel
Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920
lmandel@ca.ibm.com
Arthur Ryman/Toronto/IBM@IBMCA
01/20/2006 03:14 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
Subject
M3
I did a little testing of M3 and it looks OK. However, I noticed some XML
schema error messages. These don't stop the validation but I wonder if
this is a current limitation or I'm doing something wrong. Notice the
[error] messages:
Buildfile: D:\workspaces\woden-m3\m3test\build.xml
compile:
jar:
[jar] Building jar: D:\workspaces\woden-m3\m3test\lib\validatewsdl20.jar
main:
[validatewsdl20] File dir = D:\workspaces\woden-m3\m3test
[validatewsdl20] File baseDir = D:\workspaces\woden-m3\m3test
[validatewsdl20] file count: 4
[validatewsdl20] Reading file: Interface.wsdl
[validatewsdl20] Path:D:\workspaces\woden-m3\m3test\Interface.wsdl
[validatewsdl20] Reading
file:///D:/workspaces/woden-m3/m3test/Interface.wsdl
[validatewsdl20] [Error] Interface.wsdl:7:164: cvc-elt.1: Cannot find the
declaration of element 'wsdl:description'.
[validatewsdl20] There are 0 ElementDeclaration components.
[validatewsdl20] There are 1 Interface components.
[validatewsdl20] Interface[0] : name = {http://example.org/}myInterface
[validatewsdl20] There are 0 Binding components.
[validatewsdl20] There are 0 Service components.
[validatewsdl20] Reading file: XSDImport.wsdl
[validatewsdl20] Path:D:\workspaces\woden-m3\m3test\XSDImport.wsdl
[validatewsdl20] Reading
file:///D:/workspaces/woden-m3/m3test/XSDImport.wsdl
[validatewsdl20] [Error] XSDImport.wsdl:8:164: cvc-elt.1: Cannot find the
declaration of element 'wsdl:description'.
[validatewsdl20] [Error] name.xsd:4:94: cvc-elt.1: Cannot find the
declaration of element 'schema'.
[validatewsdl20] There are 2 ElementDeclaration components.
[validatewsdl20] ElementDeclaration[0] : name = {
http://example.org/name}SIN
[validatewsdl20] ElementDeclaration[1] : name = {
http://example.org/name}Name
[validatewsdl20] There are 1 Interface components.
[validatewsdl20] Interface[0] : name = {http://example.org/XSDImport}Names
[validatewsdl20] There are 0 Binding components.
[validatewsdl20] There are 0 Service components.
[validatewsdl20] Reading file: XSDImport2.wsdl
[validatewsdl20] Path:D:\workspaces\woden-m3\m3test\XSDImport2.wsdl
[validatewsdl20] Reading
file:///D:/workspaces/woden-m3/m3test/XSDImport2.wsdl
[validatewsdl20] [Error] XSDImport2.wsdl:8:164: cvc-elt.1: Cannot find the
declaration of element 'wsdl:description'.
[validatewsdl20] [Error] XSDImport.wsdl:8:164: cvc-elt.1: Cannot find the
declaration of element 'wsdl:description'.
[validatewsdl20] [Error] name.xsd:4:94: cvc-elt.1: Cannot find the
declaration of element 'schema'.
[validatewsdl20] There are 2 ElementDeclaration components.
[validatewsdl20] ElementDeclaration[0] : name = {
http://example.org/name}SIN
[validatewsdl20] ElementDeclaration[1] : name = {
http://example.org/name}Name
[validatewsdl20] There are 1 Interface components.
[validatewsdl20] Interface[0] : name = {http://example.org/XSDImport}Names
[validatewsdl20] There are 0 Binding components.
[validatewsdl20] There are 0 Service components.
[validatewsdl20] Reading file: test.wsdl
[validatewsdl20] Path:D:\workspaces\woden-m3\m3test\test.wsdl
[validatewsdl20] Reading file:///D:/workspaces/woden-m3/m3test/test.wsdl
[validatewsdl20] [Error] test.wsdl:16:40: cvc-complex-type.2.4.c: The
matching wildcard is strict, but no declaration can be found for element
'schema'.
[validatewsdl20] [Error] test.wsdl:39:67: cvc-complex-type.4: Attribute
'type' must appear on element 'wsdl:binding'.
[validatewsdl20] Woden[Error],0:0,Binding-0055,The binding 'NamesBinding'
does not define bindings for the interface operation '{
http://example.org/name}getNameFromSIN'. When a binding specifies an
interface it must specify bindings for all of the interfaces operations.
[validatewsdl20] There are 2 ElementDeclaration components.
[validatewsdl20] ElementDeclaration[0] : name = {
http://example.org/name}SIN
[validatewsdl20] ElementDeclaration[1] : name = {
http://example.org/name}Name
[validatewsdl20] There are 1 Interface components.
[validatewsdl20] Interface[0] : name = {
http://example.org/name}NameInterface
[validatewsdl20] There are 1 Binding components.
[validatewsdl20] Binding[0] : name = {http://example.org/name}NamesBinding
[validatewsdl20] There are 1 Service components.
[validatewsdl20] Service[0] : name = {http://example.org/name}NamesService
BUILD SUCCESSFUL
Total time: 1 second
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca