Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337945 - No validation on schema for change def tns prefix
Summary: No validation on schema for change def tns prefix
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: WTP Incubator (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Dimitar Tenev CLA
QA Contact: Dimitar Tenev CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-23 04:47 EST by Stanislav Nichev CLA
Modified: 2021-11-18 16:19 EST (History)
0 users

See Also:


Attachments
reproduce data (687 bytes, application/x-zip-compressed)
2011-02-23 04:48 EST, Stanislav Nichev CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Nichev CLA 2011-02-23 04:47:49 EST
Build Identifier: 

Hi Colleagues,                                                          
                                                                        
In SIE 731 the following scenario fails:                                
1) Open the attached WSDL in the SIE                                    
2) Go to the source tab                                                 
3) Go to the xmlns:tns prefix of the definition and update its value    
4) Go to the DT tab                                                     
5) 4 errors on the WSDL elements shown in the title bar               
6) No validation errors on the namespace, although it is broken as  
well                                                                    
                                                                        
There is already developed fix for the problem. It can be found   
here: ObjectsForResolveUtils#a                                          
reDestinationSchemaPrefixAndNamespaceValid.                             
The "if true return true" should be removed.                            
                                                                        
ObjectsForResolveUtils#processComplexTypeDefinition should be updated   
with above method. As a hint - the complexType/complexContent/{extension
base=""    restriction base=""} element should be checked for the       
attribute base.                                                         
                                                                        
The above fix works fine on breaking the prefix value. Undo/redo,       
however, is not working. The undo of the operation is sending a         
notification on the Definition. The definition is not starting the      
validation on the containing namespaces.                                
Because of that - the error markers are not removed.                    
                                                                        
Regards,                                                                
Stanislav                                                               


Reproducible: Always
Comment 1 Stanislav Nichev CLA 2011-02-23 04:48:08 EST
Created attachment 189581 [details]
reproduce data