I haven't looked at this particular code in quite a while, but I would expect you'd only get this error if some of your application code managed to load the unenhanced class not through jpa before aries had a chance to install the class weaver.
You are running with an osgi 4.3 framework so runtime weaving works? And you have all the necessary aries bits for this to work installed (not that I know exactly which ones they are)? thanks david jencks On May 27, 2012, at 2:05 PM, Balázs Zsoldos wrote: > Hi, > > thanks for the quick response. However I was interested in a slightly > different question. I had the following specific exception: > > <openjpa-2.2.0-r422266:1244990 nonfatal user error> > org.apache.openjpa.persistence.ArgumentException: This configuration > disallows runtime optimization, but the following listed types were not > enhanced at build time or at class load time with a javaagent: " > > If the Entity bundle is started before the JPA container picks it up OpenJPA > will not really work. I found an interesting paragraph in the documentation > of Gemini-JPA that is a hack to solve this problem at > http://wiki.eclipse.org/Gemini/JPA/Documentation/OtherTopics. It refreshes > the entity bundle if it is already resolved when Gemini JPA Container picks > it up. Well it sounds a bit sick but at least it may work... Does the aries > container do tricks like this? > > This is not that urgent to me as I was on EclipseLink before until I found > out that it cannot handle more difficult SQL queries. Hibernate could however > it uses solutions (storing the classes in static maps as cache). A couple of > days ago someone on this mail list (or the dev one) noted that OpenJPA is > more OSGI friendly that is why I thought it would be worthy to have a look on > it. > > Regards, > Balazs Zsoldos > Software Architect > Mobile: +36-70/594-92-34 > > Everit Kft. > https://www.everit.biz > > > > > On Sun, May 27, 2012 at 10:30 PM, James Carman <[email protected]> > wrote: > If you're using Aries' JPA support, then it won't start up an entity > manager for your bundle until a JPA provider (like OpenJPA) is > available for it. > > On Sun, May 27, 2012 at 4:04 PM, Balázs Zsoldos > <[email protected]> wrote: > > Hi, > > > > I checked the OpenJPA-OSGI possibilities and the following question came > > into my mind: > > > > - Is it a requirement for OpenJPA that the OpenJPA bundle has to start > > before the one that contains Entity classes? > > > > I know in live OSGI containers admins can play with start levels however it > > makes life very hard if we have to always think in which order we want to > > start our bundles. I did not have these problems with EclipseLink and > > Hibernate (I had different ones :)). > > > > Is there any possibility that OpenJPA-OSGI relationship will be enhanced > > somewhen in the way that no start ordering will matter and nor OpenJPA > > specific compilation neither javaagent usage will be necessary? > > > > Regards, > > Balazs Zsoldos > > Software Architect > > Mobile: +36-70/594-92-34 > > > > Everit Kft. > > https://www.everit.biz > > > > >
