I was actually thinking of putting the entire classes jar from inside the rar into the ear lib module, not exploding the rar. There weren’t any annotations in the last rar spec I worked with…
David Jencks > On Jul 30, 2018, at 12:33 PM, Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > > Hi > > The api part of the rar should be shared so put it in tomee/lib (or the ear > lib module). Worse case, David's trick of exploding the rar in the ear can > work if it uses annotations (just put it in any scanned module). > > Le lun. 30 juil. 2018 21:09, David Jencks <david.a.jen...@gmail.com> a > écrit : > >> Hopefully someone who actually knows something will speak up soon… >> You might try putting the rar classes in a lib jar in the ear. I don’t >> recall if you have to do something with the manifest class path in the ejb >> module and rar to get this to work. >> >> David Jencks >> >>> On Jul 30, 2018, at 11:16 AM, ChrisOwens <ch...@chris-owens.com> wrote: >>> >>> I am deploying (tomEE-plus 7.0.5) an EAR file that contains two modules: >> a >>> JCA connector defined in a rar file, and a JAR full of ejbs. The EJBs >>> contain classes that depend upon classes packaged in the RAR. >>> >>> Whether or not I set "initialize-in-order" to true, I get the same >> behavior: >>> The logs show no evidence that the server has tried to deploy the RAR, >>> instead it begins deploying the ejb module, and fails with >>> NoClassDefFoundError. >>> >>> If I delete the ejb module from the ear, leaving only the rar module, and >>> deploy the ear, the server appears to deploy the rar module happily. >>> >>> Jonathan Gallimore posted something a while back that I thought was >> related >>> to this problem, something about resource adapter class loading being >> lazy; >>> I thought there was even a pull request for it, but I can't seem to find >> any >>> of that now. >>> >>> Is there a workaround? >>> >>> >>> >>> >>> >>> >>> -- >>> Sent from: >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >> >>
