Problem with a method specification [message #580794] |
Tue, 24 July 2007 23:56 |
Jorge Gomez Sanz Messages: 16 Registered: July 2009 |
Junior Member |
|
|
Hello all
It is me again.
This time I have one major issue: the configuration view and the library
view are not synchronized.
The capability patterns in the library view contain 12 elements, but the
same category in the configuration view shows only 5 entries.
Looking at my log I see this error output:
org.eclipse.emf.common.util.WrappedException:
org.eclipse.epf.persistence.MultiFileIOException: Resource is out of synch
and needs to be reloaded: /home/idk/EPF/Method
Libraries/Library1/INGENIAS-Basic-Plugin/capabilitypatterns/ design
environment view/content.xmi
at org.eclipse.epf.persistence.MethodLibraryPersister.delete(Un known
Source)
at
org.eclipse.epf.library.edit.command.DeleteMethodElementComm and.deleteContent(Unknown
Source)
at
org.eclipse.epf.library.edit.command.DeleteMethodElementComm and$3.run(Unknown
Source)
at
org.eclipse.epf.library.edit.ui.UserInteractionHelper$11.run (Unknown
Source)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:113)
Caused by: org.eclipse.epf.persistence.MultiFileIOException: Resource is out
of synch and needs to be reloaded: /home/idk/EPF/Method
Libraries/Library1/INGENIAS-Basic-Plugin/capabilitypatterns/ design
environment view/content.xmi
at
org.eclipse.epf.persistence.MultiFileSaveUtil.checkOutOfSync h(Unknown
Source)
at
org.eclipse.epf.persistence.MultiFileSaveUtil.checkOutOfSync h(Unknown
Source)
at
org.eclipse.epf.persistence.MethodLibraryPersister$FailSafeP ersister.save(Unknown
Source)
... 5 more
However, I am not able to tell when exactly the error. This are more or less
the steps I did.
The reasons for this change comes from an initial strange behavior of the
composer. Somehow, I still do not know the steps but I am working on it, I
was able to create a capability pattern that did not appear in the browser.
Looking at the corresponding folder in the hard disk, I saw the folder did
exist, thought it was not shown in the composer. To solve the issue, I
deleted the folder and refreshed the composer. Naturally, a reference
problem appeared in the file plugin.xml of the plugin method I was working
on. So I went to the file and deleted the troublesome reference. Now no
problems are shown.
It was working without errors, but the following made me think I did not fix
the problem. Now, the capability patterns in the library and the
configuration view show a different number of elements.
I tried to create new process categories and copy/paste the old patterns
into new folders, but it does not let me paste them with the same name (is
this the right behavior, unique capability pattern names despite the
process package?).
To fix the problem, I created a new plugin, pasted there the capabilities,
deleted original ones, and pasted again. Though I still had to recreate the
delivery process, now it works flawlesly.
Regards
Jorge
|
|
|
Powered by
FUDForum. Page generated in 0.01824 seconds