This is a "common" bug in .NET services where it uses a construct like:
<element type="s:schema" ..../> but doesn't import the schema namespace itself into the schema. There are two options: 1) Add an <import namespace="http://www.w3.org/2001/XMLSchema"; location="....."/> 2) Change the above to something like: <xsd:any /> or something that is generic. The downside of (1) is that it will generate a ton of useless code if you wsdl2java it. However, it likely is more "proper". Dan On Wednesday, May 04, 2011 7:17:15 AM DharmalingamP wrote: > Hi, > > I need to create a Web Service Client for an external .NET web service. > The Eclipse is showing the following error in WSDL and couldn't create the > web service client. > > src-resolve.4.2: Error resolving component 's:schema'. It was detected that > 's:schema' is in namespace 'http://www.w3.org/2001/XMLSchema', but > components from this namespace are not referenceable from schema document > 'file:/// > > C:/Workspace_Webservices/SampleClient/WebContent/META-INF/wsdl/Sample.wsdl' > . If this is the incorrect namespace, perhaps the prefix of 's:schema' > needs to be changed. If this is the correct namespace, then an appropriate > 'import' tag should be added to > 'file:///C:/Workspace_Webservices/SampleClient/WebContent/META-INF/wsdl/Sam > ple.wsdl'. > > My environment details: > Tomcat 6.0, Apache CXF 2.3.0 > > Please anybody help me out. Thanks in advance. > > Thanks and Regards, > Dharmalingam P. > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/src-resolve-4-2-Error-resolving-component- > s-schema-tp4369529p4369529.html Sent from the cxf-issues mailing list > archive at Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
