-
1. Re: Arquillian with jboss 4.2.3
aslak May 21, 2010 12:39 PM (in response to vra5107)Sorry for the delayed response..
We currently do not have any support for JBoss 4.2.x or Seam 2, but there are some interest / work being done in the community to support it. But no timeline on this yet I'm afraid.
If you want to help out, your very welcome..
-
2. Re: Arquillian with jboss 4.2.3
vra5107 May 23, 2010 6:51 AM (in response to aslak)Aslak
Thanks for the reply. I found cargo plugin for maven since I posted this question. It would have been interesting to put Arquillian to use. Hope to contribute to Arquillian.
Venkat
-
3. Re: Arquillian with jboss 4.2.3
sten_aksel Jun 3, 2010 2:22 AM (in response to vra5107)Hi
You may find the code here of some value: http://code.google.com/p/seam-maven-refimpl/
From Getting Started:
"Due to problems booting the JBoss Micro Container with Maven, we have choosen to use the Apache OpenEJB embedded container to run Seam (and EJB-3.x) integration tests. The seam-refimpl project template comes preconfigured with the Apache OpenEJB embedded container for running tests"
- Sten Aksel
-
4. Re: Arquillian with jboss 4.2.3
vra5107 Jul 15, 2010 6:45 PM (in response to sten_aksel)Thanks for the reply Sten. I did find your post on this issue, but wanted to stick to jboss for various reasons. I am yet to write my first integration test but progressing well with the help of the os community.
-
5. Re: Arquillian with jboss 4.2.3
dan.j.allen Jun 7, 2010 10:36 PM (in response to vra5107)We have been trying to setup integration testing for our maven seam jboss 4.2.3 project. I have spent way too much time trying to setup SeamTest based integration testing but ended up where I started.
That's exactly why we are working on Arquillian. Integration testing Java EE has been a pain. While SeamTest had a compelling approach, it introduced it's own complexity that ultimately led to pain and failure. With Arquillian, we are committed to making it easy, elegant and powerful. Please hold us to those goals
-
6. Re: Arquillian with jboss 4.2.3
dan.j.allen Jul 15, 2010 6:48 PM (in response to vra5107)With the OSS community at your side, it's truly amazing the types of challenges you can overcome. We like hearing that
An Arquillian container for JBoss AS 4.2.3 is certainly possible. After having done two container implementations just this past weekend, I can tell you from first-hand experience that it's not particularly difficult (just requires patience). It's really just a matter of figuring out how you are going to deploy and undeploy an application. JBoss AS has long supported remote deployments, so with a little digging and persistence, you should be able to get it working (hint, search for Deployment Manager or Web Manager).
If all else fails, you can try using the JSR 88 container support I attached to ARQ-156.
(Note: this is not a new post. I reposted because the reply somehow got associated with the wrong author).
-
7. Re: Arquillian with jboss 4.2.3
aslak Jul 16, 2010 3:12 AM (in response to dan.j.allen)I have a DeployableContainer implementation for JBoss AS 4.2 Remote that I did during JBoss World locally(not committed yet).
It looks up the RMIAdaptor via JNDI to invoke the MainDeployer. It works for deployment, but the problem is with EE 4 you need all the Descriptors like web.xml, application.xml etc. We have poor support for dynamic descriptor atm so the deployment fails..
I was thinking of revisiting this when we get the Descriptors project up and running..
-
8. Re: Arquillian with jboss 4.2.3
michaelschuetz Aug 1, 2010 4:52 PM (in response to aslak)Hi,
what's the status on this?
Is it scheduled?
Is help appreciated?
Would a github fork make sense?
thanks and regards
Michael
-
9. Re: Arquillian with jboss 4.2.3
aslak Aug 2, 2010 6:52 AM (in response to michaelschuetz)JBoss AS 4.2.3 as a Container is working locally here, the problem is the descriptors that EE4 need; applications.xml etc.
Arquillian / ShrinkWrap does not have a good way of handling them at the moment. but we have a descriptors prototype project: http://github.com/shrinkwrap/descriptors
This project need help. We're looking for someone that wants to drive it/ join in.
- Formalize, Stabilize, Unify APIs
- Make APIs extendable / dynamic loading etc alla ShrinkWrap.
- Descriptor versioning, EE 4, 5, 6 etc
- ShrinkWrap integration, should Descriptors be a separate project with a ShrinkWrap 'adaptor' or be more integrated with ShrinkWrap.
- Every proper project needs a good name
- etc etc etc
Michael, you have any spare proud soldiers?
-
10. Re: Arquillian with jboss 4.2.3
michaelschuetz Aug 3, 2010 5:53 PM (in response to aslak)Aslak, thanks for pointing this out.
Would you mind creating a JIRA issue for JBoss 4.2.3 support?
So how many watchers would this JIRA ticket need to attract you attention and schedule this within one of the next releases?
Michael, you have any spare proud soldiers?
Hm, yes - perhaps there might be an option.
-
11. Re: Arquillian with jboss 4.2.3
aslak Aug 3, 2010 6:21 PM (in response to michaelschuetz)Michael Schuetz wrote:
Aslak, thanks for pointing this out.
Would you mind creating a JIRA issue for JBoss 4.2.3 support?
https://jira.jboss.org/browse/ARQ-238
So how many watchers would this JIRA ticket need to attract you attention and schedule this within one of the next releases?
Good question..
I'll make a ARQ-238 branch in my arq repo tomorrow and push the container implementation I have so far. Using Run(AS_CLIENT) should work, since Arq does not need to touch the deployment in that case. That means any form of Remote testing is doable now.
-aslak-
-
12. Re: Arquillian with jboss 4.2.3
michaelschuetz Aug 3, 2010 7:29 PM (in response to aslak)I'll make a ARQ-238 branch in my arq repo tomorrow and push the container implementation I have so far. Using Run(AS_CLIENT) should work, since Arq does not need to touch the deployment in that case. That means any form of Remote testing is doable now.
Great. Thanks a lot.
Michael
-
13. Arquillian with jboss 4.2.3
davided80 May 6, 2011 7:55 PM (in response to michaelschuetz)Here's my prototype: https://github.com/DavideD/arquillian/commits/ARQ-238
It adds the managed and the remote container.
I took the branch from Aslak's repository and fix the compilation error because of the latest changes in Arquillian.
I've followed the wiki about JSR88 at http://community.jboss.org/wiki/JSR88Client
I have to clean it but it seems to work. I would appreciate some feedback though.
Cheers,
Davide