November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12650) Detecting server ports from local runtime does not account for configured port-offset

by Ozan Ayyüce (JIRA)

Ozan Ayyüce created JBIDE-12650: ----------------------------------- Summary: Detecting server ports from local runtime does not account for configured port-offset Key: JBIDE-12650 URL: https://issues.jboss.org/browse/JBIDE-12650 Project: Tools (JBoss Tools) Issue Type: Bug Environment: eclipse juno, jboss-as-7.1.1.Final, jboss as tools Reporter: Ozan Ayyüce Priority: Minor When socket-binding in standalone.xml is configured with a port-offset other than 0, the server ports are not detected correctly in the server configuration view. The server startup is not detected also. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

6
9
0 / 0

[JBoss JIRA] (JBIDE-12424) Specifying a non-default configuration file in non-default profile doesn't work as expected via JBDS 5

by Usman Saleem (JIRA)

Usman Saleem created JBIDE-12424: ------------------------------------ Summary: Specifying a non-default configuration file in non-default profile doesn't work as expected via JBDS 5 Key: JBIDE-12424 URL: https://issues.jboss.org/browse/JBIDE-12424 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Final Reporter: Usman Saleem Assignee: Rob Stryker Specifying a non-default configuration file in non-default profile doesn't work as expected via JBDS 5. When attempt to start the server, following error is raised: The server's configuration file does not exist: /jbeap6/standalone/configuration/jbeap6/custom/configuration/standalone-full-ha.xml Looks like jboss tool automatically appending /jbeap6/standalone/configuration Note that the custom configuration can be launched via command line as: ./standalone.sh -Djboss.server.base.dir=../custom --server-config=standalone-full-ha.xml -- 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, 5 months

5
10
0 / 0

[JBoss JIRA] (JBIDE-13026) new xpath query in servers view not setting all properties from dialog

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-13026: ----------------------------------- Summary: new xpath query in servers view not setting all properties from dialog Key: JBIDE-13026 URL: https://issues.jboss.org/browse/JBIDE-13026 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.0.Alpha2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.CR1 Steps to reproduce: 1) Create an as71 server 2) expand the server in servers view 3) expand the XML Configuration, then expand PORTS 4) right-click on ports, select "new xpath" 5) Fill with details as follows a) name: blahblah (whatever) b) root dir: (blank) c) file pattern: standalone/configuration/${jboss_config_file} d) xpath pattern: //*[local-name()="socket-binding-group"] e) xpath attribute: port-offset 6) save xpath 7) look in view, ensure new xpath appearsr 8) look NEXT to new xpath (decorator, grey text), make sure value reads ${jboss.socket.binding.port-offset:0} [FAIL] 9) right-click new query, click 'edit xpath' 10) Ensure name, root dir, file pattern, xpath pattern, xpath attribute, are as expected [FAIL] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-13045) remote start of as7.0.1 includes -b flag when 7.0.1 does not support -b flag

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-13045: ----------------------------------- Summary: remote start of as7.0.1 includes -b flag when 7.0.1 does not support -b flag Key: JBIDE-13045 URL: https://issues.jboss.org/browse/JBIDE-13045 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.0.Beta2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.0.CR1 Top description seems to indicate it all really. create a local 7.0.1 jboss as server, associate it with a remote of the same version, set to rse mode, etc, and then click on the launch configuration link. If you see a -b flag, it is wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8492) Tools claim server to be running when startup failed on remote host

by Libor Zoubek (JIRA)

Tools claim server to be running when startup failed on remote host ------------------------------------------------------------------- Key: JBIDE-8492 URL: https://issues.jboss.org/browse/JBIDE-8492 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Final Reporter: Libor Zoubek Assignee: Rob Stryker -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

7
11
0 / 0

[JBoss JIRA] (JBDS-2366) Improve libs import for EAP 6

by William Siqueira (JIRA)

William Siqueira created JBDS-2366: -------------------------------------- Summary: Improve libs import for EAP 6 Key: JBDS-2366 URL: https://issues.jboss.org/browse/JBDS-2366 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: libmanagement, servers Affects Versions: 5.0.0.GA Environment: JBDS 4.x EAP 6/AS 7 Reporter: William Siqueira In previous version of EAP, we could create a LIB and all our JARs files to the application build path, so we didn't have problem with imports. in EAP 6(AS 7), we have the modules new concept. The problem is that when migrating from older EAP version to EAP 6, we have to create modules to represent our libs and when setting a server to your project, it is not bringing our custom modules which our application is dependent. What is needed is a way to select which modules will be in the project classpath whn adding a server lib to the project or perhaps automatically import all modules based on the jboss-deployment-structure.xml descriptor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-13056) NPE when invoking Mapping diagram when model doesn't correspond with DB

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13056: ------------------------------------ Summary: NPE when invoking Mapping diagram when model doesn't correspond with DB Key: JBIDE-13056 URL: https://issues.jboss.org/browse/JBIDE-13056 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.0.0.Beta2 Environment: JBDS 6.0.0.Beta2,Linux 64 Reporter: Jiri Peterka Assignee: Jiri Peterka Fix For: 4.0.0.CR1 There is NPE when starting Mapping Diagram with different schemas {code} !ENTRY org.eclipse.ui 4 0 2012-11-13 12:13:06.965 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at org.jboss.tools.hibernate.ui.diagram.editors.model.ElementsFactory.createForeingKeyConnections(ElementsFactory.java:81) at org.jboss.tools.hibernate.ui.diagram.editors.model.OrmDiagram.recreateChildren(OrmDiagram.java:231) at org.jboss.tools.hibernate.ui.diagram.editors.model.OrmDiagram.<init>(OrmDiagram.java:156) at org.jboss.tools.hibernate.ui.view.DiagramEditorInput.createOrmDiagram(DiagramEditorInput.java:68) at org.jboss.tools.hibernate.ui.view.DiagramEditorInput.<init>(DiagramEditorInput.java:64) at org.jboss.tools.hibernate.ui.view.OpenDiagramActionDelegate.openEditor(OpenDiagramActionDelegate.java:127) at org.jboss.tools.hibernate.ui.view.OpenDiagramActionDelegate.run(OpenDiagramActionDelegate.java:105) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251) 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.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54) 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:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBDS-2283) Investigate use of Eclipse-cs 5.5 in JBoss Central & JBDS Extras sites

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2283: -------------------------------- Summary: Investigate use of Eclipse-cs 5.5 in JBoss Central & JBDS Extras sites Key: JBDS-2283 URL: https://issues.jboss.org/browse/JBDS-2283 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, central Affects Versions: 6.0.0.Alpha1 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 6.0.0.Beta1 Mirrored bits are here: http://download.jboss.org/jbosstools/updates/requirements/eclipsecs/5.5.0... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-12911) CLONE - Review error handling code in as plugins

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-12911: ------------------------------------- Summary: CLONE - Review error handling code in as plugins Key: JBIDE-12911 URL: https://issues.jboss.org/browse/JBIDE-12911 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Andre Dietisheim Assignee: Andre Dietisheim Please review the error handling code in JBossAS plugin. I replaced a lot of e.printStackTrace() (in JBIDE-8434) by proper logging. I might have missed some, in some cases more handling is needed, some might not be correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

6
11
0 / 0

[JBoss JIRA] (JBIDE-10116) Issues that affect AS7/EAP integration to tools

by Max Rydahl Andersen (Created) (JIRA)

Issues that affect AS7/EAP integration to tools ----------------------------------------------- Key: JBIDE-10116 URL: https://issues.jboss.org/browse/JBIDE-10116 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta1 -- 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, 5 months

5
10
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 November 2012