Community
Participate
Working Groups
In the WSDL editor's graphical hit Ctrl+A or select Edit->Select All The action fails and the following is logged in the PDE log: null Error Fri Oct 17 11:06:48 EDT 2008 Failed to execute item selectAll Same issue is still present in WTP 3.1 M3.
Created attachment 123960 [details] Apply to org.eclipse.wst.wsdl.ui
Can we target this fix for 3.1M5 ?
Keith, thank you for the patch but I think this needs a bit more thought. The implementation of the select all action in the proposed patch recursively adds all figures to the selection. I'm thinking this is too much - perhaps it should only select the top level objects? One think I tried was to invoke delete after select all and got some NPEs. I'll attach a stack.
Created attachment 123994 [details] Stack with NPE on delete after select all.
I just noticed that the cut/copy/paste don't really work in the design view either... :-(
Hi Valentin, that's what select all is supposed to do. ;-) Notice that in the XML Editor's design view, expand the tree and do a Select All. The children are also selected. (The actions don't seem to work either.) I was aware of this follow-on problem that you found and I've already opened a bug against the XSD Editor about this. (I didn't open one yet for the WSDL Editor) See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=262684 Note that in the schema editor's index view, it doesn't make sense to select the categories, because you shouldn't be allowed to delete them. Anything else should be selected. Also in the details view.
The reason I thought selecting the top level objects should be enough is because they aggregate all their content. Any action on a selection that includes a top level object- like cut/copy/paste/delete - would act on the top level object and implicitly/recursively on their contents. For example, if you select/delete a service, all its ports go away too. It would be interesting to see if selecting only top level objects and deleting them still causes grief in the delete action. I would think the error log message reported initially is more benign than the NPE during delete.
