Hi Guys,
Ok, I've committed the converter code we discussed to the
org\apache\tool\converter directory.
I also made minor changes to the build.xml and build.properties files to
allow the build script to download WSDL4J and extract it (it is required by
the conversion code).
The tool currently outputs WSDL2.0 files with the same name as the WSDL1.1
files that are converted, but with an ".wsdl2" suffix. I believe the code
can be fairly easily wrapped to output Woden classes instead.
Thanks,
-Matt
"Jeremy Hughes"
<[EMAIL PROTECTED]
rg> To
Sent by: [email protected]
[EMAIL PROTECTED] cc
om
Subject
WSDL 1.1 to 2.0 converter
05/10/2006 12:38
PM
Please respond to
[EMAIL PROTECTED]
he.org
Matt, I just wanted to revive this topic as I was thinking about WSDL
1.1 to 2.0 conversion again. For others reading this, it was discussed
at length here:
http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200603.mbox/%3cOF711CE546.A3398E17-ON85257134.004D9B28-85257134.004
[EMAIL PROTECTED]
I'm a big +1 for you to commit the standalone conversion tool
somewhere in the Woden SVN to help us at least understand the issues
when implementing 1.1 to 2.0 conversion within Woden itself.
Of course, the packages would need to start org.apache.woden.
Howabout, org.apache.woden.tool.converter. We can then play with the
converter to help us understand the issues and potentially move some
of the relevant code into the parser in order to support reading WSDL
1.1 into the model.
Thanks,
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
