You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Alex Soto <as...@gmail.com> on 2015/10/03 23:31:29 UTC
Arquillian Chameleon
Hello, I don't know if you are aware of arquillian chameleon (
https://github.com/arquillian/arquillian-container-chameleon) basically
this project acts as a container proxy for resolving which container and
mode you want to use in your tests, so you only need to modify one string
to change from one implementation or mode to another. For example:
<container qualifier="chameleon" default="true">
<configuration>
<property name="chameleonTarget">wildfly:8.0.0.Final:managed</property>
<property name="serverConfig">standalone-full.xml</property>
</configuration>
</container>
Notice that if you want to change to another version of wildfly, you only
need to change one string, Chameleon takes care of resolving the
dependencies and modifying the classpath. Currently we have support for
Wildfly, JBoss, Glassfish (with all modes) and also we have support for
TomEE managed. But we are facing some classloader problems with embedded
mode. You can see the commit here:
https://github.com/arquillian/arquillian-container-chameleon/commit/ead79be84b5db3e6f72211218384e6b9f1179030
We think that Arquillian Chameleon is going to be the future of Arquillian
for configuring the containers as well as it is going to be Arquillian
Universe (https://github.com/arquillian/arquillian-universe-bom) for
defining extensions.
I send this thread in the dev list because maybe this issue might require a
lot of discussion and maybe changes on code.
Cheers,
Alex.
Re: Arquillian Chameleon
Posted by Romain Manni-Bucau <rm...@gmail.com>.
What is needed we dont have? Seems nthg should be required from the
container excepted being mvn friendly isnt it? If not, tempted to say
chamrleon has some good contributions to come ;)
Le 4 oct. 2015 09:15, "Alex Soto" <as...@gmail.com> a écrit :
> The idea is standarize how to define containers, it is not a substitution
> but it is a way to group all of this so users don t need to learn of each
> dependency of each server. So you can use the old way (current) but also
> the chameleon way, and it seems that it is having a lot of acceptance in
> arquillian users. So I think that adding support for TomEE would be nice to
> have the complete profile there. As I said there is a starting point and it
> the problem is only the embedded mode
>
> Alex
> El dg, 4 oct 2015 a les 7:51 Romain Manni-Bucau <rm...@gmail.com> va
> escriure:
>
> > Hi
> >
> > Tomee supports it since years so not sure chamaleon would be used with
> > tomee in practise
> > Le 3 oct. 2015 23:31, "Alex Soto" <as...@gmail.com> a écrit :
> >
> > > Hello, I don't know if you are aware of arquillian chameleon (
> > > https://github.com/arquillian/arquillian-container-chameleon)
> basically
> > > this project acts as a container proxy for resolving which container
> and
> > > mode you want to use in your tests, so you only need to modify one
> string
> > > to change from one implementation or mode to another. For example:
> > >
> > > <container qualifier="chameleon" default="true">
> > > <configuration>
> > > <property
> > > name="chameleonTarget">wildfly:8.0.0.Final:managed</property>
> > > <property name="serverConfig">standalone-full.xml</property>
> > > </configuration>
> > > </container>
> > >
> > >
> > > Notice that if you want to change to another version of wildfly, you
> only
> > > need to change one string, Chameleon takes care of resolving the
> > > dependencies and modifying the classpath. Currently we have support for
> > > Wildfly, JBoss, Glassfish (with all modes) and also we have support for
> > > TomEE managed. But we are facing some classloader problems with
> embedded
> > > mode. You can see the commit here:
> > >
> > >
> >
> https://github.com/arquillian/arquillian-container-chameleon/commit/ead79be84b5db3e6f72211218384e6b9f1179030
> > >
> > > We think that Arquillian Chameleon is going to be the future of
> > Arquillian
> > > for configuring the containers as well as it is going to be Arquillian
> > > Universe (https://github.com/arquillian/arquillian-universe-bom) for
> > > defining extensions.
> > >
> > > I send this thread in the dev list because maybe this issue might
> > require a
> > > lot of discussion and maybe changes on code.
> > >
> > > Cheers,
> > > Alex.
> > >
> >
>
Re: Arquillian Chameleon
Posted by Alex Soto <as...@gmail.com>.
The idea is standarize how to define containers, it is not a substitution
but it is a way to group all of this so users don t need to learn of each
dependency of each server. So you can use the old way (current) but also
the chameleon way, and it seems that it is having a lot of acceptance in
arquillian users. So I think that adding support for TomEE would be nice to
have the complete profile there. As I said there is a starting point and it
the problem is only the embedded mode
Alex
El dg, 4 oct 2015 a les 7:51 Romain Manni-Bucau <rm...@gmail.com> va
escriure:
> Hi
>
> Tomee supports it since years so not sure chamaleon would be used with
> tomee in practise
> Le 3 oct. 2015 23:31, "Alex Soto" <as...@gmail.com> a écrit :
>
> > Hello, I don't know if you are aware of arquillian chameleon (
> > https://github.com/arquillian/arquillian-container-chameleon) basically
> > this project acts as a container proxy for resolving which container and
> > mode you want to use in your tests, so you only need to modify one string
> > to change from one implementation or mode to another. For example:
> >
> > <container qualifier="chameleon" default="true">
> > <configuration>
> > <property
> > name="chameleonTarget">wildfly:8.0.0.Final:managed</property>
> > <property name="serverConfig">standalone-full.xml</property>
> > </configuration>
> > </container>
> >
> >
> > Notice that if you want to change to another version of wildfly, you only
> > need to change one string, Chameleon takes care of resolving the
> > dependencies and modifying the classpath. Currently we have support for
> > Wildfly, JBoss, Glassfish (with all modes) and also we have support for
> > TomEE managed. But we are facing some classloader problems with embedded
> > mode. You can see the commit here:
> >
> >
> https://github.com/arquillian/arquillian-container-chameleon/commit/ead79be84b5db3e6f72211218384e6b9f1179030
> >
> > We think that Arquillian Chameleon is going to be the future of
> Arquillian
> > for configuring the containers as well as it is going to be Arquillian
> > Universe (https://github.com/arquillian/arquillian-universe-bom) for
> > defining extensions.
> >
> > I send this thread in the dev list because maybe this issue might
> require a
> > lot of discussion and maybe changes on code.
> >
> > Cheers,
> > Alex.
> >
>
Re: Arquillian Chameleon
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
Tomee supports it since years so not sure chamaleon would be used with
tomee in practise
Le 3 oct. 2015 23:31, "Alex Soto" <as...@gmail.com> a écrit :
> Hello, I don't know if you are aware of arquillian chameleon (
> https://github.com/arquillian/arquillian-container-chameleon) basically
> this project acts as a container proxy for resolving which container and
> mode you want to use in your tests, so you only need to modify one string
> to change from one implementation or mode to another. For example:
>
> <container qualifier="chameleon" default="true">
> <configuration>
> <property
> name="chameleonTarget">wildfly:8.0.0.Final:managed</property>
> <property name="serverConfig">standalone-full.xml</property>
> </configuration>
> </container>
>
>
> Notice that if you want to change to another version of wildfly, you only
> need to change one string, Chameleon takes care of resolving the
> dependencies and modifying the classpath. Currently we have support for
> Wildfly, JBoss, Glassfish (with all modes) and also we have support for
> TomEE managed. But we are facing some classloader problems with embedded
> mode. You can see the commit here:
>
> https://github.com/arquillian/arquillian-container-chameleon/commit/ead79be84b5db3e6f72211218384e6b9f1179030
>
> We think that Arquillian Chameleon is going to be the future of Arquillian
> for configuring the containers as well as it is going to be Arquillian
> Universe (https://github.com/arquillian/arquillian-universe-bom) for
> defining extensions.
>
> I send this thread in the dev list because maybe this issue might require a
> lot of discussion and maybe changes on code.
>
> Cheers,
> Alex.
>