Sure. Most Content Servers still require some type of database to persistently store the "content", right? So, the implementation of a Content Server could easily use Entities to define their data model and use generic JPA constructs to persist the data. Independent from any particular database implementation (ie. not dependent on specific JDBC or SQL dialects). Sounds like a good fit, from my personal perspective. :-)
Kevin On Thu, May 14, 2009 at 12:14 PM, shriram <[email protected]> wrote: > Hi, > > I work for a Documentum Based product development company. Is there any way > OpenJPA applied for Content Servers. > > Thanks > sriram > > > >
