[tibullus]

I could have sworn when i first started using myEclipse that when I clicked on an element in the outline view, it would immediately move to that node in the struts designer. Is there a way that they become unlinked? Is there a way I can make sure that they are linked?

Also, is there a way I can highlight part of the xml file in the source and have it move that part of the struts designer page?

Thanks,

marc

[Brian Fernandes]

Marc,

Clicking a node in the outline view still does move to that node in the designer. There isn’t an option allowing users to disable the synchronization.

What kind of nodes are you clicking (actions, jsps…?); does it not link for all nodes and all your configs or only a few?
I cannot think of why it would stop working, perhaps you could close and re-open the Outline view to make sure.

Finally, please state your Eclipse, MyEclipse and Java versions.

Also, is there a way I can highlight part of the xml file in the source and have it move that part of the struts designer page?

Unfortunately this isn’t a feature we have in our designer, but we’ll keep it in mind.

Best,
Brian.

[tibullus]

Clicking a node in the outline view still does move to that node in the designer. There isn’t an option allowing users to disable the synchronization.

This is the feature that does not appear to be working for me. If I click on a node (any node: actions, jsps, form beans, etc), the corresponding entry in the Outline view will be highlighted. However, if I should happen to click any other entry in the outline view (e.g. another action, a forward, etc) the corresponding entry on the designer screen is not highlighted.

I seem to remember this functionality working at some point in the past, but not it doesn’t seem to work for me anymore.

Finally, please state your Eclipse, MyEclipse and Java versions.

Eclipse SDK
Version: 3.1.0
Build id: I20050617-1618

MyEclipse JSF Support
Version: 3.9.210
Build id: 20050627-4.0-Milestone-2

java version 1.4.2_08-b03

[Riyad Kalla]

tibullus,
You are not using Eclispe 3.1 final release which is what that version of MyEclipse 4.0 Milestone 2 requires, please upgrade to the final Eclipse 3.1 release.

[tibullus]

You are not using Eclispe 3.1 final release which is what that version of MyEclipse 4.0 Milestone 2 requires, please upgrade to the final Eclipse 3.1 release.

I have now gone out and updated my eclipse version, and reinstalled MyEclipse (from a clean state, just to be sure). On the way back in, I noticed the following sequence of events:

1) When I started up MyEclipse, it started on the designer page (that was the last page opened in the project I pointed the fresh MyEclipse at).
2) As it started to load, I noticed that the “Outline” view was thrashing on something. Basically, it seems to keep refreshing over and over and over again (I can tell this because the verticle scrollbar on the right side of the screen keeps disappearing, and then reappearing going from a larger size to a smaller – much like it was being refreshed and rebuilding its content)
3) If I select anything in the outline view at this point, things work as planned
4) If I close the outline view and reopen it (which I have to do because of the resource drain from the constant refreshing), I can no longer select things in the outline and have the designer automatically forward to its corresponding node.

Eclipse SDK
Version: 3.1.0
Build id: I20050627-1435

MyEclipse JSF Support
Version: 3.9.210
Build id: 20050627-4.0-Milestone-2

Java 1.4.2_08

[tibullus]

I dont’t know if this helps, but if I double click on the path of an action in a forward (for instance /dosomething.do) I get an error that reads: “An Error has occurred. See Error log for more details”.

I am unable to locate said error log, otherwise I would include any entries I found in there as well.

Coincidentally, if I click on a jsp, it will take me to the jsp properly.

[Riyad Kalla]

This is sounding very odd… the log file is at: <workspace dir>\.metadata\.log

[tibullus]

The entry that shows up in the log file after the double-click is:

!ENTRY org.eclipse.jface 4 2 2005-07-21 12:34:03.867
!MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.jface”.
!STACK 0
java.lang.NullPointerException
at com.genuitec.eclipse.struts.editor.outline.StrutsConfigNodeDoubleClickListener.openResourceInEditor(StrutsConfigNodeDoubleClickListener.java:71)
at com.genuitec.eclipse.struts.editor.outline.StrutsConfigNodeDoubleClickListener.doubleClick(StrutsConfigNodeDoubleClickListener.java:48)
at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:720)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)
at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:718)
at org.eclipse.jface.viewers.StructuredViewer.handleDoubleSelect(StructuredViewer.java:950)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1057)
at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:219)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:216)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:275)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3080)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2713)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)

The only other message in the log that would indicate the original problem was:

!ENTRY org.eclipse.core.resources 2 10035 2005-07-21 10:31:20.402
!MESSAGE A workspace crash was detected. The previous session did not exit normally.

[Author]

Posts