Community
Participate
Working Groups
In theory it should be possible to persist the state of an RCP app to any store that can implement IMemento. Unfortunately there is no Memento factory or something like it, in fact the creation of IMemento objects is hard coded to XMLMemento in many places. Ideally there should be an IWOrkBench.setMementoFactory call that an Advisor calls at startup - and this factory should then be used throughout to create and IMemento objects
Reassigning...
Reassigning bugs in component areas that are changing ownership.
I agree. I think the only thing that really needs to happen to the interface itself is to add a getElementTypes() method (or something similar); as it stands right now it is impossible to implement all the interface methods simply because this is information can not be retrieved without casting to a XMLMemento (see javadoc for IMemento.putMemento(IMemento memento)). Of course, XMLMemento itself should also be cleaned up so that it won't generate ClassCastExceptions when trying to perform operations on non-XMLMemento mementos. > In theory it should be possible to persist the state of an RCP app to any store > that can implement IMemento. Unfortunately there is no Memento factory or > something like it, in fact the creation of IMemento objects is hard coded to > XMLMemento in many places. > Ideally there should be an IWOrkBench.setMementoFactory call that an Advisor > calls at startup - and this factory should then be used throughout to create > and IMemento objects >
A patch would be welcome... http://wiki.eclipse.org/Platform_UI/How_to_Contribute
Just wanted to add a note, one big problem with always using XMLMemento is that RCP clients will have to know that that is what is being used because XMLMemento requires you use keys and values that represent valid XML otherwise an exception is thrown. This behavior isn't obvious until it happens at runtime either. I'm trying to see if a bug report exists for this already- if not I'll submit one.
Prakash is now responsible for watching bugs in the [RCP] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
