[
https://issues.jboss.org/browse/JBWS-3827?page=com.atlassian.jira.plugin....
]
R Searls commented on JBWS-3827:
--------------------------------
code added as described above into
https://svn.jboss.org/repos/jbossws/common/trunk
(3.0.0-SNAPSHOT).
Committed revision 18976.
Index: src/main/java/org/jboss/ws/common/utils/AbstractWSDLFilePublisher.java
===================================================================
--- src/main/java/org/jboss/ws/common/utils/AbstractWSDLFilePublisher.java (revision
18971)
+++ src/main/java/org/jboss/ws/common/utils/AbstractWSDLFilePublisher.java (working copy)
@@ -143,7 +143,7 @@
{
String locationURI = wsdlImport.getLocationURI();
// its an external import, don't publish locally
- if (locationURI.startsWith("http://") == false)
+ if (locationURI.startsWith("http://") == false &&
locationURI.startsWith("https://") == false)
{
// infinity loops prevention
if (published.contains(locationURI))
====================================
The fix was tested manually. It was not possbile to create an automated test. Manual
configuration of standalone.xml and $JAVA_HOME/jre/lib/security/cacerts would be
required.
WSDL publisher incorrectly attempt to publish external HTTPS import
-------------------------------------------------------------------
Key: JBWS-3827
URL:
https://issues.jboss.org/browse/JBWS-3827
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Affects Versions: jbossws-cxf-4.3
Reporter: Marc H.
Assignee: R Searls
Fix For: jbossws-cxf-5.0
In org.jboss.ws.common.utils.AbstractWSDLFilePublisher, the condition used to detect
external import looks like this:
// its an external import, don't publish locally
if (locationURI.startsWith("http://") == false) { ... }
This does not take in account import done over other protocols such as HTTPS. Deploying
such WSDL will fail since jboss will try to resolve an absolute URL against the current
deployment unit.
Simply adapting the test to include "https://" seems effective (not sure if it
truly satisfies all use cases however).
This was only tested in version 2.2.3 Final of jboss-ws-common but those lines are still
in trunk...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)