[JBoss JIRA] Created: (JBIDE-2586) "Content Assist" did not complete normally" exception is occured for struts cofiguration file.
by Anton Klimkovich (JIRA)
"Content Assist" did not complete normally" exception is occured for struts cofiguration file.
----------------------------------------------------------------------------------------------
Key: JBIDE-2586
URL: https://jira.jboss.org/jira/browse/JBIDE-2586
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: struts/shale, XML Structured Editor
Affects Versions: 3.0.0.alpha
Reporter: Anton Klimkovich
Priority: Critical
Attachments: exception.txt
EXECUTE: Create struts web project kickstart
EXECUTE: Open struts-config.xml
EXECUTE: Try to call CA.
FAILURE: CA is not available.
EXECUTE: Open web.xml
EXECUTE: Call CA.
ASSERT: CA available.
EXECUTE: Switch to opened struts-config.xml
EXECUTE: Try to call CA.
FAILURE: CA available with proposal list from web.xml
EXECUTE: Close web.xml
EXECUTE: Switch to opened struts-config.xml and call CA
FAILURE: CA is not available. java.lang.NullPointerException is occured.
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, 8 months
[JBoss JIRA] Created: (JBIDE-2666) Project archives does not seem to work with eclipse variables with arguments
by Max Rydahl Andersen (JIRA)
Project archives does not seem to work with eclipse variables with arguments
----------------------------------------------------------------------------
Key: JBIDE-2666
URL: https://jira.jboss.org/jira/browse/JBIDE-2666
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.0.0.alpha
Reporter: Max Rydahl Andersen
Fix For: 3.0.0.beta1
Trying to use ${resource_loc:/projectA/.classpath} resulted in below stacktrace and the text field just ended up being ${resource_loc}
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
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:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)
Caused by: java.lang.NullPointerException
at org.jboss.ide.eclipse.archives.ui.providers.ArchivesContentProviderDelegate.shouldRefreshProject(ArchivesContentProviderDelegate.java:117)
at org.jboss.ide.eclipse.archives.ui.providers.ArchivesContentProviderDelegate$1$1.run(ArchivesContentProviderDelegate.java:101)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
... 22 more
--
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, 8 months
[JBoss JIRA] Created: (JBIDE-2746) Exceptions in the workspace log file.
by Adrian Mitev (JIRA)
Exceptions in the workspace log file.
-------------------------------------
Key: JBIDE-2746
URL: https://jira.jboss.org/jira/browse/JBIDE-2746
Project: Tools (JBoss Tools)
Issue Type: Quality Risk
Affects Versions: 3.0.0.alpha
Environment: jbt 3.0 alpha
Reporter: Adrian Mitev
I see a lot of these in the workspace log file:
!ENTRY org.eclipse.core.resources 4 2 2008-09-08 18:25:57.937
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
at org.jboss.ide.eclipse.archives.core.WorkspaceChangeListener$2.visit(WorkspaceChangeListener.java:72)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
at org.jboss.ide.eclipse.archives.core.WorkspaceChangeListener.resourceChanged(WorkspaceChangeListener.java:68)
at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:288)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:282)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1022)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1809)
at org.eclipse.wst.validation.internal.operations.ValidationOperation$1.done(ValidationOperation.java:1398)
at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112)
at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152)
at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:558)
at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
These exceptions does not prevent the normal work of the ide.
--
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, 8 months
[JBoss JIRA] Created: (JBIDE-2341) Project Archives View - don't work properly
by Aliaksey Nis (JIRA)
Project Archives View - don't work properly
-------------------------------------------
Key: JBIDE-2341
URL: http://jira.jboss.com/jira/browse/JBIDE-2341
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 2.1.1
Environment: WindowsXP SP2
JBoss Tools 2.1.1GA
Reporter: Aliaksey Nis
In Project Archives View:
1. EJB JAR and EAR options don't work properly. They creates files with 22 bytes size, w/o content inside.
2.
EXECUTE: Create Seam Ear project and select it in package explorer.
EXECUTE: In Project Archives view - click on EAR option.
EXECUTE: Select compressed file, destination - Seam project folder, name - default(testseam.ear).
ASSERT: testear.ear created (but w/o content - look [1]).
EXECUTE: In Project Archives view - New Archive > click on EAR option.
EXECUTE: Select exploded archive, destination - Seam project folder, name - default(testseam.ear).
FAILURE: No exploded archive appears.
If you select different name for exploded archive - it will be created(but w/o content - look [1]),
Same issue for JAR and EJB JAR archives.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months