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 annoatations), 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 Borker
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.
Antonio
On Mon, Jul 30, 2012 at 3:30 PM, Nigel Deakin <nigel.deakin_at_oracle.com>wrote:
> On 30/07/2012 14:23, Antonio Goncalves wrote:
>
>> Hi all,
>>
>> Back from holidays and catching up with emails.
>>
>> 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
>
>
>
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org> |
Twitter<http://twitter.com/agoncal>|
LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org> |
Devoxx France <http://www.devoxx.fr>