November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13203) Faces Config Editor: node "Message Bundle" is not shown as child node

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-13203: ------------------------------------- Summary: Faces Config Editor: node "Message Bundle" is not shown as child node Key: JBIDE-13203 URL: https://issues.jboss.org/browse/JBIDE-13203 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.0.0.CR1 Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121129-0502-B147.jar Reporter: Daniel Azarov Assignee: Alexey Kazakov Attachments: FacesConfig.png In tab "Tree" of Faces Config Editor you can add follow elements to node "Application": 1. Message Bundle 2. Resource Bundle 3. EL Resolver 4. Property Resolver 5. Variable Resolver 6. Extension !FacesConfig.png! All of them are shown as child nodes for node "Application" but Message Bundle It is not logical. The main problem is that if you add "Message Bundle" to "Application" you can not see the result of your action. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-13202) BrowserSim preferences and about popup are not modal

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-13202: ---------------------------------------------- Summary: BrowserSim preferences and about popup are not modal Key: JBIDE-13202 URL: https://issues.jboss.org/browse/JBIDE-13202 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov On windows about and preferences window disables browsersim windows. On Ubuntu only window from which preferences window is called is disabled, on Mac OS nothing is disabled. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13161) Port forwarding on Server adapter after removing connection should not display error message

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13161: -------------------------------------- Summary: Port forwarding on Server adapter after removing connection should not display error message Key: JBIDE-13161 URL: https://issues.jboss.org/browse/JBIDE-13161 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.CR1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 4.0.0.CR1 The error message dialog should: * not appear to achieve consistent behaviour as in JBIDE-13146 (it's the same situation) - as a temporary solution, until it gets fixed properly as stated in JBIDE-13145 *or* * add to the error message also that the associated connection cannot be found. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-13200) As-You-Type Validation should not create any markers on resources

by Victor Rubezhny (JIRA)

Victor Rubezhny created JBIDE-13200: --------------------------------------- Summary: As-You-Type Validation should not create any markers on resources Key: JBIDE-13200 URL: https://issues.jboss.org/browse/JBIDE-13200 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: CDI, common/jst/core, JSF Affects Versions: 4.0.0.Beta2 Reporter: Victor Rubezhny Assignee: Alexey Kazakov Fix For: 4.1.0.Alpha1 As You Type Validator Manager should not create any resource markers. At the moment, it invokes KBValidator.validateBuildOrder, which creates a resource marker regardless of how it's called. This is correct for Build-Validation, but make a problem to As You Type validation if it's invoked right after a CDI Nature (for example) is just added to a project: {code} !ENTRY org.jboss.tools.cdi.core 4 0 2012-11-26 21:42:08.837 !MESSAGE The resource tree is locked for modifications. !STACK 1 org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications. at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116) at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2282) at org.eclipse.core.internal.resources.Resource.createMarker(Resource.java:733) at org.jboss.tools.jst.web.kb.internal.validation.KBValidator.validateBuilderOrder(KBValidator.java:100) at org.jboss.tools.cdi.internal.core.validation.CDIELValidationDelegate.validateBuilderOrder(CDIELValidationDelegate.java:53) at org.jboss.tools.cdi.internal.core.validation.CDIELValidationDelegate.shouldValidate(CDIELValidationDelegate.java:44) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.shouldValidate(ELValidator.java:637) at org.jboss.tools.common.validation.ValidationContext.shouldValidate(ValidationContext.java:137) at org.jboss.tools.common.validation.EditorValidationContext.shouldValidate(EditorValidationContext.java:50) at org.jboss.tools.common.validation.ValidationContext.init(ValidationContext.java:126) at org.jboss.tools.common.validation.ValidationContext.<init>(ValidationContext.java:43) at org.jboss.tools.common.validation.EditorValidationContext.<init>(EditorValidationContext.java:30) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.init(AsYouTypeValidatorManager.java:151) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:213) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:209) at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.projectCapabilitiesChanged(JavaDirtyRegionProcessor.java:670) at org.jboss.tools.common.validation.java.ProjectCapabilitiesService.resourceChanged(ProjectCapabilitiesService.java:300) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1366) at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1378) at org.jboss.tools.common.EclipseUtil.addNatureToProject(EclipseUtil.java:106) at org.jboss.tools.jst.web.WebModelPlugin.addNatureToProjectWithValidationSupport(WebModelPlugin.java:127) at org.jboss.tools.cdi.core.CDIUtil.enableCDI(CDIUtil.java:98) at org.jboss.tools.cdi.ui.preferences.CDISettingsPreferencePage.addCDISupport(CDISettingsPreferencePage.java:147) at org.jboss.tools.cdi.ui.preferences.CDISettingsPreferencePage.performOk(CDISettingsPreferencePage.java:135) at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448) at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) 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.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.tools.cdi.ui.preferences.AddCDISupportAction.run(AddCDISupportAction.java:44) 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.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:616) 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) !SUBENTRY 1 org.eclipse.core.resources 4 380 2012-11-26 21:42:08.838 !MESSAGE The resource tree is locked for modifications. {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, 4 months

2
1
0 / 0

[JBoss JIRA] (JBIDE-13141) OpenShift server adapter: cannot tail files

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13141: ---------------------------------------- Summary: OpenShift server adapter: cannot tail files Key: JBIDE-13141 URL: https://issues.jboss.org/browse/JBIDE-13141 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Critical Fix For: 4.0.0.CR2 -- 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, 4 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-13163) Runtime Detection doesn't recognize that EAP is already created

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13163: ------------------------------------- Summary: Runtime Detection doesn't recognize that EAP is already created Key: JBIDE-13163 URL: https://issues.jboss.org/browse/JBIDE-13163 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.0.0.Beta2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 4.0.0.Final Steps to reproduce: - start JBDS with EAP (6.0.0.CR1) - click OK when the Runtime Dialog appears - verify an EAP server is created - restart JBDS The Runtime dialog appears again. -- 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, 4 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-12179) Invalid Error marker when using Hibernate @Type annotation

by Corey Puffalt (JIRA)

13 years, 4 months

6
16
0 / 0

[JBoss JIRA] (JBIDE-13199) CLONE - Invalid Error marker when using Hibernate @Type annotation

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13199: ------------------------------------ Summary: CLONE - Invalid Error marker when using Hibernate @Type annotation Key: JBIDE-13199 URL: https://issues.jboss.org/browse/JBIDE-13199 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Reporter: Jiri Peterka Assignee: Denis Golovin Fix For: 3.3.2, 4.0.0.Alpha1 We're seeing invalid error markers when using the Hibernate @Type annotation where the type value we're specifying isn't actually a Class name. This looks like a bug in JBoss Tools (I have the new Candidate Release installed). Sample class: {code} import javax.persistence.Entity; import javax.persistence.Id; import org.hibernate.annotations.Type; @Entity public class TestEntity { @Id private Long id; @Type(type = "yes_no") private Boolean flag; } {code} The error marker states 'Type class "yes_no" could not be found.' but this is actually valid. I did find some similar cases (JBIDE-11364, JBIDE-11368) in the bug tracker but not one that described this issue exactly. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-13197) CLONE - "null" server displayed in server editor

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13197: ------------------------------------ Summary: CLONE - "null" server displayed in server editor Key: JBIDE-13197 URL: https://issues.jboss.org/browse/JBIDE-13197 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.Beta2 Reporter: Jiri Peterka Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.0.0.CR1, 4.1.x Attachments: null-server-in-adapter.png -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-13144) "null" server displayed in server editor

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13144: ---------------------------------------- Summary: "null" server displayed in server editor Key: JBIDE-13144 URL: https://issues.jboss.org/browse/JBIDE-13144 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.0.0.CR1 -- 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, 4 months

2
6
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