This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 250474 - [editor] Properties view broken after using inline schema editor
Summary: [editor] Properties view broken after using inline schema editor
Status: CLOSED FIXED
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.1 M4   Edit
Assignee: Amy Wu CLA
QA Contact: Valentin Baciu CLA
URL:
Whiteboard: investigate for 3.1
Keywords:
Depends on: 245155
Blocks:
  Show dependency tree
 
Reported: 2008-10-10 13:42 EDT by Valentin Baciu CLA
Modified: 2008-12-11 21:57 EST (History)
0 users

See Also:

Attachments
Stack trace (2.94 KB, text/plain)
2008-10-10 13:54 EDT, Valentin Baciu CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Baciu CLA 2008-10-10 13:42:09 EDT 
Create a new wsdl file using all the defaults. 
Click on the blue arrow to go to the inline schema editor for the input message element. 
Close the inline schema editor. 
Notice the properties view believes the portType is selected and there are three tabs but only the first has a label. 
Clicking on the other reveals that they also have names but the names are hidden until you click on them. 
Things are pretty much broken after that in the properties view.

Closing and re-opening the editor restore the properties view functional again.

This seems to be a regression from 3.0.3, would be worthwhile checking previous 3.1 M builds.
Comment 1 Valentin Baciu CLA 2008-10-10 13:54:00 EDT 
Created attachment 114823 [details]
Stack trace

This type of exception shows up in the PDE log. Perhaps this is due to some change in the platform code?
Comment 2 Valentin Baciu CLA 2008-12-09 16:19:15 EST 
This could be caused by the same issue as bug 245155. We should re-test with the latest platform.
Comment 3 Valentin Baciu CLA 2008-12-11 21:56:23 EST 
This seems to be fixed in I-3.1-20081210171403.
Comment 4 Valentin Baciu CLA 2008-12-11 21:57:02 EST 
Closing.