Should I just forget about the JMS northbounder then, and call this
one something like eip-northbounder, camel-northbounder, something
like that?

On Fri, Oct 24, 2014 at 12:12 PM, Matt Brozowski <m...@brozowski.com> wrote:
> You might consider using camel instead. Gives you more flexibility.
>
> Matt
>
> Sent from my iPhone
>
>> On Oct 24, 2014, at 12:36 PM, David Schlenk <david.schl...@spanlink.com> 
>> wrote:
>>
>> I'm interested in implementing the JMS northbounder. Reading through
>> the existing unfinished code, looks like the main piece left to do is
>> the configuration. I also thought I'd make an interface for the
>> various NBI configuration and destination implementations, something
>> like:
>>
>> http://paste.lisp.org/+337Z
>>
>> Then I went to implement JmsDestination, and I'm trying to figure out
>> if it's worth attempting to keep it JMS implementation agnostic? The
>> comments in JmsNorthbounder make me think sending to a local embedded
>> ActiveMQ broker (used by NRTG? anything else?) was the intention, and
>> since ActiveMQ lets you create networks of brokers that'll pass
>> messages to wherever a consumer is, that should work fine for my
>> intended use case. But is that broker's config available for
>> modification by the end user? All I can figure is that it's maybe
>> deployed as an OSGi bundle, which I know very little about (time to
>> learn I guess).
>>
>> Any guidance on the direction I should take would be appreciated.
>> --
>> David Schlenk
>> Manager, Research & Development
>> T: 763.971.2030 | Video/Email: david.schl...@spanlink.com
>> ConvergeOne Collaboration, formerly Spanlink Communications
>> New name, but same great people and Cisco focus. > Learn more
>>
>> PLEASE NOTE: My email address is changing Nov. 1 to dschl...@converge-one.com
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Please read the OpenNMS Mailing List FAQ:
>> http://www.opennms.org/index.php/Mailing_List_FAQ
>>
>> opennms-devel mailing list
>>
>> To *unsubscribe* or change your subscription options, see the bottom of this 
>> page:
>> https://lists.sourceforge.net/lists/listinfo/opennms-devel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of this 
> page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel



-- 
David Schlenk
Manager, Research & Development
T: 763.971.2030 | Video/Email: david.schl...@spanlink.com
ConvergeOne Collaboration, formerly Spanlink Communications
New name, but same great people and Cisco focus. > Learn more

PLEASE NOTE: My email address is changing Nov. 1 to dschl...@converge-one.com

------------------------------------------------------------------------------
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this 
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel

Reply via email to