Hi Eric, Do you have a stack trace for the RuntimeException? It would be interesting to see who is looking for the missing field. The OpenJPAConfigurationImpl class contains a field named brokerPlugin. In 1.0.2 the field is of type ObjectValue, in 1.2.0 it's been changed to type BrokerValue. The caller might be looking for the old type.
-Mike On Tue, Jul 1, 2008 at 1:40 PM, Eric Nelson <[EMAIL PROTECTED]> wrote: > Hi all. My current project is using OpenJPA 1.0.2 and has been working > beautifully for months now. I recently grabbed the newly released 1.1.0 > version, dropped in the openjap.jar and serp.jar into my classpath, > started the server and got: > > > > --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- > > ObjectName: > persistence.units:ear=eship.ear,jar=eshipEJB.jar,unitName=unishippers > > State: FAILED > > Reason: java.lang.RuntimeException: java.lang.NoSuchFieldError: > brokerPlugin > > > > in my main EAR file. I didn't change anything else, just dropped in the > new JAR's. I've done this in the past with new versions of OpenJPA with > no problems. I did remember to re-enhance my entity beans after adding > the new JAR's, so I'm at a loss as to what is causing this problem. Any > help would be greatly appreciated. > > > > Thanks, > > > > Eric > >
