-
Bug
-
Resolution: Done
-
Major
-
jbossws-native-3.0.4
-
None
When JBossWS is publishing the schema imports from a WSDL file and it tries to published an already published schema, the rest of schemas are not published.
The bug is in the class WSDLFilePublisher, in the method publishSchemaImports. There's a piece of code that says:
while (it.hasNext())
{
.......
if (schemaLocation.startsWith("http://") == false)
{
// infinity loops prevention
if (published.contains(schemaLocation))
else
{ published.add(schemaLocation); }....
Obviously, if the published.contains(schemaLocation) condition is true, the return clause will finish the execution of the method before processing the remaining items in the while loop.
If we replace the "return" with a "continue", everything works fine
- duplicates
-
JBWS-2413 WSDLPublisher fails when trying to publish include schemas that contain relative paths
- Closed
- is duplicated by
-
JBWS-2438 WSDLFilePublisher prematurely stops publishing schema imports
- Closed
- is incorporated by
-
JBPAPP-1644 JBossWS - WSDL schema imports do not published successfully
- Closed
-
JBPAPP-1744 JBossWS - WSDL schema imports do not published successfully
- Resolved
- is related to
-
JBWS-1843 WSDL with custom schema imports causes java.lang.OutOfMemoryError: Java heap space when there are circular schema imports dependencies
- Closed
-
JBWS-1906 Stack overflow exception when reading bad wsdl files
- Closed
-
JBWS-2411 OutOfMemoryExecption in WSDL11Reader when loading xml schemas with circular references
- Closed