[
https://issues.apache.org/activemq/browse/CAMEL-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Anstey updated CAMEL-827:
----------------------------------
Attachment: addNewArchetypes.patch
I made a minor change to get rid of the <amq:broker syntax... the embedded AMQ
broker definition now looks like
{code:language=xml}
<broker xmlns="http://activemq.apache.org/schema/core"; useJmx="false"
persistent="false">
<transportConnectors>
<transportConnector uri="tcp://localhost:61616" />
</transportConnectors>
</broker>
{code}
> Add new Camel archetypes
> ------------------------
>
> Key: CAMEL-827
> URL: https://issues.apache.org/activemq/browse/CAMEL-827
> Project: Apache Camel
> Issue Type: New Feature
> Components: tooling
> Reporter: Jonathan Anstey
> Assignee: Hadrian Zbarcea
> Fix For: 1.5.0
>
> Attachments: addNewArchetypes.patch, addNewArchetypes.patch
>
>
> Given that our archetypes will be showing up in m2eclipse after our next
> release, we should really have a few more options that will make it easier
> for someone to start using Camel.
> I propose a Spring XML based archetype which is basically the camel-router
> archetype with the Java DSL transposed to Spring XML. Another archetype shows
> how easy it is to start using Camel with ActiveMQ.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
