ApplicationComposer is a great way to test a small JAXRS service but how to handle concurrent builds? how to avoid port conflicts since all builds will use the same (default) port?
An easy solution is to “affect” one port by build…but don’t ask me to maintain the range allocation ;).
OpenEJB now provides a nice solution.
As a quick reminder here is how to test a simple webservices (I suppose you have openejb-cxf-rs as test dependency):
@EnableServices("jaxrs")
public class MyTest {
@Rule
public final ApplicationComposerRule app = new ApplicationComposerRule(this);
@Module
@JaxrsProviders(JohnzonProvider.class) // optional
@Classes(cdi = true, value = { MyResource.class, MyService.class })
public WebApp webapp() {
return new WebApp();
}
@Test
public void theTest() throws IOException {
// resource accesible on http://localhost:4204/openejb/[resource path]
}
}
Of course you can provide a @Configuration method and set a random port as value for the property httpejb.port but this is not as “fluent” as it should be. That’s why now you can use @RandomPort feature:
@EnableServices("jaxrs")
public class MyTest {
@RandomPort("httpejbd")
private URL httpEjbdPort; // http://localhost:<port>
// as before
}
@RandomPort takes the service name as parameter (if existing it will set the openejb service port otherwise name is just a key). If you inject twice the same service you’ll get the same port. Finally you can get the port injected if you type the field as an int or the root context using URL type.
Happy testing of your microservices with OpenEJB and TomEE!
