[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-4406) org.eclipse.core.internal.resources.ResourceException is occured when rename seam component after testNG was run for this component.

Daniel Azarov (JIRA) jira-events at lists.jboss.org
Thu Jun 18 12:13:56 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBIDE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Azarov resolved JBIDE-4406.
----------------------------------

    Resolution: Done


> org.eclipse.core.internal.resources.ResourceException is occured when rename seam component after testNG was run for this component.
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4406
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4406
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 3.1.0.M1
>            Reporter: Anton Klimkovich
>            Assignee: Daniel Azarov
>             Fix For: 3.1.0.M2
>
>
> EXECUTE: Create seam Ear web project
> EXECUTE: Create new action
> EXECUTE: Run testNG for action.xml in seam-test project
> EXECUTE: Open actionBean.java and select Seam-> Rename Seam Component from context menu
> EXECUTE: Input new name and press Next or Finish button
> FAILURE:   org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/seamEarNew-test/bootstrap/data/hypersonic/localDB.script'.
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:664)
> at org.eclipse.core.internal.resources.File.getContents(File.java:288)
> at org.eclipse.core.internal.resources.File.getContents(File.java:277)
> at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.scan(RenameComponentProcessor.java:144)
> at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.scan(RenameComponentProcessor.java:133)
> at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.scan(RenameComponentProcessor.java:131)
> at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.scan(RenameComponentProcessor.java:131)
> at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.scan(RenameComponentProcessor.java:131)
> at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.findELReferences(RenameComponentProcessor.java:123)
> at org.jboss.tools.seam.internal.core.refactoring.RenameComponentProcessor.createChange(RenameComponentProcessor.java:431)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:290)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
> 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)

-- 
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

        



More information about the jbosstools-issues mailing list