I fully agree that the javaagent has plenty of issues (both inOpenJPA, but mostly in Java itself) and shall only be used as last resort.
But I hope TomEE doesn't do any CMP processing anymore, isn't? That would be a shame, as CMP got ditched a long time ago and is not part of the EE6 WebProfile afaik, isn't? LieGrue, strub ----- Original Message ----- > From: Jean-Louis MONTEIRO <[email protected]> > To: [email protected] > Cc: > Sent: Thursday, July 12, 2012 3:13 PM > Subject: Re: javaagent? > > Hi, > > AFAIR, it's only used to enhance JPA entities because that is needed with > OpenJPA. > We cannot use the default openjpa javagent because of some classloader > reasons (classes must be enhanced first). > > Just be careful cause we currently support EJB 2 CMP entity beans. Behind > the cover, we use JPA and OpenJPA to manage CMP entities. That means if you > remove the javaagent, we won't be able to support CMP out of the box. > > Isn't it? > > Jean-Louis > > > 2012/7/12 Romain Manni-Bucau <[email protected]> > >> Hi, >> >> anyone has an idea why we use a javaagent? >> >> from what i saw it mainly runs the openjpa transformer... >> >> i don't really see why it is needed since if entities are enhanced at > build >> time that's more efficient and not needed, if the user wants to do it > at >> runtime he can add the openjpa javaagent. >> >> why i ask is mainly because in java it breaks the runtime because it tries >> to load the class we are loading the it leads to some LinkageErrors.... >> >> I would like to remove it from TomEE so please shout if yo uknow why we >> have it in place. >> >> - Romain >> >
