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

Raghu Kodumuri resolved AXIS-2592.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.1

> Generated Client WSDL is not valid
> ----------------------------------
>
>                 Key: AXIS-2592
>                 URL: https://issues.apache.org/jira/browse/AXIS-2592
>             Project: Axis
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: Windows XP, Java 1.5 and Eclipse 3.2.1 & Sun JavaCAPS
>            Reporter: Raghu Kodumuri
>             Fix For: 1.2.1
>
>         Attachments: ProjectStatistics.wsdl, ProjectStatistics1.wsdl
>
>
> WSDL clinet that has been generated using Axis 1.2.1 and generated wsdl can 
> not be validated by XMP SPY or Eclipse Wsdl validator. Here are the errors:
> XML SPY :
> File C:\slbProjects\IntroSpection\ProjectStatisticsNew\ProjectStatistics.wsdl 
> is not valid.
>       The selector './/xs:key|.//xs:unique|.//xs:keyref' of identity 
> constraint 'xsd:identityConstraint' must evaluate to a target node set.
>               Error location: wsdl:definitions / wsdl:types / schema
>               Details
>                       cvc-identity-constraint.1: The selector 
> './/xs:key|.//xs:unique|.//xs:keyref' of identity constraint 
> 'xsd:identityConstraint' must evaluate to a target node set.
> Eclipse Validator:
> 1. ComplexType declared in schema are not visible in wsdl part type. 
> Actual Error:The part 'getActiveVesselReturn' has an invalid value 'string' 
> defined for its type. Type declarations must refer to valid values defined in 
> a schema.
> 2. Complains xmlns datatype are not in schema:
> Error: The part 'getActiveVesselReturn' has an invalid value 'string' defined 
> for its type. Type declarations must refer to valid values defined in a 
> schema.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to