[
https://issues.apache.org/jira/browse/CAMEL-7908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171381#comment-14171381
]
Aaron Whiteside edited comment on CAMEL-7908 at 10/14/14 7:17 PM:
------------------------------------------------------------------
I'm readying a patch for this, but at the same time I'm finding a few things
that could do with cleaning up (Namely creation of
DefaultTransactionCommitStrategy spread across multiple classes), I'm tempted
to include these cleanups in my patch, would that be acceptable or would you
want a separate patch/issue?
was (Author: aaronjwhiteside):
I'm readying a patch for this, but at the same time I'm finding a few things
that could do with cleaning up (Namely creation of
DefaultTransactionCommitStrategy spread across multiple classes), I'm tempted
to include these cleanup in my patch, would that be acceptable?
> Add a DestinationCreationStrategy to the SJMS component
> -------------------------------------------------------
>
> Key: CAMEL-7908
> URL: https://issues.apache.org/jira/browse/CAMEL-7908
> Project: Camel
> Issue Type: Improvement
> Components: camel-sjms
> Affects Versions: 2.14.0
> Reporter: Aaron Whiteside
> Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Add a DestinationCreationStrategy to the SJMS component
> JMS implementations like HornetQ do not allow dynamic queue/topic creation
> via the pure JMS API's. Extending SJMS with a DestinationCreationStrategy
> would allow one to replace the DefaultDestinationCreationStrategy with a
> provider specific one that in the case of HornetQ dynamically creates the
> queue/topic using the correct management API.
> Implementation note:
> JmsObjectFactory::createMessageProducer would be modified to supply a
> DestinationCreateionStrategy, it would then use this to obtain Destination's.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
