[JBoss JIRA] (JBDS-3475) Rename FeedHenry references to RHMAP
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBDS-3475:
----------------------------------
Summary: Rename FeedHenry references to RHMAP
Key: JBDS-3475
URL: https://issues.jboss.org/browse/JBDS-3475
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: aerogear-hybrid
Affects Versions: 9.0.0.Beta1
Reporter: Gorkem Ercan
Assignee: Max Rydahl Andersen
Feedhenry is now called Red Hat Mobile Application Platform adjust branding accordingly
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-19850:
---------------------------------------
[~maxandersen] [~adietish] Worked through my functional testing and it seems like it all works the best I would expect, including the various error conditions. Additionally, added a handler that stops the port forwarding when you terminate the console.
> As a user I want to easily set up port forwarding for my application
> --------------------------------------------------------------------
>
> Key: JBIDE-19850
> URL: https://issues.jboss.org/browse/JBIDE-19850
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Blocker
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.0.Beta2
>
>
> As a user I want to be able to easily set up port forwarding to my application
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20108:
-------------------------------------
There's been no significant changes between b1 and master, so I doubt that's the issue.
> Cannot connect to remote server in JMX Navigator - Authentication fails
> -----------------------------------------------------------------------
>
> Key: JBIDE-20108
> URL: https://issues.jboss.org/browse/JBIDE-20108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> When I try to connect to a remote server via JMX Navigator, it fails on authentication:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854
> !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin
> !STACK 1
> org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> ... 7 more
> !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854
> !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> !STACK 0
> javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work.
> Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server without runtime in JMX Navigator
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
Ok, I've done some more testing, and I'm not sure where you'd like to see a warning here, [~mmalina].
The (bad) idea I was just testing out was to always show the connect / disconnect menu actions, but have them enabled / disabled, and use a tooltip text if the action is disabled.
Problem is, 1) I've never seen any menu action have a tooltip before, and 2) it doesn't seem to work anyway.
So it seems that's not a valid option really ;)
I think it'd be wrong to have the actions always enabled and show a messagebox on failure. If we know in advance the action won't work, it seems wrong to show it enabled.
So... any ideas how you'd like to see this warning displayed?
> Cannot connect to remote server without runtime in JMX Navigator
> ----------------------------------------------------------------
>
> Key: JBIDE-19463
> URL: https://issues.jboss.org/browse/JBIDE-19463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
>
> When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item.
> For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19934) NPE when opening a HTML file
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19934?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19934:
-----------------------------------------------
PaletteModelImpl has 11 methods with code
{code}
if(paletteContents != null){
... paletteContents.getFile() ...
}
{code}
that call methods on file object without checking file for null (one case is now checked).
I suggest adding method
{code}
IFile getFile() {
return (paletteContents != null) ? paletteContents.getFile() : null;
}
{code}
and replacing mentioned code with
{code}
IFile f = getFile();
if(f != null) {
...
}
{code}
> NPE when opening a HTML file
> ----------------------------
>
> Key: JBIDE-19934
> URL: https://issues.jboss.org/browse/JBIDE-19934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2, 4.3.0.Beta1
> Reporter: Gorkem Ercan
> Assignee: Daniel Azarov
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> Got the following NPE when opening a view on an angular/hybrid mobile project. I do not think it is related to angular though.
> eclipse.buildId=unknown
> java.version=1.8.0_25
> java.vendor=Oracle Corporation
> org.eclipse.ui.workbench
> Error
> Thu Jun 04 11:10:36 EDT 2015
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.palette.internal.html.impl.PaletteModelImpl.getPreferredExpandedCategory(PaletteModelImpl.java:214)
> at org.jboss.tools.jst.web.ui.palette.model.PaletteModel$PL.partActivated(PaletteModel.java:140)
> at org.eclipse.ui.internal.PartService$1.run(PartService.java:84)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81)
> at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3056)
> at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4813)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4810)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4798)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:242)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:239)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:702)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:630)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:625)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3195)
> at org.eclipse.ui.internal.WorkbenchPage.access$24(WorkbenchPage.java:3102)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3084)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3079)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3043)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3033)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:360)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:167)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:268)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:233)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
> at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50)
> at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:229)
> at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:854)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:851)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1168)
> at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:449)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1275)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server without runtime in JMX Navigator
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
So I've looked into this a bit, and I'm not sure what a good solution here is.
I could modify the IConnectionWrapper interface, to change public boolean canControl(); to public IStatus canControl(), but this would be an API change on an interface that hasn't had a method added since 2012, with previous changes back in 2008.
Alternately, we could add a new interface with one method in it, but, that always seems a bit drastic, and if this course were taken every time we needed an API change, we'd have lots more single-method interfaces.
The first option could break other extenders of ours, but we're not actually aware of any such extenders, so maybe we just don't care ;) I'll work on a patch to the interface, because something about making a new interface for one method seems wrong to me.
> Cannot connect to remote server without runtime in JMX Navigator
> ----------------------------------------------------------------
>
> Key: JBIDE-19463
> URL: https://issues.jboss.org/browse/JBIDE-19463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
>
> When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item.
> For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months