Hi Gene, This message means that the entity's finder select statement (the one used when you perform an EM.find() operation) was not cacheable. OpenJPA attempts to cache as much reusable data as possible for most efficient operation. But, in this case, you don't really care that it's not cacheable (for whatever reason). When we can cache the finder, the message is just a Trace message. It looks like this message should also be a Trace message and not an WARN. If you have the ability, please open a JIRA on this. I will also copy Pinaki since I believe he was the implementer of the function...
Thanks, Kevin On Wed, Feb 17, 2010 at 2:40 PM, Gene Shaw <[email protected]> wrote: > Trying out the 2.0.0-Beta version of OpenJPA in our application which is > currently using the 1.2.1 version of OpenJPA. I am getting a warning > message > that certain classes are not cachable. > > Using the following settings to enable caching > > <property name="openjpa.DataCache" value="true(CacheSize=5000, > SoftReferenceSize=0)"/> > <property name="openjpa.RemoteCommitProvider" value="sjvm"/> > > > And here are some examples of the warning message > > WARN [AWT-EventQueue-0] (Log4JLogFactory.java:89) - Finder for > "com.ogre.continuum.primitives.openjpa.TextImpl" is not cachable. > WARN [AWT-EventQueue-0] (Log4JLogFactory.java:89) - Finder for > "com.ogre.continuum.primitives.openjpa.DigitalStreamImpl" is not cachable. > WARN [AWT-EventQueue-0] (Log4JLogFactory.java:89) - Finder for > "com.ogre.continuum.primitives.openjpa.TextImpl" is not cachable. > WARN [AWT-EventQueue-0] (Log4JLogFactory.java:89) - Finder for > "com.ogre.continuum.primitives.openjpa.TextImpl" is not cachable. > > I searched through the documentation and didn't see much mentioned about > the Finder. Would should I do too go about correcting this issue? > > >
