[
https://jira.jboss.org/browse/JBIDE-6054?page=com.atlassian.jira.plugin.s...
]
Alexey Kazakov resolved JBIDE-6054.
-----------------------------------
Resolution: Done
I can't reproduce it either. But teoreticly I see that EL Resolver may return null in
some rear cases. So I added a check for null and fixed that NPE.
Vadim, could you verify the fix?
NullPointerException when trying to rename method
-------------------------------------------------
Key: JBIDE-6054
URL:
https://jira.jboss.org/browse/JBIDE-6054
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.1.0.GA
Reporter: Vadim Berezniker
Assignee: Alexey Kazakov
Fix For: 3.1.1
Attachments: org.jboss.tools.patch
I have a seam-gen ant based project.
When I attempt to rename a method, the refactoring process sits there for a bit in
"Checking preconditions" state and then I get an error dialog that says
"The participant '<method name>' caused an internal error and has been
disabled for refactoring."
The following exception is seen in the Eclipse log right after the message:
!ENTRY org.eclipse.ltk.core.refactoring 4 10000 2010-03-13 00:18:41.025
!MESSAGE Internal Error
!STACK 0
java.lang.NullPointerException
at
org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:256)
at
org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolve(AbstractELCompletionEngine.java:131)
at
org.jboss.tools.jsf.el.refactoring.RefactorSearcher.searchInCach(RefactorSearcher.java:210)
at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:188)
at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:148)
at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146)
at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146)
at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146)
at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146)
at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scan(RefactorSearcher.java:146)
at
org.jboss.tools.jsf.el.refactoring.RefactorSearcher.findELReferences(RefactorSearcher.java:114)
at
org.jboss.tools.jsf.ui.el.refactoring.RenameMethodParticipant.checkConditions(RenameMethodParticipant.java:70)
at
org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:257)
at
org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
at
org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:211)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at
org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
I recently updated to 3.1
--
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