Bug 212508 - [editor] Error parsing messages if WSDL has no targetNamespace attribute
Summary: [editor] Error parsing messages if WSDL has no targetNamespace attribute
Status: NEW
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard:
Keywords: helpwanted
: 314235 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-12-11 03:21 EST by Marco Hala genannt Kahle CLA
Modified: 2011-01-12 11:44 EST (History)
3 users (show)

See Also:


Attachments
Sample WSDL file (1.56 KB, text/xml)
2007-12-11 03:21 EST, Marco Hala genannt Kahle CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Hala genannt Kahle CLA 2007-12-11 03:21:22 EST
Created attachment 84937 [details]
Sample WSDL file

Build ID: 200712062304

Steps To Reproduce:
Please copy the attached WSDL into a workspace and open WSDL editor. Additionally try to validate the file.
The WSDL parser is unable to resolve the messages of the WSDL.  It returns null. The editor shows the same behaviour. Validating the file causes the following error:
Severity and Description	Path	Resource	Location	Creation Time	Id
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.	LocalDevelopment~LocalDevelopment~o~demo.sap.com/rep/ui	noNspService.wsdl	line 1	1197360347307	51


More information:
Comment 1 Valentin Baciu CLA 2007-12-11 14:59:03 EST
I see that the targetNamespace is defined as an optional attribute in the WSDL schema but this is the first example I see where a target namespace is not specified. We'll try to look into it. It it's important to you feel free to investigate - we'll accept quality patches.

The WS-I validator needs to obtain some files (called Test Assertion
Docments) from the internet. These files provide parts of the WS-I validation rules.  For legal reasons these files cannot be redistributed so the WS-I validator has to go off on the internet an fetch them. Can you please make sure you have a connection to the internet from your machine. If you do and the WS-I validator still complains, please check under Preferences->Internet->Cache. Remove all items from the cache and try again.
Comment 2 Marco Hala genannt Kahle CLA 2008-02-08 05:29:09 EST
I have an Internet connection and there is nothing in Cache BUT the parser problem is still there.

Comment 3 Valentin Baciu CLA 2008-11-10 15:32:20 EST
The WSDL editor problem is still there in WTP 3.1. 

The WS-I validator is generating the following warning:

Description	Resource	Path	Location	Type
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The conformance validation process failed.
------------------------------------------------------------------------------
  Nested exception is: 

  java.lang.NullPointerException
The WSDLAnalyzer was unable to validate the given WSDL File.	noNspService.wsdl	212508	line 1	WSDL Problem
Comment 4 Valentin Baciu CLA 2010-05-04 17:34:40 EDT
Still a problem in 3.2 M7. May require fixes in both the editor and WSDL EMF model.
Comment 5 Valentin Baciu CLA 2010-05-25 11:05:51 EDT
*** Bug 314235 has been marked as a duplicate of this bug. ***
Comment 6 Sebastien Tardif CLA 2011-01-12 11:44:48 EST
Same error in 3.2.2 using the latest Eclipse IDE for SOA Developers, and using the provided XML Samples having SpaceWarGame.wsdl.

The thing will look less buggy if at least the samples and made to not hit the bugs. The sample does have a targetNamespace.