On 30/07/2012 14:23, Antonio Goncalves wrote:
>
>
> I haven't followed the JMS 2.0 specification, so sorry if this topic has been discussed.
>
> Since EJB 3.0 and its EJBContainer API, life for integration test has been made easy (and even easier with tools
> such as
> Arquillian). I've contacted several time the Servlet 3.1 EG to have such API (a WebContainer API to start, stop,
> deploy... servlets will help for testing) and was wondering if an embedded JMSContainer API was on the roadmap ?
> Today
> integration testing with JMS/MDB is impossible in a standard way but possible with proprietary tools.
> EJBContainer is
> not intended to work with MDBs so I was wondering if the JMS EG had something in mind in terms of embedded JMS
> containers.
>
> Thanks
> Antonio
>
>
> What features would an "embedded JMS container" offer?
>
> Nigel
>
On 30/07/2012 14:56, Antonio Goncalves wrote:
> It will offer a standard API to start/stop a JMS Broker. You can then, in an integration test, start a JMS Broker
> programmatically, define a Destination and Factory (using the new @JMSDestination annotations), send a message to
> this destination, received a message, check that the received message is ok, integration test is green, and then we
> close the JMS Broker programmatically at the end of the test. Like the EJBContainer, this will just be an API and
> the implementation would just be a jar file in your classpath.
>
Thanks. Apart from the the ability to start and stop the JMS server, and the ability to define Java EE resources using
@JMSConnectionFactoryDefinition and @JMSDestinationDefinition annotations (if that's what you were referring to), what
other Java EE features would such a container offer? @Resource annotations? A transaction manager? Session beans? MDBs?
Connection pooling? CDI?
Nigel