0004162: Ability to Start Resin from IDE/JUnit Test

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0004162

[Resin]

feature

always

08-04-10 16:11

06-18-12 17:01

Reporter

reza

View Status

public

Assigned To

ferg

Priority

normal

Resolution

no change required

Status

closed

Product Version

4.0.10

Summary

0004162: Ability to Start Resin from IDE/JUnit Test

Description

While using frameworks like HTTPUnit, it would be great to be able to automatically start and shut-down Resin like this:

@RunWith(ResinRunner.class) // Manages the embedded Resin life-cycle and should
// start the web/Servlet tier.
public class AlertServletTest {

  @Test
  public void testGetAlerts() {
    try {
      WebConversation webConversation = new WebConversation();
      webConversation.setHeaderField("Connection", "close");
      WebRequest webRequest = new GetMethodWebRequest(
          "http://localhost:8080/actionbazaar/alerts"); [^]
      webRequest.setParameter("user_id", "1111");
      WebResponse webResponse = webConversation.getResponse(webRequest);
      assertEquals(5, webResponse.getDOM().getElementsByTagName("alert")
                    .getLength());
    } catch (IOException e) {
      e.printStackTrace();
    } catch (SAXException e) {
      e.printStackTrace();
    }
  }
}

Just as in the case of bean container runner/EJB embedded container, the class-path should be scanned to automatically find and deploy web.xml, bean.xml, persistence.xml etc. It should also be possible to specially provide additive/alternative deployment descriptors, including resin.xml.

Additional Information

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
08-04-10 16:11	reza	New Issue
06-18-12 17:01	ferg	Assigned To	=> ferg
06-18-12 17:01	ferg	Status	new => closed
06-18-12 17:01	ferg	Resolution	open => no change required

Mantis 1.0.0rc3[^]

27 total queries executed.
25 unique queries executed.