6 Replies Latest reply on Feb 13, 2010 10:57 AM by Jeremy Norris

    It's time for jboss-as:run :)

    Jeremy Norris Newbie

      Speaking of priorities, I personally would love to see JBoss AS embedded support first.  I think there is large, pent up demand for Arquillian, specifically the embedded testing scenarios.  I know that I have 100's of tests just waiting to be converted (and extended!).  I'll do this almost immediately as soon the first embedded Arquillian solution is ready.  This is a big opportunity for JBoss AS to get some serious traction very quickly.

        • 1. Re: It's time for jboss-as:run :)
          Andrew Rubinger Master

          By jboss-as:run you mean a Maven plugin?

           

          I think an EmbeddedAS Arquillian container is not far in the offiing; the next step I'll be doing is hacking through to enable direct Embedded container support.  Probably starting w/ OpenEJB or GlassFish.  With another release of AS 6.0.0.M2 and EmbeddedAS to follow soon behind.

           

          S,

          ALR

          • 2. Re: It's time for jboss-as:run :)
            Jeremy Norris Newbie

            ALRubinger wrote:

             

            By jboss-as:run you mean a Maven plugin?

             

            I was just going for the catchy title.  I want the spirit of "jetty:run" on top of Arquillian's container abstraction engine

             

            But of course, primarily, I want an EmbeddedAS Arquillian container.

             

            I understand and agree with the design goal that Dan mentioned on a previous thread of "you don't have to modify your test plugin to use Arquillian" (ie: no maven plugins required).  This is great for Arquillian as a test framework.  However, longer term there may be an opportunity to leverage whatever the container configuration strategy becomes.  A maven plugin could use this information and the accompanying ShrinkWrap information to launch it "jetty:run" style on any configured container.  However, I may be getting ahead of ourselves here.

            ALRubinger wrote:

             

            By jboss-as:run you mean a Maven plugin?

             

            I think an EmbeddedAS Arquillian container is not far in the offiing; the next step I'll be doing is hacking through to enable direct Embedded container support.  Probably starting w/ OpenEJB or GlassFish.  With another release of AS 6.0.0.M2 and EmbeddedAS to follow soon behind.

             

             

            This may not be practical, but it would be a huge boon for the EmbeddedAS project if somehow Arquillian had EmbeddedAS support out of the gate.

            • 3. Re: It's time for jboss-as:run :)
              Aslak Knutsen Master

              According to German, Jboss AS Embedded integration should be working again now.. http://community.jboss.org/message/525833

               

               

              We are looking into having a Maven jetty:run style plugin.. https://jira.jboss.org/jira/browse/ARQ-14

              jetty:run for your test cases doesn't really make any sense, so I guess you should be able to specify a set of @Deployment classes that should be deployed on start.. not really given it much thought yet.. Feel free to layout some ideas..

               

               

              • 4. Re: It's time for jboss-as:run :)
                Andrew Rubinger Master

                EmbeddedAS as it is now should work, kinda.  The reason I mentioned the next release is to hopefully work out a couple of ClassLoading scenarios which allow AS to boot in a non-flat (ie. everything on --classpath) model.  Plus there's the whole "ShrinkWrap versions don't match right now" issue, which will become moot after we freeze the API.

                 

                S,

                ALR

                • 5. Re: It's time for jboss-as:run :)
                  Aslak Knutsen Master
                  ohh yea, right.. forgot about ShrinkWrap..
                  • 6. Re: It's time for jboss-as:run :)
                    Jeremy Norris Newbie

                    We are looking into having a Maven jetty:run style plugin.. https://jira.jboss.org/jira/browse/ARQ-14

                    jetty:run for your test cases doesn't really make any sense, so I guess you should be able to specify a set of @Deployment classes that should be deployed on start.. not really given it much thought yet..

                    This is basically taking the container selection and configuration system (that isn't fully designed yet) and the @Deployment definitions and putting a jetty:run system around it.  This is still valuable for some types of "integration testing" as you can tie the "jetty:run" into the maven lifecycle and have other completely unrelated systems and plugins run tests against it externally.  But, yes, this is a side point to Arquillian's primary value.  I just was getting exciting thinking about the powerful constructs that could be built with Arquillian's primitives