[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4274) Changing web context invalidates Seam projects

[ https://jira.jboss.org/jira/browse/JBIDE-4274?page=com.atlassian.jira.plu... ] Alexey Kazakov commented on JBIDE-4274: --------------------------------------- It seems to be an issue of WTP. They added new RefactoringProcessor for context root rename (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=249128) in WTP 3.0.3. This processor initializes Rename Participants with following parameters: element - instance of IProject newName - <new context root> IMO that's not correct. So such paricipants will be affected: <extension point="org.eclipse.ltk.core.refactoring.renameParticipants"> <renameParticipant ... <enablement> <with variable="element"> <or> <instanceof value="org.eclipse.core.resources.IProject"/> </or> </with> </enablement> </renameParticipant> But we can check "processorIdentifier" to avoid it. Now Seam Rename Participans is invoked by org.eclipse.jdt.ui.renameJavaProjectProcessor and org.eclipse.ltk.core.refactoring.renameResourceProcessor only. BTW I see the same problem in Eclipse ant tools and in our Hibernate tools. If user changes Context Root then ANT and Hibernate launching configurations will be changed and become broken. It's easy to reproduce. I will report it to bugzilla but may be we should check "processorIdentifier" parameter in Hibernate tools too? Max? -- 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