How about a separate jar that could be used in conjunction with
activemq-broker? In time start moving 'nice to have' things from
activemq-broker into this other jar?
Hadrian
On 03/17/2015 05:57 AM, Dejan Bosanac wrote:
IMHO it should be enough to just put these classes in the new package
(something like org.apache.activemq.broker.dsl) inside the activemq-broker
module.
Regards
--
Dejan Bosanac
----------------------
Red Hat, Inc.
[email protected]
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/
On Tue, Mar 17, 2015 at 12:26 AM, artnaseef <[email protected]> wrote:
That's an interesting use-case, and I see the value there.
Would this be a new, separate artifact or a change to an existing one?
Art
P.S. apologies for confusion on my earlier post - using nabble's "raw"
content did indeed cause the content of the post to get stripped in email
somehow.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-DSLs-tp4693171p4693332.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
