[JBoss JIRA] Created: (JBIDE-3612) New Seam Project Wizard: Seam EJB project is not published.
by Alexey Kazakov (JIRA)
New Seam Project Wizard: Seam EJB project is not published.
-----------------------------------------------------------
Key: JBIDE-3612
URL: https://jira.jboss.org/jira/browse/JBIDE-3612
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.CR2
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.0.0.GA
1. Create Seam EAR Project using New Seam Web Project wizard.
2. Seam-ear is registered but seam ejb module is not published.
Clean/full-publish on ear module helps.
We register/publish seam project by adding jobs in Seam post Install delegate.
But eclipse starts building workspace only when the operation of ModifyFacetedProjectWizard is finished.
And the build thread is waiting for registring jobs is finished.
So we have EAR module published before projects are buit.
<EJB>/buid/classes is empty and wtp prints error message in console (if trace is on) and stops publishing ejb project.
So we need either force build before registration or suspend publishing until projects are buit.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-3572) Problem with archives when deleting project
by Snjezana Peco (JIRA)
Problem with archives when deleting project
-------------------------------------------
Key: JBIDE-3572
URL: https://jira.jboss.org/jira/browse/JBIDE-3572
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.0.0.CR2
Reporter: Snjezana Peco
Steps:
- create a Java Project
- open the Project Archives view
- create an archive
- delete the project
The Project Archive view still shows the project, archive; all commands are enabled; the archive is available to deploy.
Sometimes you get an exception when rebuild and/or refresh projects in the workspace. The problem will exist until you restart Eclipse.
Solution:
When the project is deleted, unregister it within the existing resource change listener.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-3627) Exception while creating second war archive for Seam war project.
by Aliaksey Nis (JIRA)
Exception while creating second war archive for Seam war project.
-----------------------------------------------------------------
Key: JBIDE-3627
URL: https://jira.jboss.org/jira/browse/JBIDE-3627
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.0.0.CR2
Environment: WindowsXP SP2
JBoss Developer Studio
Version: 2.0.0.CR2
Build id: jbdevstudio-eap-win32-2.0.0.CR2-N200901221952
JRE 1.5_08
Reporter: Aliaksey Nis
EXECUTE: Create Seam 2FP war project.
EXECUTE: Open archive view, select Seam project in Package explorer.
EXECUTE: New > New Archive>War. Right click. Left options unchanged, press Finish.
ASSERT: Archive appears.
EXECUTE: Select archive in Archives view. Select fileset in view. Press "edit fileset".
EXECUTE: When fileset menu appears - press Cancel.
EXECUTE: Select Seam project. Right click. New > New Archive>War.
FAILURE: Exception thrown. Wizard don't appears.
Error log attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-3573) EAR archive can't be created
by Snjezana Peco (JIRA)
EAR archive can't be created
-----------------------------
Key: JBIDE-3573
URL: https://jira.jboss.org/jira/browse/JBIDE-3573
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.0.0.CR2
Reporter: Snjezana Peco
Steps to reproduce:
- create a Seam EAR project
- open the Project Archives view
- call New Archive>EAR
- click the Next button
You will get the following exception :
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: null argument:
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:86)
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:74)
at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.addChild(ArchiveNodeImpl.java:275)
at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.addChild(ArchiveNodeImpl.java:266)
at org.jboss.ide.eclipse.archives.webtools.archivetypes.EarArchiveType.fillDefaultConfiguration(EarArchiveType.java:114)
at org.jboss.ide.eclipse.archives.webtools.ui.NewEARAction$EARPreviewPage.addToPackage(NewEARAction.java:101)
at org.jboss.ide.eclipse.archives.webtools.ui.PreviewPage.pageEntered(PreviewPage.java:115)
at org.jboss.ide.eclipse.archives.ui.wizards.WizardWithNotification.pageChanged(WizardWithNotification.java:72)
at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1459)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.wizard.WizardDialog.firePageChanged(WizardDialog.java:1457)
at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1237)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1166)
at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1139)
at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1128)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1126)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:820)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.ide.eclipse.archives.webtools.ui.NewEARAction.run(NewEARAction.java:49)
at org.jboss.ide.eclipse.archives.webtools.ui.NewEARAction.run(NewEARAction.java:54)
at org.jboss.ide.eclipse.archives.ui.providers.ArchivesActionProvider$ActionWrapper.run(ArchivesActionProvider.java:224)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
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:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
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:386)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-3661) FreeMarker IDE Plugin Hangs Eclipse with "SWTError: No more handles"
by kaliatech (JIRA)
FreeMarker IDE Plugin Hangs Eclipse with "SWTError: No more handles"
--------------------------------------------------------------------
Key: JBIDE-3661
URL: https://jira.jboss.org/jira/browse/JBIDE-3661
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: FreeMarker
Environment: All
Reporter: kaliatech
The FreeMarker IDE plugin hangs my Eclipse instance after some time when editing larger FreeMarker templates. The Eclipse workspace log shows multiple exceptions before hanging, and the errors seem to start from within the FreeMarker plugin. The errors generally contain a message like "org.eclipse.swt.SWTError: No more handles". See the forum post for more detail.
I'm not an expert with Eclipse/SWT/Plugin development, but looking through code in SVN, it doesn't look like the label images used in the Freemarker Outline view tree are being disposed. The plugin's ImageManager creates the label images that are then used by the plugin's OutlineLabelProvider. However, I don't see where those images are ever disposed. My guess is that outline labels are created/reconstructed quite often, and so more and more images get created but never disposed.
Assuming SWT images are immutable and can be reused, the fix might be as simple as modifying OutlineLabelProvider to cache the images in a map by the filename. Then, making sure they are reused on every call to the provider. (Whatever caches the images should also dispose them when itself is disposed, but if the images are being reused, it probably doesn't matter much.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 2 months