RMI registry needs to be created inside PaxRunnerTestContainer instead of being
created inside container-rbc's Activator
------------------------------------------------------------------------------------------------------------------------
Key: PAXEXAM-191
URL: http://issues.ops4j.org/browse/PAXEXAM-191
Project: Pax Exam
Issue Type: Improvement
Components: Default Test Container
Reporter: Bartosz Kowalewski
Assignee: Bartosz Kowalewski
Right know choosing port for RMI and creating RMI registry works like this:
1. The process that launches the test creates a server socket to check if a
port is free. This is done using FreePort.
2. The Activator creates RMI registry.
3. The process that launches the test looks the registry up.
Proposed this approch:
1. The process that launches the test creates a registry on a free port.
2. The Activator looks the registry up.
This JIRA issue is dedicated to tracking this given enhancement separately.
However, this a fix for this issue will also fix PAXEXAM-174 and probably cause
status of PAXEXAM-181 to be changed to 'won't fix'.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
