Woden attempts to load http://www.w3.org/2001/XMLSchema.xsd every time it 
parses a WSDL document (or if Axis2 instructs Woden to do so)
---------------------------------------------------------------------------------------------------------------------------------------

                 Key: AXIS2-4436
                 URL: https://issues.apache.org/jira/browse/AXIS2-4436
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
    Affects Versions: 1.5
         Environment: Windows XP SP3, Sun JDK 1.6.0_13, Tomcat 6.0.20, Axis2 
1.5 WAR
            Reporter: olivier gattaz


When Axis2  tries to deploy a Webservices which has an explicit "wsdl2" file in 
its "aar" archive,  Woden tries to access to the public URL of the name space  
xmlns:xs="http://www.w3.org/2001/XMLSchema"; .

If the jvm doesn't have a proxy configuration (eg. java networking properties ) 
the socket layer returns the exception "java.net.SocketException:Connection 
reset" after the timeout delay (30 seconds or something like this).

For exemple when I put the sample "StudentService.aar" file ( See Keith 
Chapman's article : "RESTful  Web Services with Apache Axis2" 
http://wso2.org/library/3726 ) in the "services" folder of an Axis2 v1.5 web 
application server, I got these lines in the tomcat log file:

Woden[Warning],0:0,WSDL504,Could not locate the schema document at URL  
"http://www.w3.org/2001/XMLSchema.xsd",java.net.SocketException:Connection reset
Woden[Warning],0:0,WSDL504,Could not locate the schema document at URL  
"http://www.w3.org/2001/XMLSchema",java.net.SocketException:Connection  reset 
Woden[Warning],0:0,Description-1001,The targetNamespace  
'http://axis2.apache.org' is not dereferencable.
[INFO] Deploying Web service: StudentService.aar -  
file:/D:/_devs_intradon/X3_SERVERWSJULIET/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/com.sage.x3.serverws.axis2/WEB-INF/
 services/StudentService.aar




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to