September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9335) Multiple detected runtime indexes miss the brackets

by Jiri Peterka (JIRA)

Multiple detected runtime indexes miss the brackets --------------------------------------------------- Key: JBIDE-9335 URL: https://issues.jboss.org/browse/JBIDE-9335 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.3.0.M2 Reporter: Jiri Peterka Assignee: Snjezana Peco Fix For: 3.3.0.M3 Runtime detection should improve indexing of multiple servers - brackets should be added Currently it's: jboss-eap-4.0 jboss-eap-4.0 1 jboss-eap-4.0 2 jboss-soa-p5 jboss-soa-p5 1 jboss-soa-p5 2 Should be rather like this: jboss-eap-4.0 jboss-eap-4.0(2) jboss-eap-4.0(3) jboss-soa-p5 jboss-soa-p5(2) jboss-soa-p5(3) Consider indexing from 1 (not from 0) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9376) Create OpenShift Express Server Type

by Max Rydahl Andersen (JIRA)

Create OpenShift Express Server Type ------------------------------------ Key: JBIDE-9376 URL: https://issues.jboss.org/browse/JBIDE-9376 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta1, 3.3.0.M3 If we treat OpenShift as a server without runtime, we can just use hardcoded defaults for openshift and remove alot of UI -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9229) [P2/UpdateSite] Add 'Web Services Tools' and 'JAX-RS Tools' into the 'Web and Java EE development category'

by Xavier Coulon (JIRA)

[P2/UpdateSite] Add 'Web Services Tools' and 'JAX-RS Tools' into the 'Web and Java EE development category' ----------------------------------------------------------------------------------------------------------- Key: JBIDE-9229 URL: https://issues.jboss.org/browse/JBIDE-9229 Project: Tools (JBoss Tools) Issue Type: Task Components: Webservices Affects Versions: 3.3.0.M1 Reporter: Xavier Coulon Assignee: Nick Boldt Looking at the at nightly stable JBossTools P2 repository (jbosstools - http://download.jboss.org/jbosstools/updates/nightly/3.3_stable_branch/), I noticed that the 'JBoss Web Services tools' and 'JBoss JAX-RS Tools' are not part of the "Web and Java EE Development". The only way to find them is to look into the "All JBoss Tools 3.3" category. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9251) hyperlink window should not contain duplicit entries

by Lukas Jungmann (JIRA)

hyperlink window should not contain duplicit entries ---------------------------------------------------- Key: JBIDE-9251 URL: https://issues.jboss.org/browse/JBIDE-9251 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Lukas Jungmann Assignee: Alexey Kazakov -open http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/unwraps.html -create class: {code} package com.acme; @SessionScoped public class PermissionManager { Permission permission; void setPermission(Permission permission) { this.permission=permission; } @Unwraps //@Current Permission getPermission() { return this.permission; } } {code} -create class: {code} package com.acme; @SessionScoped class SecurityManager { @Inject //@Current Permission permission; boolean checkAdminPermission() { return permission.getName().equals("admin"); } } {code} -make sure that "@Current" is commented out -open hyperlink window on @Current in SecurityManager => popup shows 3 entries for PM.getPermission() but only one should be shown instead see attached screenshot -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9428) Support injection of Provider<X> beans

by Viacheslav Kabanovich (JIRA)

Support injection of Provider<X> beans -------------------------------------- Key: JBIDE-9428 URL: https://issues.jboss.org/browse/JBIDE-9428 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 3.3.0.M2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 5.6.2. The built-in Instance The container must provide a built-in bean with: • Instance<X> and Provider<X> for every legal bean type X in its set of bean types, • every qualifier type in its set of qualifier types, • scope @Dependent, • no bean EL name, and • an implementation provided automatically by the container. Since Instance extends Provider, CDI implementations are likely to just implement Instance interface, which automatically supports injections of Provider<X> as well as that of Instance<X>. So, in practice, there is no difference between these two injections, but formally, Provider interface misses methods narrowing the set of eligible beans and methods for checking if that set is ambiguous or unsatisfied; the only method get() throws RuntimeException in such cases, so that it is logical to perform validation of Provider<X> injection in the same way as X injection. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9342) @Inject Instance<BeanType> should be validate

by Alexey Kazakov (JIRA)

@Inject Instance<BeanType> should be validate --------------------------------------------- Key: JBIDE-9342 URL: https://issues.jboss.org/browse/JBIDE-9342 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M3 Suppose we have the following injection: {code} @Inject @Sync Instance<PaymentProcessor> paymentProcessor; {code} and if there is no bean with qualifier @Sync and type PaymentProcessor available then CDI validator should mark such a injection as unsatisfied. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9354) Stopping JBoss 5.1 server Fails in about 3 different ways!

by Rob Stryker (JIRA)

Stopping JBoss 5.1 server Fails in about 3 different ways! ---------------------------------------------------------- Key: JBIDE-9354 URL: https://issues.jboss.org/browse/JBIDE-9354 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Rob Stryker Assignee: Andre Dietisheim Fix For: 3.3.0.M3 Stopping a JBoss 5.1 server comes up with the dialog introduced in JBIDE-9243. This dialog was meant to give users the option of what to do in the case of a server STARTUP and the server was already up. This should not be showing during a SHUTDOWN. The reason it shows during the shutdown is because StopLaunchConfiguration, a class marked deprecated and unused, is in fact used. This class, StopLaunchConfiguration, EXTENDS a class named AbstractJBossStartLaunchConfiguration, including the new methods for what to do during STARTUP in the even the server is ALREADY STARTED Additionally, after correcting the preLaunchCheck for StopLaunchConfiguration, an attempt to stop the server was *always* receiving a failing dialog, even though the server would eventually shut down. The reason for this is that the stop code in LocalJBossBehaviorDelegate.gracefullStop$Thread.run included the following code: if (stopProcess.getExitValue() == 0) { if( isProcessRunning()) { // cancel the stop, say it failed, etc } } This code will *ALWAYS* misread a stop as a fail because the process that is launched to initiate the stop will finish in under 1 second, while the actual SERVER process may take 5 or 6 seconds to shut down. Therefore, after the stop process is launched, and finishes, with an exit code of 0 (no error), the process is ALWAYS still running. I am correcting the following: 1) Overriding the preLaunchCheck in StopLaunchCOnfiguration 2) I am replacing the faulty logic for recognizing a failed stop with proper logic to ONLY respond if the exit code is NOT 0 3) I am expecting Andre to PROPERLY mark as deprecated or NOT deprecated the class StopLaunchConfiguration. It is currently marked deprecated, but it is still in use, and inherits from AbstractJBossStartLaunchConfiguration. A review will be necessary to see if it makes sense for StopLaunchConfiguration to inherit from a class named AbstractJBossStartLaunchConfiguration. And finally, changes that seem like they make no difference and are just code cleanup / re-organization *STILL* require SMOKE TESTS before commits. This is to make sure you didn't accidentally break something, like startup and shutdown of every server type. A bad build hinders QE's work for a full day and can cause tons of other problems. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9546) Reorganize synchronization in CDIProject

by Fisheye JIRA Integration (JIRA)

Reorganize synchronization in CDIProject ---------------------------------------- Key: JBIDE-9546 URL: https://issues.jboss.org/browse/JBIDE-9546 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.3.0.M3 Reporter: Fisheye JIRA Integration Fix For: 3.3.0.M3 Created by Alexey Kazakov from Denis Golovin's Crucible comment on CDIProject.java lines 1174-1194 https://source.jboss.org/cru/REV-JBIDE-8#c87 : It looks wrong, it rather should be in one synchronized(this) block {code} synchronized (beansByPath) { beansByPath.clear(); } synchronized (beansByName) { beansByName.clear(); } synchronized (namedBeans) { namedBeans.clear(); } synchronized (alternatives) { alternatives.clear(); } synchronized (decorators) { decorators.clear(); } synchronized (interceptors) { interceptors.clear(); } synchronized (allBeans) { allBeans.clear(); }{code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9476) Quick fix should be aware of bean producers in case of ambiguous dependency

by Alexey Kazakov (JIRA)

Quick fix should be aware of bean producers in case of ambiguous dependency --------------------------------------------------------------------------- Key: JBIDE-9476 URL: https://issues.jboss.org/browse/JBIDE-9476 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.M4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9284) AS7 launch configuration can not be opened

by Fred Bricon (JIRA)

AS7 launch configuration can not be opened ------------------------------------------ Key: JBIDE-9284 URL: https://issues.jboss.org/browse/JBIDE-9284 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Environment: Indigo, Nightly builds of JBoss AS plugins from trunk Reporter: Fred Bricon Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M3 You can not open the AS7 launch configuration anymore. If you click on the "Open launch configuration" link, nothing happens. But Eclipse's error log shows : {noformat}java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:4263) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:466) at org.eclipse.swt.widgets.Text.setText(Text.java:2099) at org.jboss.ide.eclipse.as.rse.ui.RSELaunchTabProvider$RSERemoteLaunchTab.initializeFrom(RSELaunchTabProvider.java:126) at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:86) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:194) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:751) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:623) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:640) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:602) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:578) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.initializeContent(LaunchConfigurationPropertiesDialog.java:102) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.createContents(LaunchConfigurationsDialog.java:437) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.create(LaunchConfigurationsDialog.java:368) at org.eclipse.jface.window.Window.open(Window.java:790) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1132) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:203) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:629) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:606) at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:588) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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){noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
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 2011