[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-4355) java.lang.IllegalArgumentException is occured after renaming JBoss ESB project
Denny Xu (JIRA)
jira-events at lists.jboss.org
Wed Aug 19 04:13:26 EDT 2009
[ https://jira.jboss.org/jira/browse/JBIDE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denny Xu resolved JBIDE-4355.
-----------------------------
Resolution: Duplicate Issue
Duplicate issue : JBIDE-2887
> java.lang.IllegalArgumentException is occured after renaming JBoss ESB project
> -------------------------------------------------------------------------------
>
> Key: JBIDE-4355
> URL: https://jira.jboss.org/jira/browse/JBIDE-4355
> Project: JBoss Tools
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.1.0.M1
> Reporter: Anton Klimkovich
> Assignee: Denny Xu
> Fix For: 3.1.0.M3
>
>
> EXECUTE: Create Jboss ESB project with SOA-P 4.3 runtime
> EXECUTE: Refactor-> Rename -> Input new name and press Finish button
> FAILURE: Exception thrown.
> java.lang.IllegalArgumentException: Project facet has not been defined.
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl.getProjectFacet(FacetedProjectFrameworkImpl.java:230)
> at org.eclipse.wst.common.project.facet.core.ProjectFacetsManager.getProjectFacet(ProjectFacetsManager.java:74)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getDefaultFacet(ModelProviderManager.java:278)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:266)
> at org.eclipse.jst.j2ee.refactor.operations.ProjectRenameOperation.updateProject(ProjectRenameOperation.java:91)
> at org.eclipse.jst.j2ee.refactor.operations.ProjectRefactorOperation.execute(ProjectRefactorOperation.java:58)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
> at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
> at org.eclipse.jst.j2ee.refactor.listeners.ProjectRefactoringListener$1.runInWorkspace(ProjectRefactoringListener.java:199)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
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