[ 
https://issues.apache.org/jira/browse/AXIS2-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sagara Gunathunga  updated AXIS2-4521:
--------------------------------------

    Attachment: AARBasedWSDLLocator.java.txt
                ArchiveReader.java.txt

Attached  patch will fix this issue and also AXIS2- 4436.

> [WSDL2.0] WSDL504,Could not locate the schema document when tomcat starts up
> ----------------------------------------------------------------------------
>
>                 Key: AXIS2-4521
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4521
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.5
>         Environment: Windows XP
> Tomcat: 5.5
> Axis1.5
>            Reporter: lorcel gao
>         Attachments: AARBasedWSDLLocator.java.txt, ArchiveReader.java.txt, 
> MediaService-dev.aar
>
>
> I am trying to deploy the aar wirtten in wsdl2.0 in the container of Axis2 
> 1.5 with Tomcat5.5. But it always throws below exceptions when tomcat starts 
> up.
> [INFO] AARBasedWSDLLocator: Unable to resolve 
> jar:file://file:/E:/Tools/apache-tomcat-5.5.28/webapps/tnws/WEB-INF/services/MediaService-dev.aar!/META-INF/xsd/tn-services-2.0.xsd
> [WARN] Woden[Warning],0:0,WSDL504,Could not locate the schema document at URL 
> "jar:file://file:/E:/Tools/apache-tomcat-5.5.28/webapps/tnws/WEB-INF/services/Medi
> aService-dev.aar!/META-INF/xsd/tn-services-2.0.xsd",java.util.zip.ZipException:The
>  network path was not found
> [WARN] Woden[Warning],0:0,WSDL504,Could not locate the schema document at URL 
> "http://telenav.com/datatypes/services/v10/",java.net.ConnectException:Connection
>  timed out: connect
> [WARN] Woden[Warning],0:0,Description-1001,The targetNamespace 
> 'http://telenav.com/services/media/v10/' is not dereferencable.
> And then i upgraded all the wonden jars in Axis2 1.5  from 1.0M8 to 
> 1.0-SNAPSHOT and the issue still exists.
> It seems the Axis2 is trying to locate the xsds and eventually failed to 
> locate them but the xsds are really there. The actual full path of the xsd is 
> exactly the same as the exception said. These exception didn't block the 
> service, the service run well even these excetpion are thrown. But it will 
> make the startup of tomcat take long time.

-- 
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