September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12457) changed settings are not used when I let the clone fail (by refusing to store the new host fingerprint)

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12457: ---------------------------------------- Summary: changed settings are not used when I let the clone fail (by refusing to store the new host fingerprint) Key: JBIDE-12457 URL: https://issues.jboss.org/browse/JBIDE-12457 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.2, 3.4.0.M1 If you refuse to store the host key of the new openshift application, the clone will fail. The wizard is then not closed, it stays opened. You may then change the applications settings, but they're not used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] (JBIDE-12069) NPE when cancelling the Domain creation as part of an Application creation

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12069: ------------------------------------- Summary: NPE when cancelling the Domain creation as part of an Application creation Key: JBIDE-12069 URL: https://issues.jboss.org/browse/JBIDE-12069 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.Final java.lang.NullPointerException at org.eclipse.jface.window.Window.initializeBounds(Window.java:758) at org.eclipse.jface.dialogs.Dialog.initializeBounds(Dialog.java:714) at org.eclipse.jface.window.Window.create(Window.java:435) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at org.jboss.tools.openshift.express.internal.ui.action.CreateApplicationAction.run(CreateApplicationAction.java:49) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12116) Cannot cancel Verifying SSH session job's dialog

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12116: --------------------------------------- Summary: Cannot cancel Verifying SSH session job's dialog Key: JBIDE-12116 URL: https://issues.jboss.org/browse/JBIDE-12116 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Fix For: 3.3.1, 3.4.x When the Port forwarding is invoked from Openshift Explorer for the first time a job is triggered (Verifying SSH session to retrieve Application's ports...) and a dialog is displayed. User can run the job on backgroud, show details and cancel the job. However, when Cancel is pressed the Port forwarding dialog is shown anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-12075) UI freeze when opening Create App wizard if user is not connected and password is in secure storage

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12075: ------------------------------------- Summary: UI freeze when opening Create App wizard if user is not connected and password is in secure storage Key: JBIDE-12075 URL: https://issues.jboss.org/browse/JBIDE-12075 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.CR1 If user is not connected and password is in secure store, a connection is attempted, but in the UI thread, not in a background thread/job, leading to UI being frozen until connection on OpenShift is done. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-11970) include runtime jars into java search transparently

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11970: ------------------------------------------- Summary: include runtime jars into java search transparently Key: JBIDE-11970 URL: https://issues.jboss.org/browse/JBIDE-11970 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.4.x I just realized PDE has a way to add source from all plugins into java search - this would be super useful for runtime jars which is not on the classpath. http://www.vogella.com/articles/EclipseCodeAccess/article.html#search_inc... We should investigate how that is done. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-12155) Add "New User Library Fileset" option into Project Archives explorer

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12155: ----------------------------------------- Summary: Add "New User Library Fileset" option into Project Archives explorer Key: JBIDE-12155 URL: https://issues.jboss.org/browse/JBIDE-12155 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 3.3.0.CR1 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Fix For: 3.3.0.Final, 3.4.0.M1 Project Archives view includes option to create new user library fileset for archive. This option is accessible only in archives view, not in explorer. I don't see any reason why this option is not included in archives explorer as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9212) Consider introducing Profiles of AS Server adapteres

by Max Rydahl Andersen (JIRA)

Consider introducing Profiles of AS Server adapteres ---------------------------------------------------- Key: JBIDE-9212 URL: https://issues.jboss.org/browse/JBIDE-9212 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.M3 With all the different combinations of server behaviors and pollers dependent if you are runnig locally, remotely, openshift express or openshift flex it becomes hard to configure/tweak. Idea is to introduce the notion of profiles, provide a set of default ones users can apply in Server Wizard or even in the server editor and allow them to create new ones based on existing ones. These profiles would cover: ports, start/stop behavior, pollers, deployments and launch setup. (more?) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-11439) Improve EJB3 Wizards

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-11439: ---------------------------------------- Summary: Improve EJB3 Wizards Key: JBIDE-11439 URL: https://issues.jboss.org/browse/JBIDE-11439 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: ejb3 Reporter: Rastislav Wagner Assignee: Rob Stryker Fix For: 3.3.0.Beta3 *EJB3 Message Driven Bean:* Wizard doesn't warn user if Name is not specified or Package is set to default. Finish button should be disabled. Wizard doesn't have window title *EJB3 Session Bean:* Same as previous one - Wizard doesn't warn user if Name is not specified or Package is set to default. Finish button should be disabled. Session Bean Wizard has Bean Package, Bean Name fields and Message Driven has Package, Name fields. We should choose only one naming. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9442) Investigate possibility for remote debug launch of app servers

by Rob Stryker (JIRA)

Investigate possibility for remote debug launch of app servers -------------------------------------------------------------- Key: JBIDE-9442 URL: https://issues.jboss.org/browse/JBIDE-9442 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7271) Ensure Tools work with out-of-the-box platforms

by Rob Stryker (JIRA)

Ensure Tools work with out-of-the-box platforms ----------------------------------------------- Key: JBIDE-7271 URL: https://jira.jboss.org/browse/JBIDE-7271 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.CR1 I've recently started re-testing with out-of-the box platforms (EPP, EAP, SOA-P), fresh unzipped installations, and I'm realizing most of them do not have JMX enabled. This is a problem for our tools. It means things like putting the our deployments into a metadata location rather than config/deploy cannot work, because we cannot tell the Deployment Scanner (via JMX) that thats where our deployments are. Also, without JMX enabled, I've noticed my shutdown scripts fail. Originally I thought this was just a toolset issue, but when I started using the command line to see if there was some problem in the tools or not, I started realizing, I have absolutely *NO* idea how to properly shut down these platform servers without modifying property files. IS there a way? Or are all new users of EAP / EPP / SOA-P expected to go expose their jmx console in order to use the ./shutdown.sh script? For EAP and EPP, I am only able to properly shut down the server if I modify the default/conf/props/jmx-console-users.properties file. Is this correct? There is no way to shut down the server from the command line without exposing a user via JMX? When trying SOA-P 5.1, I notice the same behaviour. The shutdown script does not work at all without JMX exposed, *AND*, in this case, the "soa-users.properties" file is the one containing the usernames and passwords admin=admin. A summary, In order to enable *command line* shutdowns (and thus tooling shutdowns), it seems I must modify a properties file (who's name changes between platforms??) to expose the jmx console. So again, I ask, am I doing this right? This is all command-line. The next problem is, assuming all my assumptions are correct, what should our tools do to help users with a fresh *manually downloaded* EAP / EPP / SOA-P installations do to get set up? (As far as I know, JBDS bundles customize the configuration slightly). Should we offer to expose their consoles FOR them by changing this properties file? Or should we simply deploy all objects in server/{config}/deploy instead of in workspace.metadata.folder and use jmx to add that folder to the deployment scanner? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2012