[
https://jira.jboss.org/jira/browse/JBESB-3166?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3166:
------------------------------
Description: Imports were only being rewritten if the protocol was http or https. If
it was file, classpath or internal, the imports were simply left alone - not really that
they were "malformed" *by* anything. There are two parts to the fix: 1) rewrite
the imports, 2) add the scheme check *and* relative import fixing to the import recursion.
(was: Imports were only being rewritten if the protocol was http or https. If it was
file, classpath or internal, the imports were simply left alone - not really that they
were "malformed" *by* anything. There are two parts to the fix: 1) rewrite the
imports by prepending the import locations with the appropriate scheme, 2) add the scheme
check *and* relative import fixing to the import recursion.)
non-http or https import schemes' (file, classpath, internal)
locations not rewritten by SOAPProxyWsdlLoader
------------------------------------------------------------------------------------------------------------
Key: JBESB-3166
URL:
https://jira.jboss.org/jira/browse/JBESB-3166
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7 CP1
Imports were only being rewritten if the protocol was http or https. If it was file,
classpath or internal, the imports were simply left alone - not really that they were
"malformed" *by* anything. There are two parts to the fix: 1) rewrite the
imports, 2) add the scheme check *and* relative import fixing to the import recursion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira