Bug 139758 - [editor] Revisit inline schema editor design
Summary: [editor] Revisit inline schema editor design
Status: NEW
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard: reviewed_1.5
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-05-02 13:07 EDT by Lawrence Mandel CLA
Modified: 2010-07-20 11:36 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lawrence Mandel CLA 2006-05-02 13:07:05 EDT
Testing on S-1.5RC2-200605010522, I opened a file in the WSDL editor and clicked the arrow to go into the schema. Once in the schema I could not find a way to get back to the WSDL view.
Comment 1 Lawrence Mandel CLA 2006-05-02 13:26:31 EDT
Of course right after I submitted this I discovered that the inline XSD editor is actually a separate editor now. Seems to me that it's unintuitive to have two editors open for the same file (the XSD editor actually has the same WSDL source view). I think it would be preferable to keep all editing of a single document confined to a single editor. Can a new tab/page be opened in the WSDL editor when editing an inline schema? And I still think there should be some way of hyperlinking from the inline schema view back to the WSDL view.

I've downgraded the severity of the defect to normal and updated the summary.
Comment 2 Richard Mah CLA 2006-06-09 14:13:50 EDT
Let's look at the feedback we get on this issue and revisit our approach.
Comment 3 David Carver CLA 2008-06-28 01:37:55 EDT
Actually, it would be very nice to have this in some tab view instead of opening another editor.   Not sure exactly how to accomplish this, especially since the two design views are pretty different.   The issue is componded when you have multiple schemas from multiple namespaces that you may need to navigate through.   It's not uncommon for me to have a WSDL that may use schemas from about 12 different namespaces.  As you add more and more WS-* specis like WS-Reliable Messaging, and WS-MakeConnection, etc, the problem just grows.