But even with Arquillian we would need ShrinkWrap to build deployable
artifacts. Or what do you mean? For SE we need only to tweak our class
path or class loader.
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
