Today, for one of the tasks i need one sample WSDL so that i can create some mock service in SOAP UI. As usual wanted to leverage google search capabilities 
for the same, instead of coming up with one on my own.
I have taken one of the WSDLs given in w3.org to my eclipse. I am surprised to see the errors given by eclipse for the WSDL. I made sure that the WSDL structure, namespace aliases etc. are given correctly.On careful examination of the inline XSD given in the WSDL, found the issue is with the namespace which is given as http://www.w3.org/1999/XMLSchema.
Modifying this namespace to http://www.w3.org/2001/XMLSchema resolved the error.
So the moral of the story is that some times blind copy does not give the intended time saving benefits as we expect.
Siva's Blog 
one doubt sir…
do you think this is the issue with namespace. Namespace is only used for unique identification.
or is it that eclipse interprets only this(http://www.w3.org/2001/XMLSchema) namespace.
Why the eclipse does not understand if it’s a standard?http://www.w3.org/2001/XMLSchema is different from http://www.w3.org/1999/XMLSchema and we can’t use a complex type defined in one namespace when wsdl is expecting complex type from another namespace.http://www.w3.org/1999/XMLSchema is the old namespace and we should not use it any longer.