activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3363) create archetype to help folks get started with ActiveMQ messaging using camel + spring
Date Sat, 02 Nov 2013 22:05:17 GMT


Claus Ibsen resolved AMQ-3363.

    Resolution: Won't Fix

We have archetypes with Camel and ActiveMQ etc.

> create archetype to help folks get started with ActiveMQ messaging using camel + spring
> ---------------------------------------------------------------------------------------
>                 Key: AMQ-3363
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>            Reporter: james strachan
> Folks often get quite lost hacking pure JMS code; its hard. Even using the Spring JMSTemplate
/ MessageListenerContainer can be tricky.
> It might be nice to create a little archtype which has a spring XML inside it and some
sample beans for consuming messages & processing/transforming them using Camel's annotations
@Producer / @Consumer so there's no middleware APIs at all - just nice simple POJO stuff.
> So am thinking something simple like...
> * a producer bean using @Producer that producers some messages (maybe on startup or something)
> * a consumer bean with @Consumer that does something with the messages
> Spring XML with...
> * an embedded broker (thats easy to zap/comment out)
> * an ActiveMQ camel component bean with the brokerURL defined (so folks can see there's
1 simple property to define to move the broker somewhere else)
> * a simple camel route to show how easy it is to mix and match camel routes and the beans
> In general thinking we could have a real simpel archetype that can get folks started
with AMQ without having to worry too much about the JMS API; and also help get them started
on Camel too.
> I guess the app could even extend camel-web and generate a WAR then folks would get a
little UI for browsing their queue etc. e.g. like...

This message was sent by Atlassian JIRA

View raw message