-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thank you again!
Just to be clear, you are saying that the payload of a message through the NMR
does not need to be XML, but it will be encoded and decoded as XML inside the
NMR? I ask because I have successfully sent other kinds of data through the NMR.
It sounds like the NMR is is some ways, a legacy effort.
- ---
A. Soroka
Software & Systems Engineering :: Online Library Environment
the University of Virginia Library
On Apr 16, 2012, at 11:44 AM, Jean-Baptiste Onofré wrote:
> NMR means Normalized Message Router.
>
> It means that, whatever endpoint you use, the message will have the same
> format (XML described).
>
> Due to that, the NMR brings a set of feature (audit, security, etc) but has
> drawbacks ("bad" performance due to XML marshaling/unmarshaling, doesn't fit
> very to some protocol (RS), etc).
>
> As you can have quite the same NMR features using Camel (for example, using
> wire tap, you can have something equivalent to audit), my advice is to use
> directly Camel.
>
> Regards
> JB
>
> On 04/16/2012 05:39 PM, [email protected] wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Thank you-- that is good to know.
>>
>> It does bring me a further question: where does the NMR sit in this space of
>> components? For example, what functionality is the NMR bringing that Camel's
>> VM component does not? Does the NMR integrate in some way with DOSGi? Or is
>> it bounded at the OSGi container? (In which case, it would seem to have a
>> smaller remit than the VM component...) I assume that the NMR is intended to
>> do more than support the JBI container...?
>>
>> - ---
>> A. Soroka
>> Software& Systems Engineering :: Online Library Environment
>> the University of Virginia Library
>>
>> On Apr 16, 2012, at 11:01 AM, Jean-Baptiste Onofré wrote:
>>
>>> Hi,
>>>
>>> you can use in an OSGi environment. The vm endpoint from one bundle is
>>> visible to the routes in others bundles (I use it a lot).
>>>
>>> Regards
>>> JB
>>>
>>> On 04/16/2012 04:41 PM, [email protected] wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> I've been wondering about the VM component myself-- as I understand it
>>>> (and I may be wrong) it relies on classloader visibility for VM endpoints
>>>> to be visible to other components. Would there be any issues of conflict
>>>> with the OSGi classloader system there? For example, would VM endpoints in
>>>> one bundle be visible to other bundles?
>>>>
>>>> - ---
>>>> A. Soroka
>>>> Software& Systems Engineering :: Online Library Environment
>>>> the University of Virginia Library
>>>>
>>>> On Apr 13, 2012, at 11:07 AM, Christian Schneider wrote:
>>>>
>>>>> Btw. there is also the vm: component which allows you to communicate
>>>>> between bundles... and of course there always is jms :-)
>>>>> In fact I always use camel directly in Karaf and have not faced bigger
>>>>> issues where I would have missed the NMR.
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> Am 13.04.2012 16:42, schrieb [email protected]:
>>>>>> I found this to be surprisingly difficult. I was motivated by a raft of
>>>>>> improvements in Camel 2.9.x, especially better Blueprint support, but I
>>>>>> ran
>>>>>> into lots of package import-export problems and this:
>>>>>>
>>>>>> http://fusesource.com/issues/browse/MR-434
>>>>>>
>>>>>> so eventually, I switched to using Camel in Karaf without ServiceMix.
>>>>>> Luckily, our integration problem was simple enough that I could switch
>>>>>> from
>>>>>> using the NMR to using Camel's SEDA component. I'd like to switch back
>>>>>> before our integrations get more complex (which they always do {grin}).
>>>>>>
>>>>>> Of course, YMMV.
>>>>>>
>>>>>> ---
>>>>>> A. Soroka
>>>>>> Software and Systems Engineering
>>>>>> the University of Virginia Library
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 13, 2012 at 10:01 AM, James Carman
>>>>>> <[email protected]>wrote:
>>>>>>
>>>>>>> Is it okay to upgrade the existing version of Camel that's bundled
>>>>>>> with ServiceMix? We would like to upgrade to Camel 2.9.x. If so,
>>>>>>> what's the easiest way to do so? Do we just have both versions
>>>>>>> running inside the container?
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Christian Schneider
>>>>> http://www.liquid-reality.de
>>>>>
>>>>> Open Source Architect
>>>>> Talend Application Integration Division http://www.talend.com
>>>>>
>>>>
>>>> -----BEGIN PGP SIGNATURE-----
>>>> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
>>>> Comment: GPGTools - http://gpgtools.org
>>>>
>>>> iQEcBAEBAgAGBQJPjC+yAAoJEATpPYSyaoIkTjIH/1+W7tukGUfaF7LkyV93fgdk
>>>> rVlk+gxHp04bBwivowc85krFErGb6BLfGUEmUdbN3tbfwNx86MZxkPUFGhZJnBRs
>>>> aaHSKePdk4/TsGOAx+yYA4edGRlPofGrKCHfJABXyGYuoHiON+H1L8vxh9ziqDVN
>>>> ti+IyFYxNEQZ4hLiIKyeX8M/F0j4Uu5XXOkVViMrqKXc+8VV8B/Utvc5gG+KKJtU
>>>> GbK/3kMLYg3KZiF1HqBqw+1LR7I1WYpgEcBMenXyHqrMNOKwskxBTEYDZjtMDIb6
>>>> Z/Ad+PN6a735g5G/0O3IwVCsIsEHvnqkNDCbAONNpewzjHD2nK7t7cSQ8oWf/eA=
>>>> =mMck
>>>> -----END PGP SIGNATURE-----
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> [email protected]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
>> Comment: GPGTools - http://gpgtools.org
>>
>> iQEcBAEBAgAGBQJPjD0fAAoJEATpPYSyaoIkIBUH+QF2qK6E+hmwL9PJTZX2X6zz
>> zo5688Ax3PqP8F+vrff5VNeHRXn/jRYOoJ9b99vquihi+XmS+ZvQWdTBTpcvSAuE
>> gMSieVxFKNO3OzWTR0xEvLd0W7N1RsIH6KEeM3A3FPXJSXxJtoWb/XqqRFJ8WoiA
>> e6Si0WCVdMDilHmuoNg5awpCThhxsQYqjVizDiPSDP5KIzeBoZlv6qmdXkKbEj7A
>> 2/5CLZfzjYlY3rCVm2Hmtvquj5EMN1SOwYSzvlEkXWLMotrD3dk7lPPQ/J62cWw+
>> tZtQaQclStQWy5SjqAZ3Jgnqa5FwSGZlmOc/xGTdLdxtqdjqGiaVFoYrAINmgSw=
>> =FkS1
>> -----END PGP SIGNATURE-----
>
> --
> Jean-Baptiste Onofré
> [email protected]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJPjEOUAAoJEATpPYSyaoIkDgoIALOhARGstAa++ezeXvleUTyp
8XeOya63MWwU1UWCd76x9WqyG3scTl7eygBqkkilPRPtysiPdjsmtCt6osHmsif5
rDZoTOzP1IqnEdseeM9eniicS5MRTa137M60s1VB7KbBu20z4lpzvTXdj7FhuhGs
CTHxdg8uX65O5uJzbkop/SeakRr3cevPabCmahdVCYCQw3Pz3uSYu2ZOye3Y8gua
uQ+Cq3DcW2oHTP6bLr60HLWRa7GJ7fzPMmfrSney+iiR6TK0l1BuDogKq08PpbBb
HMJaZYAqP7TJACNCMhQ6SWla1xfE0myuN8p/V7W/FemVelW2mVm/1ApHCno9eyQ=
=xEzC
-----END PGP SIGNATURE-----
