Community
Participate
Working Groups
In the previous version of web tools, the whole schema could be displayed as a tree. In the new version I can only see the subnodes of the currently selected node. I would like to see the whole schema structure in one view, like it was possible in the previous version.
I voted for this because I was deeply disappointed at the removal of this feature for 1.5. I guess I don't understand the removal of something so helpful to visualizing the schema (in terms of how an XML instance would look) - this type of view is why XMLSpy is so popular and useful. Perhaps it's not as technically correct, but it does allow one to more quickly understand the schema as a whole, by allowing the user to browse the schema in an instance-focused way. Please bring it back, at least as another optional view.
*** Bug 172170 has been marked as a duplicate of this bug. ***
I voted for this as well and would like to say that I completely agree with Dallas Vaughan. Replacing the current view with the original treeview might meet objection, but I don't see why the treeview shouldn't be available as an optional view. What harm would that do? The treeview code already exists anyway so it shouldn't be a great deal of work to bring this feature back again. I liked the treeview a lot and was very disappointed when I realized it had been replaced and I cannot help but add that I'm unable to understand how this change could be carried out in the first place. To my mind, if asked whether they wanted the treeview out, 100 out of 100 XML developers would say that they insisted on this view. It's deprecation is just about as baffling to me as if a UML plugin vendor had replaced it's graphical UML views with advertisements for crayons.
*** Bug 185217 has been marked as a duplicate of this bug. ***
An alternative suggestion would be to allow the number of nodes or (classes) displayed to be user configurable. Typically, when looking at a schema graphically it is not uncommon to want to see more of the complexTypes and elements in use than what is currently shown. The prior versions from 0.7 and 1.0 showed a more traditional XML Spy/Oxygen XML/Stylus Studio view. The current view is more of a UML class diagram view, which while useful, may not necessarily give a good view for those that aren't familiar with UML Class diagrams.
This feature is really useful and this is the only reason why we stay on Eclipse 3.1 at work (french Department of Justice). We have dozens of inter-linked XSD files and the new view is almost unusable... I suggest to increase the priority of that bug.
Vote for it .. I really miss this feature. Are there specific technical, political or licensing reasons why this feature is not available anymore? What are the barriers to re-introduce the tree view? Regards, Oben
Is there an workaround for this issue. Can users who want the features roll to older version by some means?
the outline-view like it is makes it very difficult to access nested local element definitions.
*** Bug 288578 has been marked as a duplicate of this bug. ***
