|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hi Bob,
you are correct. The runtime cannot handle WSDLs imported this way (the path ../../pathToWsdl becomes invalid). My question is why do we allow to do the import in the first place? IMHO this Feature Request is not a valid use case.
I myself don't see any advantages. Now you can import a WSDL from another project only to see an error in the problems tab which says exactly as mentioned in Andrej's comment (https://issues.jboss.org/secure/ViewProfile.jspa?name=apodhrad). And the problem is shown for a good reason!
What would be the correct approach in this case? Copy the WSDL do a local folder or do the import as an URL based on the SOAP address of the service? Any thoughts?
Cheers!
Marek