Just for my knowledge why classloader rule solution is not an option? If we start using remote solutions we ll have other issues (we need random ports at least) and how do you simulate provided libs? + There are alternative like pax and karaf testing integration. All looks complicated for compared to what we actually need
Wdyt? Le 1 févr. 2015 22:31, "Oliver B. Fischer" <[email protected]> a écrit : > Hi, > > it seems so that the Arquillian daemon is exactly doing what we need: > > https://github.com/arquillian/arquillian-daemon > > Bye, > > Oliver > > Am 29.01.15 um 08:31 schrieb Mark Struberg: > >> That's why I wanted some 'isolating' Arquillian SE adaptor :) >> I prefer using Arquillian over any homegrown solution as we might use >> that to later test EE containers as well. >> >> LieGrue, >> strub >> >> >> >> >> On Thursday, 29 January 2015, 0:33, Romain Manni-Bucau < >>> [email protected]> wrote: >>> have a test classloader, should be far enough and avoid to depend on >>> SW and having to create archives (we just switch the classloader which >>> knows the SPI we want and that's it). >>> >>> >>> Romain Manni-Bucau >>> @rmannibucau >>> http://www.tomitribe.com >>> http://rmannibucau.wordpress.com >>> https://github.com/rmannibucau >>> >>> >>> >>> 2015-01-29 0:28 GMT+01:00 Oliver B. Fischer <[email protected]>: >>> using >>> self-defined >>> >> > -- > N Oliver B. Fischer > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > P +49 30 44793251 > M +49 178 7903538 > E [email protected] > S oliver.b.fischer > J [email protected] > X http://xing.to/obf > >
