[JBoss JIRA] Commented: (RHDS-72) RHDS menu items on Fedora 7
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/RHDS-72?page=comments#action_12372908 ]
Max Andersen commented on RHDS-72:
----------------------------------
what distros are that ?
We got reports from debian, ubuntu and fedora about this....seem pretty consistent.
> RHDS menu items on Fedora 7
> ---------------------------
>
> Key: RHDS-72
> URL: http://jira.jboss.com/jira/browse/RHDS-72
> Project: Red Hat Developer Studio
> Issue Type: Bug
> Affects Versions: 1.0.0.beta1
> Environment: Fedora 7, RHDS nightly 200708080004
> Reporter: Manik Surtani
> Assigned To: Vladimir Ralev
> Fix For: 1.0.0.beta2
>
> Attachments: installer_on_kde, Screenshot.png
>
>
> Using the installer was nice and easy, but when it prompted me to install RHDS in my menu, I opted for it to create it's own group. And it didn't. So here are the list of my gripes with this:
> 1) The default (at least on F7) should be in the "Programming" group, with other dev tools - not it's own RHDS group.
> 2) When it does try and create the RHDS group ( as I opted for) it created a group called "Other" and dumped the menu items in there.
> 3) There were 2 copies of each menu item.
> See screen shot for details of all 3 above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 7 months
[JBoss JIRA] Commented: (RHDS-72) RHDS menu items on Fedora 7
by Vladimir Ralev (JIRA)
[ http://jira.jboss.com/jira/browse/RHDS-72?page=comments#action_12372901 ]
Vladimir Ralev commented on RHDS-72:
------------------------------------
This behavior is definitely no by the xdg menu spec and doesn't happen in the distros we've been testing on the EAP. Anyway, the problem here is that in linux the shortcuts are not assigned to a specific location, they have assigned categories and the parent menu items are actually category aggregators - overlaps and multiple categories are allowed and linux users should be used to this..
The recommended way of installing application externally (not managed by some pack tool - apt/yum/rpm) is to create a top level folder (there is also a back-compatibility reason for this). You can assign a category too or only assign a category without top level program group (set program group to ""), but in linux it's uncommon to have a separate uninstaller shortcut in the categories aggregation menus. If you want to give it a try anyway see the list of available categories and how they are aggregated here http://standards.freedesktop.org/menu-spec/menu-spec-1.0.html
BTW, I think I fixed the issue with showing the items in "Others" now, try to rebuild the installer to verify. I still haven't tested it because of some weird fedora7 download problem.
> RHDS menu items on Fedora 7
> ---------------------------
>
> Key: RHDS-72
> URL: http://jira.jboss.com/jira/browse/RHDS-72
> Project: Red Hat Developer Studio
> Issue Type: Bug
> Affects Versions: 1.0.0.beta1
> Environment: Fedora 7, RHDS nightly 200708080004
> Reporter: Manik Surtani
> Assigned To: Vladimir Ralev
> Fix For: 1.0.0.beta2
>
> Attachments: installer_on_kde, Screenshot.png
>
>
> Using the installer was nice and easy, but when it prompted me to install RHDS in my menu, I opted for it to create it's own group. And it didn't. So here are the list of my gripes with this:
> 1) The default (at least on F7) should be in the "Programming" group, with other dev tools - not it's own RHDS group.
> 2) When it does try and create the RHDS group ( as I opted for) it created a group called "Other" and dumped the menu items in there.
> 3) There were 2 copies of each menu item.
> See screen shot for details of all 3 above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 7 months
[JBoss JIRA] Resolved: (JBIDE-775) DnD doesn't work on Diagram.
by Daniel Azarov (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-775?page=all ]
Daniel Azarov resolved JBIDE-775.
---------------------------------
Resolution: Done
org.jboss.tools.jsf.ui\src\org\jboss\tools\jsf\ui\editor\dnd\FileTransferDropTargetListener.java
org.jboss.tools.jsf.ui\src\org\jboss\tools\jsf\ui\editor\dnd\XModelTransferDropTargetListener.java
org.jboss.tools.struts.ui\src\org\jboss\tools\struts\ui\editor\dnd\FileTransferDropTargetListener.java
org.jboss.tools.struts.ui\src\org\jboss\tools\struts\ui\editor\dnd\XModelTransferDropTargetListener.java
DND.DROP_DEFAULT -> DND.DROP_COPY
Now Struts Diagram Editor doesn't support xhtml files at all.
> DnD doesn't work on Diagram.
> ----------------------------
>
> Key: JBIDE-775
> URL: http://jira.jboss.com/jira/browse/JBIDE-775
> Project: JBoss Tools
> Issue Type: Bug
> Components: JSF
> Affects Versions: 2.0.0.Beta3
> Environment: RHEL
> Reporter: Anton Klimkovich
> Assigned To: Daniel Azarov
> Priority: Critical
> Fix For: 2.0.0.Beta4
>
> Attachments: Npe.txt, Npe2.txt
>
>
> Open faces-config.xml or struts-config.xml
> Make DnD of any page on Diagram
> It doesn't work
> But! If you mysteriously DnD the page on Diagram and then move it there from one place to another some errors will appear.
> Mysteriously DnD can be done if you Drop page close by already existing one.
> Logs of errors are attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 7 months
[JBoss JIRA] Commented: (JBIDE-695) JBoss Server port Monitoring issue
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-695?page=comments#action_12372719 ]
Max Andersen commented on JBIDE-695:
------------------------------------
btw. the following helped me answer the above ;)
http://www.eclipse.org/webtools/initial-contribution/IBM/evalGuides/Serve...
http://yettocome.blogspot.com/2005/12/tomcat-port-monitoring-in-eclipse-w...
> JBoss Server port Monitoring issue
> ----------------------------------
>
> Key: JBIDE-695
> URL: http://jira.jboss.com/jira/browse/JBIDE-695
> Project: JBoss Tools
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 2.0.0.Beta3
> Environment: WindowsXP SP2
> rhds-win32-1.0.0.beta1.jar
> Red Hat Developer Studio
> Version: 1.0.0
> Build: build 209
> JDK 1.5_08
> Reporter: Aliaksey Nis
> Assigned To: Rob Stryker
>
> In RHDS:
> 1. Right click on Jboss server in Server view
> 2. Select Properties
> 3. Select Monitoring , press Add button
> Next exception appear:
> Unhandled event loop exception
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:84)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:72)
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:578)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:938)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:660)
> at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1066)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:871)
> at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:994)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:682)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:630)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:617)
> at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:573)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1368)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1330)
> at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:571)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:251)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1606)
> at org.eclipse.wst.server.ui.internal.viewers.MonitorDialog.createDialogArea(MonitorDialog.java:123)
> at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:752)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1081)
> at org.eclipse.jface.window.Window.open(Window.java:785)
> at org.eclipse.wst.server.ui.internal.viewers.MonitorComposite$2.widgetSelected(MonitorComposite.java:135)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
> at org.eclipse.jface.window.Window.open(Window.java:796)
> at org.eclipse.wst.server.ui.internal.view.servers.PropertiesAction.perform(PropertiesAction.java:36)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
> 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.equinox.launcher.Main.invokeFramework(Main.java:504)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 7 months
[JBoss JIRA] Commented: (JBIDE-695) JBoss Server port Monitoring issue
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-695?page=comments#action_12372718 ]
Max Andersen commented on JBIDE-695:
------------------------------------
Looking in the source the Tomcat server adapter seem to be the one with most advanced/complete set of port setup code.
It is meant to be used by the tcp monitor in WTP.
I added a Tomcat 5 server
Right clicked on it and the monitoring submenu is initially empty (weird wtp ui again IMO)
but if you go into properties there are an Monitoring node. Here you can add ports to be monitored.
Now open the tcp/ip monitor and right click properties and you should see these port being added.
The werid thing is though that just going to localhost:8080 doesn't trigger the monitoring to come into play; you have to use the other port that is shown, e.g. http://localhost:8598 is what i had to go to to see the tcp/ip monitor come into play.
So that makes sense for HTTP...but how this makes sense for internal ports likke ssh, ajp etc. which is contacted by jboss internally - I have no idea yet.
Note: Tomcat adapter actually has alot of nice features; like detecting that ports that it needs are already used (try it - it's nice ;)
> JBoss Server port Monitoring issue
> ----------------------------------
>
> Key: JBIDE-695
> URL: http://jira.jboss.com/jira/browse/JBIDE-695
> Project: JBoss Tools
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 2.0.0.Beta3
> Environment: WindowsXP SP2
> rhds-win32-1.0.0.beta1.jar
> Red Hat Developer Studio
> Version: 1.0.0
> Build: build 209
> JDK 1.5_08
> Reporter: Aliaksey Nis
> Assigned To: Rob Stryker
>
> In RHDS:
> 1. Right click on Jboss server in Server view
> 2. Select Properties
> 3. Select Monitoring , press Add button
> Next exception appear:
> Unhandled event loop exception
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:84)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:72)
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:578)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:938)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:660)
> at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1066)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:871)
> at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:994)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:682)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:630)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:617)
> at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:573)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1368)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1330)
> at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:571)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:251)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1606)
> at org.eclipse.wst.server.ui.internal.viewers.MonitorDialog.createDialogArea(MonitorDialog.java:123)
> at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:752)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1081)
> at org.eclipse.jface.window.Window.open(Window.java:785)
> at org.eclipse.wst.server.ui.internal.viewers.MonitorComposite$2.widgetSelected(MonitorComposite.java:135)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
> at org.eclipse.jface.window.Window.open(Window.java:796)
> at org.eclipse.wst.server.ui.internal.view.servers.PropertiesAction.perform(PropertiesAction.java:36)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
> 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.equinox.launcher.Main.invokeFramework(Main.java:504)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 7 months