|
|
|
|
|
Re: Persisting the generated implemented class in Sapphire [message #760900 is a reply to message #760673] |
Mon, 05 December 2011 14:38 |
Konstantin Komissarchik Messages: 1077 Registered: July 2009 |
Senior Member |
|
|
Quote:Could you please demonstrate what you advise with some small snippets?
We don't have a ready-made sample for this and it is more than could be put together quickly for a forum post. Take a look at Sapphire's Resource API and refer to XmlResource for a concrete implementation example.
Quote:Whenever your JPA generator matures, please consider those of us who use JDO.
We are fundamentally limited in what we can support with existing people contributing to the project. Large expansions in scope (such as supporting JPA or JDO) will likely require an interested party to come forward willing to contribute to the implementation. A bit ago, I thought we had such contributor lined up for JPA support, but he walked away before the task got started.
Quote:NB: To what database can one currently persist Sapphire's model?
Sapphire natively implements support for in-memory persistence and for XML persistence. Everything else would need to be done through a custom Resource implementation. As such, Sapphire doesn't natively support persistence to any database, but an adopter could implement it for any database they choose.
- Konstantin
[Updated on: Mon, 05 December 2011 14:39] Report message to a moderator
|
|
|
Re: Persisting the generated implemented class in Sapphire [message #760982 is a reply to message #760900] |
Mon, 05 December 2011 18:46 |
St Clair Clarke Messages: 118 Registered: March 2010 |
Senior Member |
|
|
Hello Konstatin,
Quote:Sapphire natively implements support for in-memory persistence and for XML persistence. Everything else would need to be done through a custom Resource implementation. As such, Sapphire doesn't natively support persistence to any database, but an adopter could implement it for any database they choose.
It would seem that Sapphire currently had quite a limited user base in mind when its main form of persistence is XML. Or is it that Sapphire is simply attempting to garner a niche market - XML persistence to be specific.
I would think that currently the majority of database persistence is still related to relational databases, yet there is no obvious mechanism for that.
Please point me to Sapphire's scope for me to take a closer look as to what the framework hopes to accomplish.
Currently it seems that the UI aspect of the framework is brilliant, but what can be done with this UI out-of-the-box is quite limited.
I would not want to simply change to XML persistence just because Sapphire supports it.
Thanks
[Updated on: Mon, 05 December 2011 18:53] Report message to a moderator
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04431 seconds