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

[Max Rydahl Andersen]

>> 
>>>> That is what I meant, but since the configs would be the same but simply just an offset specified when starting up
>>>> it becomes the same does it not ?
>>>> 
>>>> Anyway, I'm curious how you guys workaround this problem when using arquillian - I keep having to remember shutting
>>>> down my AS before running anything Arquillian related.
>>>> 
>>>> Maybe that is the only approach?
>>> 
>>> Well, yes.  I always shut down my AS instance before starting another one (whether via ARQ or not).
>> 
>> Yeah, its just that its so easy now to end up in a weird port or runtime conflict that I think many won't notice and believe there is a bug when if they had
>> just been made aware of it somehow the confusion could be avoided.
> 
> Any issues in the forums or similar where users are actually reporting 
> this problem?  And that they can't figure out they've started running 2 
> AS instances in the same port space?

I'll have to dig - the latest one was one Aslak contacted me on based on a forum posting to Arquillian.

>>> Unless you're using the ARQ remote connector to attach to an existing remote process, and you don't want ARQ managing your server lifecycle (only deployment and testing).
>> 
>> ARQ Managing your server lifecycle ? How would that work ? For me ARQ is just about starting/attaching and stopping/detaching when running tests.
> 
> Yes, "starting" and "stopping" is managing the server lifecycle.  It's 
> done in Embedded and Managed modes by ARQ.
> 
>> 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.

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.

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

> 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.

/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