Re: [Dev] Dev studio errors and feedback
Hello Dulitha, Please find the below steps I followed in attempting to reproduce your issue in developer studio 3.8.0 in linux . Please give me the steps to reproduce if this is not the way. Also let me know your OS. 1) created ESB project 1 2) created Rest API with the name "sampleRest" in project 1 3) created ESB project 2 4) created Rest API with the name "sampleRest" in project 2 5) created Capp1 including ESB Project 1 6) created Capp2 including ESB Project 2 7) deleted sampleRest from each ESB project and observed the changes being reflected in the capp accordingly. I also tried deleting multiple artifacts. and observed that the car file reflects them fine. Regards Awanthika Awanthika Senarath Software Engineer, WSO2 Inc. Mobile: +94717681791 On Tue, Dec 22, 2015 at 9:31 PM, Dulitha Wijewantha wrote: > > > On Wed, Dec 16, 2015 at 9:17 PM, Awanthika Senarath > wrote: > >> Hello Dulitha, >> >> >> I agree that artifact name needs to be unqiue to the car file. But in a >> scenario where you have 2 esb configuration projects having an artifact >> with the same name (in-sequence.xml) - it crashes the car interface. >> >> If you have the same ESB artifact in different configuration projects, >> you cannot pack them in the same car file. Because in car file level we >> only consider the artifact name and not the folder hierarchy (which >> involves the ESB project). The ESB project is introduced by Dev studio to >> maintain artifacts. When you deploy the car file in the ESB, ESB will only >> deploy the artifacts as single entries and not the project, and I fail to >> understand you reasoning behind having the same artifact name as you wont >> be able to deploy them in the same ESB instance in a single car file anyway. >> >> But I accept that this should be conveyed to the user via a message, not >> crashing the car file. >> >> >> About the issue you faced when deleting artifacts, I was not able to >> reproduce it, >> >> 1. Created two ESB projects >> 2. Created 2 Rest API artifacts with the same name in both projects >> 3. Deleted on Rest API >> >> It worked as expected for me in Dev studio 3.8.0 >> >> Could you please give me your Dev studio version and also reproducing >> steps? >> > > It was dev studio 3.8.0. > > Did you create the car project as well on both projects? > > Also there is an issue in deleting multiple artifacts. If muliple are > deleted the car file doesn't reflect those. > > >> >> Regards >> Awanthika >> >> Awanthika Senarath >> Software Engineer, WSO2 Inc. >> Mobile: +94717681791 >> >> >> >> On Wed, Dec 16, 2015 at 10:23 PM, Dulitha Wijewantha >> wrote: >> >>> >>> >>> On Tue, Dec 15, 2015 at 10:26 PM, Awanthika Senarath >> > wrote: >>> Hi Dulitha, Find my responses in-line, 1) Can't have the same project name in the workspace. For example - I create a project called gateway-dev and have gateway-car, gateway-synapse, gateway-registry. I can't create a project with gateway-staging and have gateway-car. Is this an eclipse limitation? This is an eclipse limitation. Eclipse maintains a META file called .project for each and every project and the name in this .project file needs to be unique. 2) Can't have the same artifact name in the workspace. This one is bit annoying. I renamed the project to gateway-dev-synapse and gateway-staging-synapse. I can't have the api artifact with id.xml inside dev project and staging project in the same namespace:- the car picking form gets confused on the two assets. What's more - it will get corrupted and not have anything at all from synapse to pick. Below is an error that popped in the error console Yes, car files import artifacts based on the artifact name and in the artifact.xml of a car file it will list all the artifacts that needs to be bundled in that particular car, hence the artifact names needs to be unique for the car file. The error you have got is due to dev studio crashing before the file system files are properly refreshed, OR an attempt to manually edit the file system resources not via eclipse. Ideally this should be resolved by refreshing the workspace files through eclipse (right click the file and refresh) >>> >>> I agree that artifact name needs to be unqiue to the car file. But in a >>> scenario where you have 2 esb configuration projects having an artifact >>> with the same name (in-sequence.xml) - it crashes the car interface. >>> >>> >>> >>> 3) Deleting a resource (API) got me below error - Could you please let us know how to reproduce this? did you attempt to rename the resource before deleting? >>> This was the scenario where I had the same arifact name in 2 different >>> esb configuration projects. >>> >>> >>> 4) Bulk import for resources - You are correct, this is a current limitation. You can import the syn
Re: [Dev] Dev studio errors and feedback
On Wed, Dec 16, 2015 at 9:17 PM, Awanthika Senarath wrote: > Hello Dulitha, > > > I agree that artifact name needs to be unqiue to the car file. But in a > scenario where you have 2 esb configuration projects having an artifact > with the same name (in-sequence.xml) - it crashes the car interface. > > If you have the same ESB artifact in different configuration projects, you > cannot pack them in the same car file. Because in car file level we only > consider the artifact name and not the folder hierarchy (which involves the > ESB project). The ESB project is introduced by Dev studio to maintain > artifacts. When you deploy the car file in the ESB, ESB will only deploy > the artifacts as single entries and not the project, and I fail to > understand you reasoning behind having the same artifact name as you wont > be able to deploy them in the same ESB instance in a single car file anyway. > > But I accept that this should be conveyed to the user via a message, not > crashing the car file. > > > About the issue you faced when deleting artifacts, I was not able to > reproduce it, > > 1. Created two ESB projects > 2. Created 2 Rest API artifacts with the same name in both projects > 3. Deleted on Rest API > > It worked as expected for me in Dev studio 3.8.0 > > Could you please give me your Dev studio version and also reproducing > steps? > It was dev studio 3.8.0. Did you create the car project as well on both projects? Also there is an issue in deleting multiple artifacts. If muliple are deleted the car file doesn't reflect those. > > Regards > Awanthika > > Awanthika Senarath > Software Engineer, WSO2 Inc. > Mobile: +94717681791 > > > > On Wed, Dec 16, 2015 at 10:23 PM, Dulitha Wijewantha > wrote: > >> >> >> On Tue, Dec 15, 2015 at 10:26 PM, Awanthika Senarath >> wrote: >> >>> Hi Dulitha, >>> >>> Find my responses in-line, >>> >>> 1) Can't have the same project name in the workspace. For example - I >>> create a project called gateway-dev and have gateway-car, gateway-synapse, >>> gateway-registry. I can't create a project with gateway-staging and have >>> gateway-car. Is this an eclipse limitation? >>> This is an eclipse limitation. Eclipse maintains a META file called >>> .project for each and every project and the name in this .project file >>> needs to be unique. >>> >>> 2) Can't have the same artifact name in the workspace. This one is bit >>> annoying. I renamed the project to gateway-dev-synapse and >>> gateway-staging-synapse. I can't have the api artifact with id.xml inside >>> dev project and staging project in the same namespace:- the car picking >>> form gets confused on the two assets. What's more - it will get corrupted >>> and not have anything at all from synapse to pick. Below is an error that >>> popped in the error console >>> Yes, car files import artifacts based on the artifact name and in >>> the artifact.xml of a car file it will list all the artifacts that needs to >>> be bundled in that particular car, hence the artifact names needs to be >>> unique for the car file. The error you have got is due to dev studio >>> crashing before the file system files are properly refreshed, OR an attempt >>> to manually edit the file system resources not via eclipse. Ideally this >>> should be resolved by refreshing the workspace files through eclipse (right >>> click the file and refresh) >>> >> >> I agree that artifact name needs to be unqiue to the car file. But in a >> scenario where you have 2 esb configuration projects having an artifact >> with the same name (in-sequence.xml) - it crashes the car interface. >> >> >> >>> >>> >> 3) Deleting a resource (API) got me below error - >>> Could you please let us know how to reproduce this? did you attempt >>> to rename the resource before deleting? >>> >> This was the scenario where I had the same arifact name in 2 different >> esb configuration projects. >> >> >> >>> >>> 4) Bulk import for resources - >>> You are correct, this is a current limitation. You can import the >>> synapse configuration with multiple proxies in it and dev-studio will >>> generate the proxies for different artifacts in the synapse configuration. >>> But currently it is not supported to import multiple proxy.xml files >>> simultaneously. >>> >>> Regards >>> Awanthika >>> >>> >>> Awanthika Senarath >>> Software Engineer, WSO2 Inc. >>> Mobile: +94717681791 >>> >>> >>> >>> On Wed, Dec 16, 2015 at 6:25 AM, Dulitha Wijewantha >>> wrote: >>> Hi guys, I got some issues today working on the developer studio. 1) Can't have the same project name in the workspace. For example - I create a project called gateway-dev and have gateway-car, gateway-synapse, gateway-registry. I can't create a project with gateway-staging and have gateway-car. Is this an eclipse limitation? 2) Can't have the same artifact name in the workspace. This one is bit annoying. I renamed the project to gateway-dev-synapse and
Re: [Dev] Dev studio errors and feedback
Hello Dulitha, I agree that artifact name needs to be unqiue to the car file. But in a scenario where you have 2 esb configuration projects having an artifact with the same name (in-sequence.xml) - it crashes the car interface. If you have the same ESB artifact in different configuration projects, you cannot pack them in the same car file. Because in car file level we only consider the artifact name and not the folder hierarchy (which involves the ESB project). The ESB project is introduced by Dev studio to maintain artifacts. When you deploy the car file in the ESB, ESB will only deploy the artifacts as single entries and not the project, and I fail to understand you reasoning behind having the same artifact name as you wont be able to deploy them in the same ESB instance in a single car file anyway. But I accept that this should be conveyed to the user via a message, not crashing the car file. About the issue you faced when deleting artifacts, I was not able to reproduce it, 1. Created two ESB projects 2. Created 2 Rest API artifacts with the same name in both projects 3. Deleted on Rest API It worked as expected for me in Dev studio 3.8.0 Could you please give me your Dev studio version and also reproducing steps? Regards Awanthika Awanthika Senarath Software Engineer, WSO2 Inc. Mobile: +94717681791 On Wed, Dec 16, 2015 at 10:23 PM, Dulitha Wijewantha wrote: > > > On Tue, Dec 15, 2015 at 10:26 PM, Awanthika Senarath > wrote: > >> Hi Dulitha, >> >> Find my responses in-line, >> >> 1) Can't have the same project name in the workspace. For example - I >> create a project called gateway-dev and have gateway-car, gateway-synapse, >> gateway-registry. I can't create a project with gateway-staging and have >> gateway-car. Is this an eclipse limitation? >> This is an eclipse limitation. Eclipse maintains a META file called >> .project for each and every project and the name in this .project file >> needs to be unique. >> >> 2) Can't have the same artifact name in the workspace. This one is bit >> annoying. I renamed the project to gateway-dev-synapse and >> gateway-staging-synapse. I can't have the api artifact with id.xml inside >> dev project and staging project in the same namespace:- the car picking >> form gets confused on the two assets. What's more - it will get corrupted >> and not have anything at all from synapse to pick. Below is an error that >> popped in the error console >> Yes, car files import artifacts based on the artifact name and in the >> artifact.xml of a car file it will list all the artifacts that needs to be >> bundled in that particular car, hence the artifact names needs to be unique >> for the car file. The error you have got is due to dev studio crashing >> before the file system files are properly refreshed, OR an attempt to >> manually edit the file system resources not via eclipse. Ideally this >> should be resolved by refreshing the workspace files through eclipse (right >> click the file and refresh) >> > > I agree that artifact name needs to be unqiue to the car file. But in a > scenario where you have 2 esb configuration projects having an artifact > with the same name (in-sequence.xml) - it crashes the car interface. > > > >> >> > 3) Deleting a resource (API) got me below error - >> Could you please let us know how to reproduce this? did you attempt >> to rename the resource before deleting? >> > This was the scenario where I had the same arifact name in 2 different > esb configuration projects. > > > >> >> 4) Bulk import for resources - >> You are correct, this is a current limitation. You can import the >> synapse configuration with multiple proxies in it and dev-studio will >> generate the proxies for different artifacts in the synapse configuration. >> But currently it is not supported to import multiple proxy.xml files >> simultaneously. >> >> Regards >> Awanthika >> >> >> Awanthika Senarath >> Software Engineer, WSO2 Inc. >> Mobile: +94717681791 >> >> >> >> On Wed, Dec 16, 2015 at 6:25 AM, Dulitha Wijewantha >> wrote: >> >>> Hi guys, >>> I got some issues today working on the developer studio. >>> >>> 1) Can't have the same project name in the workspace. For example - I >>> create a project called gateway-dev and have gateway-car, gateway-synapse, >>> gateway-registry. I can't create a project with gateway-staging and have >>> gateway-car. Is this an eclipse limitation? >>> >>> 2) Can't have the same artifact name in the workspace. This one is bit >>> annoying. I renamed the project to gateway-dev-synapse and >>> gateway-staging-synapse. I can't have the api artifact with id.xml inside >>> dev project and staging project in the same namespace:- the car picking >>> form gets confused on the two assets. What's more - it will get corrupted >>> and not have anything at all from synapse to pick. Below is an error that >>> popped in the error console - >>> >>> org.eclipse.core.runtime.CoreException: The file is not synchronized >>>
Re: [Dev] Dev studio errors and feedback
On Tue, Dec 15, 2015 at 10:26 PM, Awanthika Senarath wrote: > Hi Dulitha, > > Find my responses in-line, > > 1) Can't have the same project name in the workspace. For example - I > create a project called gateway-dev and have gateway-car, gateway-synapse, > gateway-registry. I can't create a project with gateway-staging and have > gateway-car. Is this an eclipse limitation? > This is an eclipse limitation. Eclipse maintains a META file called > .project for each and every project and the name in this .project file > needs to be unique. > > 2) Can't have the same artifact name in the workspace. This one is bit > annoying. I renamed the project to gateway-dev-synapse and > gateway-staging-synapse. I can't have the api artifact with id.xml inside > dev project and staging project in the same namespace:- the car picking > form gets confused on the two assets. What's more - it will get corrupted > and not have anything at all from synapse to pick. Below is an error that > popped in the error console > Yes, car files import artifacts based on the artifact name and in the > artifact.xml of a car file it will list all the artifacts that needs to be > bundled in that particular car, hence the artifact names needs to be unique > for the car file. The error you have got is due to dev studio crashing > before the file system files are properly refreshed, OR an attempt to > manually edit the file system resources not via eclipse. Ideally this > should be resolved by refreshing the workspace files through eclipse (right > click the file and refresh) > I agree that artifact name needs to be unqiue to the car file. But in a scenario where you have 2 esb configuration projects having an artifact with the same name (in-sequence.xml) - it crashes the car interface. > > 3) Deleting a resource (API) got me below error - > Could you please let us know how to reproduce this? did you attempt to > rename the resource before deleting? > This was the scenario where I had the same arifact name in 2 different esb configuration projects. > > 4) Bulk import for resources - > You are correct, this is a current limitation. You can import the > synapse configuration with multiple proxies in it and dev-studio will > generate the proxies for different artifacts in the synapse configuration. > But currently it is not supported to import multiple proxy.xml files > simultaneously. > > Regards > Awanthika > > > Awanthika Senarath > Software Engineer, WSO2 Inc. > Mobile: +94717681791 > > > > On Wed, Dec 16, 2015 at 6:25 AM, Dulitha Wijewantha > wrote: > >> Hi guys, >> I got some issues today working on the developer studio. >> >> 1) Can't have the same project name in the workspace. For example - I >> create a project called gateway-dev and have gateway-car, gateway-synapse, >> gateway-registry. I can't create a project with gateway-staging and have >> gateway-car. Is this an eclipse limitation? >> >> 2) Can't have the same artifact name in the workspace. This one is bit >> annoying. I renamed the project to gateway-dev-synapse and >> gateway-staging-synapse. I can't have the api artifact with id.xml inside >> dev project and staging project in the same namespace:- the car picking >> form gets confused on the two assets. What's more - it will get corrupted >> and not have anything at all from synapse to pick. Below is an error that >> popped in the error console - >> >> org.eclipse.core.runtime.CoreException: The file is not synchronized with >> the local file system. >> at >> org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338) >> at >> org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325) >> at >> org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233) >> at >> org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240) >> at >> org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) >> at >> org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) >> at >> org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) >> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) >> at >> org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) >> at >> org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) >> at >> org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) >> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) >> at >> org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) >> at >> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) >> >> >> org.eclipse.core.runtime.CoreException: The file is not synchronized with >> th
Re: [Dev] Dev studio errors and feedback
Hi Dulitha, Find my responses in-line, 1) Can't have the same project name in the workspace. For example - I create a project called gateway-dev and have gateway-car, gateway-synapse, gateway-registry. I can't create a project with gateway-staging and have gateway-car. Is this an eclipse limitation? This is an eclipse limitation. Eclipse maintains a META file called .project for each and every project and the name in this .project file needs to be unique. 2) Can't have the same artifact name in the workspace. This one is bit annoying. I renamed the project to gateway-dev-synapse and gateway-staging-synapse. I can't have the api artifact with id.xml inside dev project and staging project in the same namespace:- the car picking form gets confused on the two assets. What's more - it will get corrupted and not have anything at all from synapse to pick. Below is an error that popped in the error console Yes, car files import artifacts based on the artifact name and in the artifact.xml of a car file it will list all the artifacts that needs to be bundled in that particular car, hence the artifact names needs to be unique for the car file. The error you have got is due to dev studio crashing before the file system files are properly refreshed, OR an attempt to manually edit the file system resources not via eclipse. Ideally this should be resolved by refreshing the workspace files through eclipse (right click the file and refresh) 3) Deleting a resource (API) got me below error - Could you please let us know how to reproduce this? did you attempt to rename the resource before deleting? 4) Bulk import for resources - You are correct, this is a current limitation. You can import the synapse configuration with multiple proxies in it and dev-studio will generate the proxies for different artifacts in the synapse configuration. But currently it is not supported to import multiple proxy.xml files simultaneously. Regards Awanthika Awanthika Senarath Software Engineer, WSO2 Inc. Mobile: +94717681791 On Wed, Dec 16, 2015 at 6:25 AM, Dulitha Wijewantha wrote: > Hi guys, > I got some issues today working on the developer studio. > > 1) Can't have the same project name in the workspace. For example - I > create a project called gateway-dev and have gateway-car, gateway-synapse, > gateway-registry. I can't create a project with gateway-staging and have > gateway-car. Is this an eclipse limitation? > > 2) Can't have the same artifact name in the workspace. This one is bit > annoying. I renamed the project to gateway-dev-synapse and > gateway-staging-synapse. I can't have the api artifact with id.xml inside > dev project and staging project in the same namespace:- the car picking > form gets confused on the two assets. What's more - it will get corrupted > and not have anything at all from synapse to pick. Below is an error that > popped in the error console - > > org.eclipse.core.runtime.CoreException: The file is not synchronized with > the local file system. > at > org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338) > at > org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325) > at > org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233) > at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240) > at > org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at > org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at > org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) > at > org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) > at > org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) > at > org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) > at > org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) > at > org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > > > org.eclipse.core.runtime.CoreException: The file is not synchronized with > the local file system. > at > org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338) > at > org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325) > at > org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233) > at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240) > at > org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at > org.eclipse.ltk.core.refac
[Dev] Dev studio errors and feedback
Hi guys, I got some issues today working on the developer studio. 1) Can't have the same project name in the workspace. For example - I create a project called gateway-dev and have gateway-car, gateway-synapse, gateway-registry. I can't create a project with gateway-staging and have gateway-car. Is this an eclipse limitation? 2) Can't have the same artifact name in the workspace. This one is bit annoying. I renamed the project to gateway-dev-synapse and gateway-staging-synapse. I can't have the api artifact with id.xml inside dev project and staging project in the same namespace:- the car picking form gets confused on the two assets. What's more - it will get corrupted and not have anything at all from synapse to pick. Below is an error that popped in the error console - org.eclipse.core.runtime.CoreException: The file is not synchronized with the local file system. at org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325) at org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233) at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) org.eclipse.core.runtime.CoreException: The file is not synchronized with the local file system. at org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325) at org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233) at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) 3) Deleting a resource (API) got me below error - org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:4397) at org.eclipse.swt.SWT.error(SWT.java:4312) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:637) at org.eclipse.ltk.internal.ui.refactoring.ErrorWizardPage.performFinish(ErrorWizardPage.java:162) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:710) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.okPressed(RefactoringWizardDialog2.java:468) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable
