Re: Protocol of Arquillian Embedded Adapter
Hi Alex Local protocol allows nicer start so very tempted to keep it like that. Servlet protocol has few bugs/issues and is not what you target by default with embedded adapters IMO. Le 4 oct. 2015 01:25, "John D. Ament" a écrit : > Hey Alex, > > To be honest, I find the protocol section of arquillian the most confusing > for new users to pick up. Why should they care what the protocol > transferring the test data is using? I remember at the beginning, AS7 had > a JMX protocol. This made tons of sense, since it didn't impact the > running application. No one understood why their tests stopped work > though! Truth be told, the fact that most people end up relying on > servlet, without even realizing that its the arquillian runtime starting an > HTTP request makes it confusing to understand scope. Basically, users end > up relying on the servlet protocol to start their HTTP request for them, > instead of starting an HTTP request for their test invocation. > > Just curious, is this out on discourse somewhere? I can continue my whine > fest there :-) > > John > > On Sat, Oct 3, 2015 at 4:58 PM Alex Soto wrote: > > > Hello mates, > > > > I send this email to start a discussion for a change on TomEE Arquillian > > Adapter. > > > > The other day, because of the book (Arquillian In Action), I checked the > > protocol used by different adapters. I noticed that only Weld adapter and > > TomEE embedded adapter are using the local protocol,all other ones are > > using the Servlet 3.0 protocol. And maybe you are asking why this is > > important? Well the problem is that a lot of extensions requires this > > protocol to work, for example Arquillian Persistence extension or > Arquillan > > Warp extension. In case a user wants to use embedded TomEE and one > > extension that requires servlet protocol, it would get a cryptic > exception. > > Of course there is a workaround and it is overriding the default protocol > > by using protocol special tag in arquillian.xml and adding the > > servlet-protocol dependency. > > > > I think that it would be easier for everyone if all adapters works in the > > same way. With the release of TomEE 7 I think it could be a good > > opportunity to make this change in the Arquillian embedded adapter as > well > > and align with the rest of the containers. > > > > The change to be done is very simple in terms of code (Adding one > > dependency and change one String of the adapter). > > > > What do you think? From the point of view of Arquillian community it > would > > be the logic step. > > > > Alex. > > >
Re: Arquillian Chameleon
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" 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: > > > > name="chameleonTarget">wildfly:8.0.0.Final:managed > standalone-full.xml > > > > > 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: Protocol of Arquillian Embedded Adapter
Hey Alex, To be honest, I find the protocol section of arquillian the most confusing for new users to pick up. Why should they care what the protocol transferring the test data is using? I remember at the beginning, AS7 had a JMX protocol. This made tons of sense, since it didn't impact the running application. No one understood why their tests stopped work though! Truth be told, the fact that most people end up relying on servlet, without even realizing that its the arquillian runtime starting an HTTP request makes it confusing to understand scope. Basically, users end up relying on the servlet protocol to start their HTTP request for them, instead of starting an HTTP request for their test invocation. Just curious, is this out on discourse somewhere? I can continue my whine fest there :-) John On Sat, Oct 3, 2015 at 4:58 PM Alex Soto wrote: > Hello mates, > > I send this email to start a discussion for a change on TomEE Arquillian > Adapter. > > The other day, because of the book (Arquillian In Action), I checked the > protocol used by different adapters. I noticed that only Weld adapter and > TomEE embedded adapter are using the local protocol,all other ones are > using the Servlet 3.0 protocol. And maybe you are asking why this is > important? Well the problem is that a lot of extensions requires this > protocol to work, for example Arquillian Persistence extension or Arquillan > Warp extension. In case a user wants to use embedded TomEE and one > extension that requires servlet protocol, it would get a cryptic exception. > Of course there is a workaround and it is overriding the default protocol > by using protocol special tag in arquillian.xml and adding the > servlet-protocol dependency. > > I think that it would be easier for everyone if all adapters works in the > same way. With the release of TomEE 7 I think it could be a good > opportunity to make this change in the Arquillian embedded adapter as well > and align with the rest of the containers. > > The change to be done is very simple in terms of code (Adding one > dependency and change one String of the adapter). > > What do you think? From the point of view of Arquillian community it would > be the logic step. > > Alex. >
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: wildfly:8.0.0.Final:managed standalone-full.xml 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.
Protocol of Arquillian Embedded Adapter
Hello mates, I send this email to start a discussion for a change on TomEE Arquillian Adapter. The other day, because of the book (Arquillian In Action), I checked the protocol used by different adapters. I noticed that only Weld adapter and TomEE embedded adapter are using the local protocol,all other ones are using the Servlet 3.0 protocol. And maybe you are asking why this is important? Well the problem is that a lot of extensions requires this protocol to work, for example Arquillian Persistence extension or Arquillan Warp extension. In case a user wants to use embedded TomEE and one extension that requires servlet protocol, it would get a cryptic exception. Of course there is a workaround and it is overriding the default protocol by using protocol special tag in arquillian.xml and adding the servlet-protocol dependency. I think that it would be easier for everyone if all adapters works in the same way. With the release of TomEE 7 I think it could be a good opportunity to make this change in the Arquillian embedded adapter as well and align with the rest of the containers. The change to be done is very simple in terms of code (Adding one dependency and change one String of the adapter). What do you think? From the point of view of Arquillian community it would be the logic step. Alex.
