|Re: Persisting the Eclipse Application? [message #1008535 is a reply to message #1008526]
||Tue, 12 February 2013 21:53
| Thomas Schindl
Registered: July 2009
When it comes to loading/saveing I'd suggest to you serialize your stuff
e.g. as XML and use JAXB to bind it to a bean.
The model loading/saveing is done through the IModelResourceHandler you
can force the framework to use your custom one by passing something like
Am 12.02.13 21:39, schrieb Alex Kipling:
> Thnx Thomas, setting persisten state on model elements, as described
> was a really useful buzzword, thnx Tom.
> What I would like to do is saving a bunch of attributes, for every part.
> (Integer, maybe Serializables)
> These attributes I would like to save in a DB,
> so I thought about using Eclipse's persistency mechanism, and
> implementing it's interfaces.
> Do you know which mechanism is responsible for persisting a model on
> application stop?
> Where do I have too hook in, in order to change the save location from
> Eclipse's native location to my DB?
Powered by FUDForum
. Page generated in 0.21869 seconds