[JBoss JIRA] Created: (JBIDE-9687) Unhandled event loop exception during removing generators from package-info.java in JPA details view
by Jiri Peterka (JIRA)
Unhandled event loop exception during removing generators from package-info.java in JPA details view
----------------------------------------------------------------------------------------------------
Key: JBIDE-9687
URL: https://issues.jboss.org/browse/JBIDE-9687
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 3.3.0.M3
Environment: jbdevstudio-product-eap-linux-gtk-x86_64-5.0.0.v201109071858R-H28-M3, Fedora 15, 64-bit
Reporter: Jiri Peterka
Fix For: 3.3.0.M4
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ClassCastException: org.eclipse.jpt.jpa.core.internal.resource.java.source.SourcePackage cannot be cast to org.eclipse.jpt.jpa.core.resource.java.JavaResourcePersistentMember)
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.views.log.EventDetailsDialog.open(EventDetailsDialog.java:180)
at org.eclipse.ui.internal.views.log.EventDetailsDialogAction.run(EventDetailsDialogAction.java:98)
at org.eclipse.ui.internal.views.log.LogView$15.doubleClick(LogView.java:535)
at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:845)
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.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:843)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1462)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1246)
at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:246)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:307)
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: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)
Caused by: java.lang.ClassCastException: org.eclipse.jpt.jpa.core.internal.resource.java.source.SourcePackage cannot be cast to org.eclipse.jpt.jpa.core.resource.java.JavaResourcePersistentMember
at org.eclipse.jpt.jpa.core.internal.resource.java.source.SourceAnnotation.getParent(SourceAnnotation.java:106)
at org.eclipse.jpt.jpa.core.internal.resource.java.source.SourceAnnotation.convertToStandAlone(SourceAnnotation.java:235)
at org.jboss.tools.hibernate.jpt.core.internal.resource.java.SourceGenericGeneratorsAnnotation.convertLastNestedAnnotationToStandAlone(SourceGenericGeneratorsAnnotation.java:100)
at org.eclipse.jpt.jpa.core.internal.resource.java.source.SourceAnnotatedElement.convertLastNestedAnnotation(SourceAnnotatedElement.java:288)
at org.eclipse.jpt.jpa.core.internal.resource.java.source.SourceAnnotatedElement.removeAnnotation(SourceAnnotatedElement.java:276)
at org.eclipse.jpt.jpa.core.internal.resource.java.source.SourceAnnotatedElement.removeAnnotation(SourceAnnotatedElement.java:260)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernateJavaGeneratorContainerImpl.removeGenericGenerator(HibernateJavaGeneratorContainerImpl.java:104)
at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernateJavaGeneratorContainerImpl.removeGenericGenerator(HibernateJavaGeneratorContainerImpl.java:99)
at org.jboss.tools.hibernate.jpt.ui.internal.mapping.details.GenericGeneratorsComposite$3.removeSelectedItems(GenericGeneratorsComposite.java:151)
at org.eclipse.jpt.common.ui.internal.widgets.AddRemovePane.removeItems(AddRemovePane.java:619)
at org.eclipse.jpt.common.ui.internal.widgets.AddRemovePane$4.run(AddRemovePane.java:405)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 42 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-6537) Helios support for JBT v3.1.1
by Darryl Miles (JIRA)
Helios support for JBT v3.1.1
-----------------------------
Key: JBIDE-6537
URL: https://jira.jboss.org/browse/JBIDE-6537
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Hibernate, Seam
Affects Versions: 3.1.1
Reporter: Darryl Miles
Assignee: Max Rydahl Andersen
Both the "Hibernate Tools" and "Seam Tools" for JBT v3.1.1 have too narrow version requirements for com.ibm.icu to be compatible with Helios.
Helios comes with com.ibm.icu v4.2.1
Currently the version requirements are set to [3.4.4,4.1.0) so this should be changed at a minimum to [3.4.4,4.3.0) to allow both these JBT components to install on top of Helios.
However you should consider using an even wider version width of [3.4.4,5) since it is accepted practise that minor version increments are backwardly compatible and a major version change is potentially API breaking. This means that generally JBT should (and is expected to) work on all future versions of com.ibm.icu up until version 5 is released.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBDS-1847) No syntax auto-completion in Drools IDE for RHS
by Blaine Mincey (JIRA)
No syntax auto-completion in Drools IDE for RHS
-----------------------------------------------
Key: JBDS-1847
URL: https://issues.jboss.org/browse/JBDS-1847
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: drools
Affects Versions: 4.1.0.GA
Environment: RHEL 6.1
Sun JDK 1.6.0_25 64-bit
JBDS 4.1
Reporter: Blaine Mincey
Fix For: LATER
When creating/editing rules in the Drools IDE, it is possible for syntax auto-completion for the model/facts, variables, etc. on the LHS(When syntax). However, there is not auto-completion for the RHS (Then syntax).
It would be great to have the syntax auto-completion to work on the RHS as it does for the LHS of rules authoring.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Commented: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-1819:
-------------------------------------------
isaac/nick, this is not about update sites its about project example sites.
> Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2
> -----------------------------------------------------------------------
>
> Key: JBDS-1819
> URL: https://issues.jboss.org/browse/JBDS-1819
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: SOA Platform
> Affects Versions: 4.1.0.CR3
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.1.M1
>
> Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png
>
>
> Need to ensure there are sample ESB quickstarts available to run cleanly with SOA-P 5.2 on JBDS 4.1.1
> Was:
> Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1
> Was:
> This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months