[wsas-java-dev] XSLT that converts WSDL11 to WSDL20

[Davanum Srinivas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

MPL is ok for us to ship.

thanks,
dims

Jonathan Marsh wrote:
> AIUI Saxon is substantially faster than Xalan.  I don't know if the Mozilla
> Public License is compatible with Apache, but I suspect it will be.
> http://saxon.sourceforge.net/saxon6.5.2/conditions.html
> I think the stylesheet is available under the W3C document license, but I'll
> check.
>  
> 
> Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
>  
>> -----Original Message-----
>> From: saminda abeyruwan [mailto:saminda at wso2.com]
>> Sent: Thursday, August 16, 2007 9:19 AM
>> To: wsas-java-dev at wso2.org
>> Cc: Jonathan Marsh; mashup-dev at wso2.org
>> Subject: Re: [wsas-java-dev] XSLT that converts WSDL11 to WSDL20
>>
>> Hi All,
>>
>> With the help of Kieth and Ruwan, I've been able to integrate
>> http://www.w3.org/2006/02/wsdl11to20.xsl to WSAS; WSDL11 to WSDL20
>> converter.
>>
>> The prior XSLT has version 2.0 rules. Thus, we want be able to use
>> Xerces or Xalan XSL parsers. XSLT 2.0 templates are processed by SAXSON
>> parsers. In addition to this SAXSON parsers also process XSLT 1.0
>> templates. [1,2 & 3]
>>
>> Following has stated in [1]
>>
>> **
>> Saxon comes in two packages: Saxon-B implements the "basic" conformance
>> level for XSLT 2.0 and XQuery, while Saxon-SA is a schema-aware XSLT
>> and
>> XQuery processor. Both packages are available on both platforms (Java
>> and .NET). Saxon-B is an open source product available from this site;
>> Saxon-SA is a commercial product available from Saxonica Limited. A
>> free
>> 30-day evaluation license is available.
>> **
>>
>> The artifacts we are going to use are Saxen-B complaint. Thus, we could
>> remove Xerces and Xalan dependencies and introduce SAXSON dependencies
>> into our system. This is open source and available in maven2 repos. I
>> still haven't been able to find the licensing document for Saxon-B
>> complaint artifacts. Please aid me on this.
>>
>> I've been able to test this around Axis2 templates, Try it templates
>> and
>> the prior mentioned converter template.
>>
>> If we were to move into Saxon-B, following will be need in processing
>> the templates.
>>
>> 1. Saxon-8.9.jar (3.6M) or Saxon-8.7.jar (3.1M)
>> 2. Saxon-dom-8.9.jar (89K) or Saxon-8.7.jar (43K)
>> 3. Saxon-xpath-8.9.jar (37K) or Saxon-8.7.jar (37K)
>>
>> Saxon-*-8.7.jars are available in standard Maven2 repository, yet
>> Saxon-*-8.9.jars are not available.
>>
>> If the licensing is compliant, shall we move to Saxon parsers when
>> processing XSLTs.
>>
>> Thank you
>>
>> Saminda
>>
>> Resources :
>>
>> [1]. http://saxon.sourceforge.net/
>> [2]. http://www.saxonica.com/
>> [3]. http://www.w3.org/TR/xslt20/
>>
>> saminda abeyruwan wrote:
>>> Hi Jonathan,
>>>
>>> We are on the process of writing tools for users of WSAS, and out of
>> one
>>> will be WSDL11 to WSDL20 converter.
>>>
>>> In order to get this tool working, we've used Convert class that
>> comes
>>> from Woden project. Apparently, it doesn't have all the parsing
>>> capabilities such as unrecognizing SOAP12 binding, HTTP binding etc.
>>>
>>> Is there a version 1.0 XSLT to do the conversion?
>>>
>>> Thank you and looking forward to hearing from you.
>>>
>>> Saminda
>>>
>>> _______________________________________________
>>> Wsas-java-dev mailing list
>>> Wsas-java-dev at wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
>>>
> 
> 
> _______________________________________________
> Wsas-java-dev mailing list
> Wsas-java-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
> 


- --
Davanum Srinivas (dims at wso2.com)
Director, Customer Engagements, WSO2 (http://wso2.com)
Yahoo IM: dims Cell/Mobile: +1 (508) 415 7509
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFGxRH/gNg6eWEDv1kRAmJeAKClBkXLd1C6Zr/9eqZlV2Jf8oWFugCg0r7A
Yx1btYCnOJ/8DU2JUOWAT18=
=g4if
-----END PGP SIGNATURE-----