[Users] A WSDL file could not be imported

stagirus mamasa at stagirus.com
Wed Jan 9 16:46:14 CET 2013


Thank you Vincent. I found there was an extraneous character got inserted at
the end of the WSDL file. Not sure how it got there. After removing that
character, importing the WSDL was successful. Your suggestion of validating
the XML/WSDLs is also very helpful.

I have a few other questions. I hope you can help me.
1. CXF generated WSDL files contain a complete definition of schema for each
WSDL file. These definitions get repeated for every WSDL file. CXF correctly
maintains namespaces according to Java package names. In the past, we had
some challenges with Open ESB because of this issue. Their ESB/Studio
complained that it could not use the same object definitions across multiple
services because each service had its own schema definitions. So, my team
had to manually extract the common schema definitions into a separate/shared
schema file. This was a laborious process. How does Petals Studio handle
this issue? Is this even an issue with Petals? 

2. I have several CXF services/WSDLs to be imported into Petals Studio.
Rather than saving and importing of each service/WSDL at a time, can Petals
Studio import all WSDLs available on the App Server folder (/services) at
once?

Thanks in advance for your help.
 



--
View this message in context: http://forum.petalslink.com/A-WSDL-file-could-not-be-imported-tp4025421p4025424.html
Sent from the Users (get help, provide help) mailing list archive at Nabble.com.


More information about the Users mailing list