openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Prud'hommeaux <>
Subject Re: When to use AbstractStoreManager?
Date Fri, 22 Jun 2007 01:15:00 GMT

You are correct: OpenJPA was designed to allow the modular  
development of a custom back-end using the AbstractStoreManager for  
the basic data store operations. Many of the base methods allow you  
to develop the interactions in a naive way, and then make them more  
performant and sophisticated over time.

We even have an example implementation of a custom StoreManager that  
simply stores data in XML files: you can see the code at https:// 
org/apache/openjpa/xmlstore/ or browse the javadocs at http:// 

We're always excited when people use that aspect of the architecture,  
so we would be interested to learn whether you decide to use it or not.

On Jun 21, 2007, at 5:59 PM, Ed Hillmann wrote:

> Hi all.  I'm investigating the abilities of JPA against a custom API
> for data definition and retrieval.  While 99.99% of the JPA examples
> I've seen allow you to define your plain Java object against database
> objects, that's not the scenario I'm presented with.
> I've attempting to write a client application against a known API.
> There is an existing API of procedure calls to server processes that I
> must use in order to display and handle the data.
> I've come across the OpenJPA class called AbstractStoreManager.  From
> what I can tell, this can be used to support non-JDBC datastores into
> the OpenJPA environment.  Is this correct?  If so, it looks like this
> is what I would need to implement.
> Has anyone used this?  Am I misunderstanding for what this class is  
> intended?
> Thanks for any help,
> Ed

View raw message