EMFT Texo: EMF – RCP persistence using Texo generated JPA entities
Hi!
After working on Texo JSON Rest, the next step for me has been to implement an EMF Resource which persists its data using JPA annotated entities in a standard ORM.
This makes it possible to use Texo in a RCP environment with an EMF generated front-end and a Texo generated JPA backend.
The first implementation of the TexoResource supports a 2-tier architecture: the JPA TexoResource communicates directly with the database through the JPA/ORM layer.
My next step will be to implement a Texo JSON Resource which communicates using JSON with a server running Texo. The server side of this 3 tier architecture is already done: the Texo JSON web service layer. For an example project running Texo in Tomcat/web container check out this wiki page or see this video.
For this new development I am developing EMF JSON converters, these could be useful also in other solutions, you can find the relevant plugin here in git.
I am cooperating with others to develop an example RCP using Texo. My goal is to provide more example projects. If you are interested in cooperating on this, ping me on the Texo forum.
Thanks for reading and I hope this blog post helps to give Texo a try. Visit the Texo wiki for more information. Let me know if you have any questions or remarks on the EMFT newsgroup or forum!
gr. Martin

[...] supporting a 2-tier architecture it is now time to make the step to a full 3-tier application architecture for EMF [...]
Taking EMF to the third tier: the Texo JSON Resource « Martin Taal's Blog
August 30, 2012 at 12:21 am
Hi Martin, What would it take expose CDO Objects as JSON data which can be retrieved with Rest, SOAP or other HTTP carried XML formats?
Christophe Bouhier
January 10, 2013 at 8:16 am
Hi Christophe,
Interesting question!
Texo provides an EMF-JSON serializer so EMF generated objects (like CDO objects) can be json serialized to. This is also being used in the TexoJSONResource provided by Texo.
There are some tricky details related to proxying but these are handled in Texo so it should be quite okay to handle this in CDO also.
It would be a nice addition to CDO, so let me know, maybe I can spend some time on this.
Also feel free to ask on the newsgroup then we can discuss more.
gr. Martin
http://git.eclipse.org/c/texo/org.eclipse.emf.texo.git/tree/core/org.eclipse.emf.texo.json/src/org/eclipse/emf/texo/json/JSONEObjectStore.java#n237
http://git.eclipse.org/c/texo/org.eclipse.emf.texo.git/tree/core/org.eclipse.emf.texo.json/src/org/eclipse/emf/texo/json/JSONEMFConverter.java
http://git.eclipse.org/c/texo/org.eclipse.emf.texo.git/tree/core/org.eclipse.emf.texo.json/src/org/eclipse/emf/texo/json/EMFJSONConverter.java
martintaal
January 10, 2013 at 3:09 pm