[CACTUS-49] Jetty doesn't stop after Cactus test run in Eclipse

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5-beta1
• Fix Version/s: 1.5-rc1
• Component/s: Eclipse Integration
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 22249
• Assignee: Vincent Massol
• Reporter: James Stangler
• Created: 08/Aug/03 21:13
• Updated: 17/Apr/04 15:44
• Resolved: 17/Apr/04 15:44

Description

The class 'org.apache.cactus.extension.jetty.JettyTestSetup' is used to start Jetty when running a
Cactus test in Eclipse. Jetty starts properly but isn't shutdown when the test is completed. This
is a problem if a TestSuite contains two JettyTestSetup tests. In our company we have an
AllTests class in each package which runs all of the tests in the package and subpackages. Hence
we have many cases where a TestSuite runs more than one JettyTestSetup test. The server fails
to start for subsequent JettyTestSetup tests and no further tests are run.

The fix is to make two changes. The first is to make the server a class variable. The lines:

// Create a Jetty Server object and configure a listener
Object server = createServer(baseConfig);

should be

// Create a Jetty Server object and configure a listener
server = createServer(baseConfig);

with 'Object server' declared with the other class variables.

The second change is to stop Jetty in the tearDown method as such:

protected void tearDown() throws Exception {
super.tearDown();
if (server != null)

{ server.getClass().getMethod("stop", null).invoke(server, null); }

}