Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » How to avoid to get IllegalArgumentException when rename a non-j2ee project
How to avoid to get IllegalArgumentException when rename a non-j2ee project [message #222962] Thu, 23 October 2008 04:23
Denny Xu is currently offline Denny Xu
Messages: 3
Registered: July 2009
Junior Member
I have defined a new project type by defining a new facet, such as
"jst.esb", and developed a project wizard for the project type based on
WTP, after the ESB project is created, it only contains two facets:
jst.esb and jst.java. So far so good, but after renaming the project , it
gets a java.lang.IllegalArgumentException:Project facet has not been
defined.
at
org.eclipse.wst.common.project.facet.core.internal.FacetedPr ojectFrameworkImpl.getProjectFacet(FacetedProjectFrameworkIm pl.java:230)
at
org.eclipse.wst.common.project.facet.core.ProjectFacetsManag er.getProjectFacet(ProjectFacetsManager.java:74)
at
org.eclipse.jst.j2ee.model.ModelProviderManager.getDefaultFa cet(ModelProviderManager.java:278)
at
org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProv ider(ModelProviderManager.java:266)
at
org.eclipse.jst.j2ee.refactor.operations.ProjectRenameOperat ion.updateProject(ProjectRenameOperation.java:98)
at
org.eclipse.jst.j2ee.refactor.operations.ProjectRefactorOper ation.execute(ProjectRefactorOperation.java:58)
at
org.eclipse.wst.common.frameworks.internal.datamodel.DataMod elPausibleOperationImpl$1.run(DataModelPausibleOperationImpl .java:376)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1800)
at
org.eclipse.wst.common.frameworks.internal.datamodel.DataMod elPausibleOperationImpl.runOperation(DataModelPausibleOperat ionImpl.java:401)
at
org.eclipse.wst.common.frameworks.internal.datamodel.DataMod elPausibleOperationImpl.runOperation(DataModelPausibleOperat ionImpl.java:352)
at
org.eclipse.wst.common.frameworks.internal.datamodel.DataMod elPausibleOperationImpl.doExecute(DataModelPausibleOperation Impl.java:242)
at
org.eclipse.wst.common.frameworks.internal.datamodel.DataMod elPausibleOperationImpl.executeImpl(DataModelPausibleOperati onImpl.java:214)
at
org.eclipse.wst.common.frameworks.internal.datamodel.DataMod elPausibleOperationImpl.cacheThreadAndContinue(DataModelPaus ibleOperationImpl.java:89)
at
org.eclipse.wst.common.frameworks.internal.datamodel.DataMod elPausibleOperationImpl.execute(DataModelPausibleOperationIm pl.java:202)
at
org.eclipse.jst.j2ee.refactor.listeners.ProjectRefactoringLi stener$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)

Could anybody enlighten me how to avoid this? is there a workaround ?
Thanks
Denny
Previous Topic:deploy to tomcat failure
Next Topic:Do I really need WTP for JAX-WS JBossWS WebServices? Or is JBossTools enough?
Goto Forum:
  


Current Time: Fri Jul 25 23:24:50 EDT 2014

Powered by FUDForum. Page generated in 0.01479 seconds