January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10681) Opening Agenda view throws DebugException

by Juraj Gargulak (JIRA)

Juraj Gargulak created JBIDE-10681: -------------------------------------- Summary: Opening Agenda view throws DebugException Key: JBIDE-10681 URL: https://issues.jboss.org/browse/JBIDE-10681 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: LATER Reporter: Juraj Gargulak Assignee: Kris Verlaenen Priority: Minor DebugException is thrown when Agenda view change focus while debugging: !ENTRY org.drools.eclipse 4 120 2012-01-20 16:38:52.473 !MESSAGE Internal error in Drools Plugin: !STACK 1 org.eclipse.debug.core.DebugException: Error when compiling snippet return getAgenda().getFocus();: The method getFocus() is undefined for the type Agenda at org.drools.eclipse.debug.DebugUtil$EvaluationBlock.evaluate(DebugUtil.java:194) at org.drools.eclipse.debug.DebugUtil.getValueByExpression(DebugUtil.java:116) at org.drools.eclipse.debug.AgendaViewContentProvider.getAgendaElements(AgendaViewContentProvider.java:86) at org.drools.eclipse.debug.AgendaViewContentProvider.getChildren(AgendaViewContentProvider.java:54) at org.drools.eclipse.debug.DroolsDebugViewContentProvider.getElements(DroolsDebugViewContentProvider.java:52) at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1010) at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:703) at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1336) at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391) at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917) at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:605) at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2622) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1908) at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1883) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1840) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1826) at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1508) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1506) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465) at org.drools.eclipse.debug.actions.ShowLogicalStructureAction$1.run(ShowLogicalStructureAction.java:55) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.drools.eclipse.debug.actions.ShowLogicalStructureAction.valueChanged(ShowLogicalStructureAction.java:53) at org.drools.eclipse.debug.actions.ShowLogicalStructureAction.run(ShowLogicalStructureAction.java:45) at org.eclipse.debug.ui.AbstractDebugView$3.run(AbstractDebugView.java:612) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) 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) !SUBENTRY 1 org.drools.eclipse 4 120 2012-01-20 16:38:52.474 !MESSAGE Error when compiling snippet return getAgenda().getFocus();: The method getFocus() is undefined for the type Agenda -- 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, 9 months

5
6
0 / 0

[JBoss JIRA] (JBIDE-10707) Audit view cannot load log file

by Juraj Gargulak (JIRA)

Juraj Gargulak created JBIDE-10707: -------------------------------------- Summary: Audit view cannot load log file Key: JBIDE-10707 URL: https://issues.jboss.org/browse/JBIDE-10707 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: LATER Reporter: Juraj Gargulak Assignee: Kris Verlaenen Audit view cannot load log file. Probably because of this exception: !ENTRY org.drools.eclipse 4 120 2012-01-25 15:58:37.076 !MESSAGE Internal error in Drools Plugin: !STACK 0 java.lang.NoClassDefFoundError: org/xmlpull/v1/XmlPullParserFactory at com.thoughtworks.xstream.io.xml.XppDriver.createParser(XppDriver.java:57) at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:58) at com.thoughtworks.xstream.XStream.createObjectInputStream(XStream.java:1660) at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:118) at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:103) at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39) at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:276) at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:90) 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.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1061) at org.eclipse.swt.dnd.DropTarget.drag_data_received(DropTarget.java:371) at org.eclipse.swt.dnd.DropTarget.Drag_Data_Received(DropTarget.java:251) at org.eclipse.swt.internal.gtk.OS._gtk_drag_get_data(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_drag_get_data(OS.java:6693) at org.eclipse.swt.dnd.DropTarget.drag_drop(DropTarget.java:416) at org.eclipse.swt.dnd.DropTarget.Drag_Drop(DropTarget.java:258) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) 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) After this exception audit view shows message "The selected audit log is empty." but the log file is not empty and it contains logged data. -- 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, 9 months

6
7
0 / 0

[JBoss JIRA] Created: (JBDS-1532) Users should be warned when installing 32 bit JBDS on Leopard

by Martin Malina (JIRA)

Users should be warned when installing 32 bit JBDS on Leopard ------------------------------------------------------------- Key: JBDS-1532 URL: https://issues.jboss.org/browse/JBDS-1532 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 4.0.0.CR1 Environment: Mac OS X 10.5 Leopard jbdevstudio-product-macosx-cocoa-4.0.0.v201101230948R-H100-CR1.jar Reporter: Martin Malina I stumbled upon this when testing JBDS on Leopard: When you install the Cocoa (32bit) version of JBDS on Leopard, it lets you install it with no problem even though it's not supported because then it's bound to run with Java 1.5 (Java 1.6 is 64bit-only on Leopard). When you start JBDS after the installation at first everything seems ok - the welcome screen, the menu... But for example the installed EAP runtime is missing and soon you realize that other plugins are missing too - this is the result of running JBDS running with Java 1.5 in this case. If a user installs 32bit version of JBDS on Leopard, it is his fault. But it would be nice to have some kind of warning - either during the installation. Or when JBDS is started with Java 1.5. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

12
44
0 / 0

[JBoss JIRA] Created: (JBIDE-6644) Offer quick fixes for CDI validations

by Pete Muir (JIRA)

Offer quick fixes for CDI validations ------------------------------------- Key: JBIDE-6644 URL: https://jira.jboss.org/browse/JBIDE-6644 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Max Rydahl Andersen -- 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, 9 months

5
12
0 / 0

[JBoss JIRA] (JBIDE-9833) Quick fixes for problem markers in beans.xml

by Daniel Azarov (Created) (JIRA)

Quick fixes for problem markers in beans.xml -------------------------------------------- Key: JBIDE-9833 URL: https://issues.jboss.org/browse/JBIDE-9833 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: CDI Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.0.M4 1. Quick fix for "There is no class with the specified name [JSR-299 §5.1.1]" problem marker In case when Bean class or Stereotype does not exists there should be a quick fix: "Create Bean Class/Stereotype". This quick fix should run Creation wizard for Bean Class or Stereotype with selected "Add @Alternative" option 2. Quick fix for "<class> element must specify the name of an alternative bean class [JSR-299 §5.1.1]" and "<stereotype> element must specify the name of an @Alternative stereotype annotation [JSR-299 §5.1.1]" problem markers In case of existing of Bean Class or Stereotype and when Bean Class or Stereotype has no @Alternative annotation there should be a quick fix: "Add @Alternative annotation to Bean Class/Stereotype" 3. Quick fix for "There is no class with the specified name [JSR-299 §9.4]/[JSR-299 §8.2]" problem markers In case when Decorator or Interceptor does not exists there should be a quick fix: "Create Interceptor/Decorator". This quick fix should run Creation wizard for Interceptor or Decorator -- 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, 9 months

6
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7676) Quick fix for "Method has more than one parameter annotated @Observes [JSR-299 §10.4.2]" error marker

by Daniel Azarov (JIRA)

Quick fix for "Method has more than one parameter annotated @Observes [JSR-299 §10.4.2]" error marker ----------------------------------------------------------------------------------------------------- Key: JBIDE-7676 URL: https://jira.jboss.org/browse/JBIDE-7676 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.x This quick fix should offer to delete @Observes annotation -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7671) Quick fix for "Static/Generic method of a bean cannot be annotated @Inject [JSR-299 §3.9.1]" error markers

by Daniel Azarov (JIRA)

Quick fix for "Static/Generic method of a bean cannot be annotated @Inject [JSR-299 §3.9.1]" error markers ---------------------------------------------------------------------------------------------------------- Key: JBIDE-7671 URL: https://jira.jboss.org/browse/JBIDE-7671 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.x This quick fix should offer to delete @Inject annotation -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8201) Quick fix for "Managed bean with a public field must be @Dependent scoped" error marker

by Alexey Kazakov (JIRA)

Quick fix for "Managed bean with a public field must be @Dependent scoped" error marker --------------------------------------------------------------------------------------- Key: JBIDE-8201 URL: https://issues.jboss.org/browse/JBIDE-8201 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.x See details in JBIDE-7947 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7670) Quick fix for "Method has more than one parameter annotated @Disposes [JSR-299 §3.3.6]" error marker

by Daniel Azarov (JIRA)

Quick fix for "Method has more than one parameter annotated @Disposes [JSR-299 §3.3.6]" error marker ---------------------------------------------------------------------------------------------------- Key: JBIDE-7670 URL: https://jira.jboss.org/browse/JBIDE-7670 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.x This quick fix should offer to delete @Disposes annotation -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7639) Quick fix for "Injection point type cannot be a type variable [JSR-299 §5.2.2]" error marker

by Daniel Azarov (JIRA)

Quick fix for "Injection point type cannot be a type variable [JSR-299 §5.2.2]" error marker -------------------------------------------------------------------------------------------- Key: JBIDE-7639 URL: https://jira.jboss.org/browse/JBIDE-7639 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.x This quick fix should offer to delete @Inject annotation -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
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 January 2012