W3C home > Mailing lists > Public > public-ws-semann@w3.org > June 2007

Re: [Fwd: SAWSDL Eclipse tests]

From: Joel Farrell <joelf@us.ibm.com>
Date: Tue, 12 Jun 2007 13:36:07 -0400
To: Jacek Kopecky <jacek.kopecky@deri.org>
Cc: Pierre.CHATEL@fr.thalesgroup.com, SAWSDL public list <public-ws-semann@w3.org>, richard.aillet@fr.thalesgroup.com
Message-ID: <OFCE852C16.35305439-ON852572F8.005BBBC1-852572F8.0060B7C1@us.ibm.com>
Hi Jacek,

In Eclipse, the reordering worked.  The WSDL validated, although the WSI
profile compliance check could not run to completion.  Code generation was


public-ws-semann-request@w3.org wrote on 06/12/2007 11:48:37 AM:

> Dear Pierre, Richard and Joel,
> I wonder whether the problem might be in the wrong ordering of the
> elements. I just checked the WSDL schema and the schema primer and it
> seems that the extensibility elements should come first (according to
> the schema, that is), whereas our spec has two examples with the reverse
> order, first wsdl:input and wsdl:output, then sawsdl:attrExtensions.
> I'm not sure though whether tools would expect the extension elements to
> be after the WSDL elements (because the order matters - it specifies the
> message exchange pattern), in which case tweaking the schema could be
> necessary.
> Richard or Pierre, can you please try the file with the reverse order of
> sawsdl and wsdl attributes? Or whether you could tweak the schema used
> by your tool to also allow extension elements after the WSDL elements?
> Best regards,
> Jacek
> -------- Forwarded Message --------
> From: Joel Farrell <joelf@us.ibm.com>
> To: SAWSDL public list <public-ws-semann@w3.org>
> Subject: SAWSDL Eclipse tests
> Date: Tue, 12 Jun 2007 09:09:07 -0400
> I have done some further testing on the following developer tools:
> IBM WebSphere Integration Developer 6.0.1
> Eclipse 3.2.1 with Web Tools Platform 1.5.2
> Eclipse 3.2.2 with Web Tools Platform 1.5.4
> In each case, WSDL files with attrExtensions under operation can be
> created and edited without errors. However, in each tool, when an
> explicit validation is done, the attrExtensions element is flagged as
> invalid.
> Eclipse uses wsdl4j to parse WSDL files. The two wsdl4j parsers in the
> two Eclipse Web Tools Platform levels both use the same xsd file - the
> one that allows element extension for operation , but they still do not
> accept the extension element as used.
> However, in all three tools, I could still successfully generate code
> from the WSDL file. Documenting this fact may allow eclipse-based
> attrExtension usage to proceed.
> Regards,
> Joel
Received on Tuesday, 12 June 2007 17:36:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:20 UTC