btw - I think I've also just figured out why the old editor is coming up - it seems to happen whenever I try to open a file (using double click) and I've either not got the dev studio dashboard open or I've not got it highlighted as the current perspective. In both of these cases it reverts to the old editor.
cheers for now, John. John Hawkins Director: Solutions Architecture On Fri, Jul 3, 2015 at 12:44 PM, John Hawkins <[email protected]> wrote: > OK, that explains what the editor is :-) > I'm not sure that I was doing anything other than double clicking the > config file (the .xml file ) but I do see that if I explicitly open-with > then it does open up in that editor. > > I've just had a manifestation of the "unable to open editor" problem. The > sequence of events I did was... > 1) create new ESB Config project > 2) Create new Proxy Service. > > If failed to open the editor on the new proxy service. I'm attaching the > .log. The relevant events are at > > 2015-07-03 12:27:22.354 > > which then has a classcastexception following it at > > 2015-07-03 12:27:22:409 > > java.lang.ClassCastException: org.eclipse.ui.internal.ErrorEditorPart > cannot be cast to > org.wso2.developerstudio.eclipse.gmf.esb.diagram.part.EsbMultiPageEditor > > > Looks like a cause perhaps of at least one of the problems? I've had it > before now that if the workspace dies underneath somewhere (like in this > case where an exception happens) then I've had to restart the workspace to > get it working again. Perhaps the classcastexception is the error thats > causing a pyramid of other issues ? > > > many thanks for your help ! > > John. > > > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
