If there is no annotation i dont recall if the ra.xml is read. We have a
nested rar support in wars but it is really advanced and surely not desired
outside cloud hosting (where you dont have other choices).
In any case some repackaging is needed.
Le lun. 30 juil. 2018 22:08, David Jencks a
écr
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
> wrote:
>
> Hi
>
> The api part o
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 a
écrit :
> Hopefully someone who
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
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 sho
About production readiness of TomEE8:
I guess what Romain meant is that most parts which make up TomEE8 (Johnzon,
CXF, Tomcat, OWB, etc) are already used in production since a year. Even at
JavaEE8 level. There are only a few parts (BVal2) which only more recently made
the jump to EE8.
But eve
