Petals Studio

Actually, it seems that Wsdl4j does not support cross-file inclusions too.
But the parsing is done in such a way, and the examples we use are made in such a way, that we did not see it earlier.

To check it:
+ Have 2 WSDL, one importing the other.
+ Make the importer declare the service.
+ Make the imported declare the port type.
+ Parse it with the studio: it works because we search the services first. But in the code, try to get all the port types. You won't get any.

EasyWSDL 3.0 40M1 appears to be less mature than expected:

• JARs remain used in memory, which leads to JAR locking.
• The API does not cross file imports.
• The writer does rewrite namespaces for every mark-up and does not format the code. The workaround is to use the pretty formatter from EasyCommons, but this does not work with cross-file modifications.

Consequently, this migration is delayed indefinitely.
The removal of Woden is confirmed. Wsdl4j will be kept instead.

OK. In fact, I think there is no interest in supporting WSDL 2.0 in the studio for the moment. Petals does not support it anymore. And we have a lot of specific utilities in the studio for that.

• Remove WSDL4J and Woden from the studio.
• Remove all our useless utilities for WSDL (at least 2 or 3 classes).
• Create a specific bundle for EasyWSDL (*.common.libs.easywsdl). Use the version 3.0-alpha.
• Migrate the rest of the code to use EasyWSDL.

This is not an emergency anymore because WSDL 2.0 is no more supported by EasyWSDL.