https://issues.apache.org/jira/browse/SMX4NMR-239
--
View this message in context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3300369.html
Sent from the Camel - Users mailing list archive at Nabble.com.
e message before entering the NMR.
>
> I was wondering what is it used for ?
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3293713.html
> Sent from the Camel - Users mailing list archive at Na
I also remarked that using the NMR adds another entry in the exchange header
: NMRMessage which holds a copy of the message before entering the NMR.
I was wondering what is it used for ?
--
View this message in context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is
I am using Apache ServiceMix 4.2.0. It is the version bundled with Fuse 4.3.
The version of the NMR is Apache ServiceMix NMR 1.2.0
HTH
--
View this message in context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3291204.html
Sent from the Camel - Users
Oh, which version of servicemix are you using?
It looks like camel-nmr component doesn't deal will the Authentiacation
token rightly.
On 12/3/10 11:36 AM, Olivier.Roger wrote:
The CamelAuthentication header appears when message is passing through the
NMR
Here is the route:
-CamelAuthentication-is-null-tp3290948p3291160.html
Sent from the Camel - Users mailing list archive at Nabble.com.
t; http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3290979.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
B
context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3290979.html
Sent from the Camel - Users mailing list archive at Nabble.com.
containing
> object: null with key: CamelAuthentication cannot be serialized, it will be
> excluded by the holder.
>
> Is this normal that CamelAuthentication is present but null in the exchange
> headers ?
> --
> View this message in context:
> http://camel.4654
: CamelAuthentication cannot be serialized, it will be
excluded by the holder.
Is this normal that CamelAuthentication is present but null in the exchange
headers ?
--
View this message in context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3290948.html
Sent from
10 matches
Mail list logo