[jboss-as7-dev] Arquillian and JPDA on AS7

Andrew Lee Rubinger andrew.rubinger at redhat.com
Wed Mar 30 19:34:06 EDT 2011



On 03/30/2011 03:26 PM, Max Rydahl Andersen wrote:
>>> IMO Starting/Stopping AS for debugging/"real" testing is done from command line scripts or if using an IDE for it with whatever mechanism they use (which aren't ARQ)
>>
>> Respectfully disagree.  That's how it's traditionally been done because
>> we've had no better way.  Again, ARQ can manage the server lifecycle in
>> Embedded and Managed modes.  And "real testing" is subjective; I can do
>> all sorts of amazing things in these modes (like used shared memory to
>> test concurrency and pass-by-reference) that are impossible in other
>> ways.  Not to mention that it's dead simple to run.
>
> by "real testing" I mean you are running against the "real" thing and not some stripped down server/deployment.

ARQ does not strip anything down.  It's a plumbing layer only; it 
bridges the JUnit/TestNG lifecycle and plugs it into server lifecycle, 
adding in things like deployment and injection along the way.  ARQ 
enables testing as "real" as the target container adaptor you choose.

> And unless i'm completely misunderstanding you then the start/stop of a server via ARQ is still doing the "lifecycle" of a junit/integration test run.

Yes.  You mention later in this Thread that by "real" you mean "manual 
verification".  ARQ automates by either starting or connecting to a 
server as part of the test lifecycle.

> Just because ARQ provides this does not mean the "live"/"real" running on the server goes away ?

Huh?  If you use the Remote connector, then ARQ will disconnect from the 
server you have running.  In Embedded or Managed, it shuts down the 
server it started.

>> The most isolated run mode is Remote, which yes, most closely reflects a
>> production environment.  I like to encourage the notion of using
>> whatever run level is appropriate, and also use many layers of testing.
>
> Yes, but unless ARQ has some serious magic going on it is still not as fast as the IDE to do incremental deployments
> and there is other tooling setup/configuration that is hard/requires a lot of work of  the very userclasses dependent ARQ approach.

ARQ's not doing incremental deployments.  Again, the entry point is the 
JUnit/TestNG harness.

Course, when you have a server as fast as AS7, the time to boot a new 
server instance is IMO negligible.  And incremental deployment, however 
useful during development, is not "real" by any stretch of the 
imagination. :)

S,
ALR

>
> /max
>
>>
>> S,
>> ALR
>>
>>>
>>> /max
>>>
>>>>
>>>> S,
>>>> ALR
>>>>
>>>>>
>>>>>
>>>>> /max
>>>>>
>>>>>>
>>>>>> S,
>>>>>> ALR
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> /max
>>>>>>>
>>>>>>>>
>>>>>>>> Stuart
>>>>>>>>
>>>>>>>> On 22/03/2011, at 6:37 AM, Anil Saldhana wrote:
>>>>>>>>
>>>>>>>>> You might wonder why I cannot start AS7 in JPDA mode and debug in Eclipse.
>>>>>>>>> The issue is Arquilian tries to start the container again and I see
>>>>>>>>> "Address in use" exceptions in the
>>>>>>>>> log.  This is even after I have used
>>>>>>>>> =======
>>>>>>>>> @RunWith(Arquillian.class)
>>>>>>>>> @Run(RunModeType.AS_CLIENT)
>>>>>>>>> =======
>>>>>>>>> annotations.
>>>>>>>>>
>>>>>>>>> So I am not sure if Arquilian can check whether AS7 is already running.
>>>>>>>>> If yes, don't try to start the containers.
>>>>>>>>>
>>>>>>>>> On 03/21/2011 12:56 PM, Anil Saldhana wrote:
>>>>>>>>>> Hi all,
>>>>>>>>>>    I have a test case that constructs a web archive using arquilian and
>>>>>>>>>> then deploys on AS7.
>>>>>>>>>>
>>>>>>>>>> But I am not seeing any way to use JPDA on AS7 via the JUnit test
>>>>>>>>>> because Arquilian is starting the container. Neither the standalone.conf
>>>>>>>>>> JPDA settings nor the vm arguments set in eclipse allow me to trace
>>>>>>>>>> through AS7 code.
>>>>>>>>>>
>>>>>>>>>> Anybody else faced this?
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Anil
>>>>>>>>> _______________________________________________
>>>>>>>>> jboss-as7-dev mailing list
>>>>>>>>> jboss-as7-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> jboss-as7-dev mailing list
>>>>>>>> jboss-as7-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>>>
>>>>>>> /max
>>>>>>> http://about.me/maxandersen
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jboss-as7-dev mailing list
>>>>>>> jboss-as7-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>> jboss-as7-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>>
>>>>>
>>>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> /max
> http://about.me/maxandersen
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev



More information about the jboss-as7-dev mailing list