You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "olivier gattaz (JIRA)" <ji...@apache.org> on 2009/07/21 09:25:14 UTC
[jira] Created: (AXIS2-4436) 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)
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.
[jira] Updated: (AXIS2-4436) 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)
Posted by "olivier gattaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
olivier gattaz updated AXIS2-4436:
----------------------------------
Component/s: wsdl
> 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
> Components: wsdl
> 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.
[jira] Commented: (AXIS2-4436) 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)
Posted by "Sagara Gunathunga (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776011#action_12776011 ]
Sagara Gunathunga commented on AXIS2-4436:
-------------------------------------------
WSDL20ToAxisServiceBuilder use AARBasedWSDLLocator as a customWSDLResolver. In order to resolve schema documents locally AARBasedWSDLLocator should look-up with any catalog before it load over the network but current resolveURI(URI unResUri) method does not invoke any catalog and hence it always try to access schema over the network .
It is possible to solve this by Invoking Woden's default URIResolver under the resolveURI(URI unResUri) method to find out whether the particular schema is locally available or not , if it is available return the local URL.
> 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
> Components: wsdl
> 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.
[jira] Commented: (AXIS2-4436) 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)
Posted by "Sagara Gunathunga (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776015#action_12776015 ]
Sagara Gunathunga commented on AXIS2-4436:
-------------------------------------------
Fix for AXIS2-4521 will work for this too.
> 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
> Components: wsdl
> 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.