Add JEUS 8 as deployment target for CI

[arjantijms]

Next to GlassFish and WildFly there is one additional Java EE 7 implementation at the moment: JEUS 8. Although it's still in development it's already Java EE 7 certified.

I blogged about JEUS 8 here http://arjan-tijms.blogspot.com/2013/10/jeus-application-server-story-continues.html and here http://arjan-tijms.blogspot.com/2013/09/diving-into-unknown-jeus-application.html

There currently isn't an Arquillian container for JEUS, but I think a rudimentary one talking to the console deployer is probably not that hard to create (I can certainly look into creating one).

The developer preview can be freely and directly downloaded from http://tmaxsoft.com/product/jeus/certification

But, as JEUS is proprietary software I'm not sure if it's allowed to be used to run CI tests. We can always ask though ;)

[arun-gupta]

Adding this to our slew of test would be great! Do you want initiate conversation with JEUS ?

@aslakknutsen might be able to help you with Arquillian adapter ?

[blabno]

I'd love to learn how to create Arquillian container plugin so I'll assist you if Aslak guides us. 16 gru 2013 22:26 "Arun Gupta" [email protected] napisa³(a):

Adding this to our slew of test would be great! Do you want initiate conversation with JEUS ?

@aslakknutsen https://github.com/aslakknutsen might be able to help you with Arquillian adapter ?

Reply to this email directly or view it on GitHubhttps://github.com/javaee-samples/javaee7-samples/issues/172#issuecomment-30702355 .

[arjantijms]

I've had some email exchanges with Yoon Kyung Koo (JEUS' lead developer) in the past, so I can surely ask him.

Vineet Reynolds posted a rather detailed explanation on how to create an Arquillian container adapter here: http://arquillian.org/guides/developing_a_container_adapter

But just looking into the source code of existing adapters gives a lot of insight as well. There are a few options here;

1. Use a Java Process to execute the JEUS deployer command on the filesystems and provide commands/read the response via stdin/stdout. A few existing Arquillian adapters take the same approach.
2. Try to find out what protocol JEUS is using internally (if any) and use that directly. Maybe there's something about it in their documentation. It's rather thorough and contains info on a lot of internal implementations details.

[arjantijms]

I talked to Yoon. He thinks it's a really nice idea, but at the moment he's very busy. He hopes to be able to talk to marketing to provide us with either a trial or full license.

If I'm not mistaken, the JEUS trial license limits the number of concurrent users. Since only Jenkins uses the server this should be enough.

[aslakknutsen]

@arjantijms Any updates on this?

[arjantijms]

No updates yet, other than that I was just thinking this week about this issue ;) I'll contact Yoon to ask him how things are at his side. We should now also be a lot closer to the final release of JEUS, which makes for a better test target of course.