Here is an example, We are going to allow third-party developers to specify custom schema of their objects and relationships between these objects at our runtime system, and we will save the meta-info into our database. In return, with the meta-info, we will generate these custom objects according to the client system third-party developers are using.
When third-party developers take these generated objects, they can start composing object-graph at client side and we will have an API to take the serialized object graph, deserialize it and use hibernate to persistent the graph. In ideal case, we need the object graph be able to contain mixed native objects and custom objects, mixed newly created objects and existing objects. The problem arises in several ways, 1) We don't know how many custom-objects we will have in an open runtime system, we tend not to generate corresponding runtime types at server side. We are thinking to have just one compile-time master type at server side which can represent whatever custom objects 2) If #1 assumption stays, which means that we need to help Hibernate to finish some work in doing the right mapping and also generate the right SQL queries to deal with the collapsing of custom tables to physical tables. Is this archievable with current Hibernate architecture already? If not, technically, is it doable in some way by customizing Hibernate? (I'm pretty new to Hibernate) Thanks very much Kelven On Wed, Mar 25, 2009 at 2:58 PM, Fabio Maulo <[email protected]> wrote: > Make here an example of "custom object" and how you want persist one with a > relation and a collection. Perhaps NH2.1.0 has what you are looking for. > > 2009/3/25 kelveny <[email protected]> > > >> We've developed a storage model which can allow virtual custom tables >> to be collapsed to a fix number of physical tables, the idea of this >> is to allow third-party developers to develop and deploy new features >> with custom objects on top of our runtime system. >> >> We've been heavily used Hibernate for our native objects, with this >> new feature requirement, we would like to extend the same model to >> third-party developers, which means, to extend Hibernate ORM power >> across native objects and custom objects. >> >> From Hibernate perspective, make its mapping layer work on these >> custom object, how ambitious is it, or if not, what is the best >> approach to do so? >> > > > > -- > Fabio Maulo >
