[news.eclipse.webtools] Help with WSDL validation error

[Mauro Molinari <mauro.molinari@xxxxxxxxxxxx>]

Hello!
After creating a WSDL from a Java class using Axis2 1.3 Eclipse plugin, 
I get a WSDL file on which Eclipse gives me a validation error:

src-resolve.4.2: Error resolving component 
'ns0:FailedConfigurationException'. It was detected that 
'ns0:FailedConfigurationException' is in namespace 
'http://ticketFramework.webservice.cardinis.com/xsd', but components 
from this namespace are not referenceable from schema document 
'file:///C:/<complete-path>/WEB-INF/services/accessServices/META-INF/accessServices.wsdl'. 
If this is the incorrect namespace, perhaps the prefix of 
'ns0:FailedConfigurationException' needs to be changed. If this is the 
correct namespace, then an appropriate 'import' tag should be added to 
'file:///C:/<complete-path>/WEB-INF/services/accessServices/META-INF/accessServices.wsdl'.

What does this error mean? Why is it given?

This is a fragment of the WSDL:

<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
 xmlns:axis2="http://access.webservice.cardinis.cardinis.com";
 xmlns:ns1="http://access.webservice.cardinis.cardinis.com/xsd";
 xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
 xmlns:ns0="http://ticketFramework.webservice.cardinis.com/xsd";
 xmlns:xs="http://www.w3.org/2001/XMLSchema";
 xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
 xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
 targetNamespace="http://access.webservice.cardinis.cardinis.com";>
 <wsdl:types>
  <xs:schema
   xmlns:ax21="http://ticketFramework.webservice.cardinis.com/xsd";
   attributeFormDefault="qualified" elementFormDefault="qualified"
   targetNamespace="http://ticketFramework.webservice.cardinis.com/xsd";>
   <xs:complexType name="FailedConfigurationException">
    <xs:complexContent>
     <xs:extension base="ns1:Exception">
      <xs:sequence />
     </xs:extension>
    </xs:complexContent>
   </xs:complexType>
[...]

Any suggestion would be really appreciated.

Mauro.