Page History

...

Code Block
nmr:endpointName

URI Options

Div

class	confluenceTableSmall

Option	Default Value	Description
`runAsSubject`	`false`	Apache ServiceMix

Wiki Markup

{div:class=confluenceTableSmall} || Option || Default Value || Description || | {{runAsSubject}} | {{false}} | *Apache ServiceMix

4.4:

*

When

this

is

set

to

{{{*}

true

{*}}}

on

a

consumer

endpoint,

the

endpoint

will

be

invoked

on

behalf

of

the

{{

Subject

}}

that

is

set

on

the

{{

Exchange

}}

(i.e.

the

call

to

{{

Subject.getSubject(AccessControlContext)

}}

will

return

the

{{

Subject

}}

instance)

| | {{synchronous}} | {{false}} | When this is set to {{{*}true{*}}} on a consumer endpoint, an incoming, synchronous NMR Exchange will be handled on the sender's thread instead of being handled on a new thread of the NMR endpoint's thread pool | | {{timeout}} | {{0}} | *Apache ServiceMix 4.4:* When this is set to a value greater than 0, the producer endpoint will timeout if it doesn't receive a response from the NMR within the given timeout period (in milliseconds). Configuring a timeout value will switch to using synchronous interactions with the NMR instead of the usual asynchronous messaging. | | {{throwExceptionOnFailure}} | true | *Apache ServiceMix 4.5.2:* When this is set to {{{*}false{*}}} then NMR's exceptions (like TimeoutException) will be consumed silently. | | {{interfaceName}} | null | *Apache ServiceMix 4.5.3:* When specify this as a {{{*}QName{*}}} then it could be considered when NMR looking for the target NMR endpoint during dispatch| | {{serviceName}} | null | *Apache ServiceMix 4.5.3:* When specify this as a {{{*}QName{*}}} then it could be considered when NMR looking for the target NMR endpoint during dispatch| {div}


`synchronous`	`false`	When this is set to `true` on a consumer endpoint, an incoming, synchronous NMR Exchange will be handled on the sender's thread instead of being handled on a new thread of the NMR endpoint's thread pool
`timeout`	`0`	Apache ServiceMix 4.4: When this is set to a value greater than 0, the producer endpoint will timeout if it doesn't receive a response from the NMR within the given timeout period (in milliseconds). Configuring a timeout value will switch to using synchronous interactions with the NMR instead of the usual asynchronous messaging.
`throwExceptionOnFailure`	true	Apache ServiceMix 4.5.2: When this is set to `false` then NMR's exceptions (like TimeoutException) will be consumed silently.
`interfaceName`	null	Apache ServiceMix 4.5.3: When specify this as a `QName` then it could be considered when NMR looking for the target NMR endpoint during dispatch
`serviceName`	null	Apache ServiceMix 4.5.3: When specify this as a `QName` then it could be considered when NMR looking for the target NMR endpoint during dispatch

Examples

Consumer

Code Block

from("nmr:MyServiceEndpoint") // consume nmr exchanges asynchronously
from("nmr:MyServiceEndpoint?synchronous=true").to() // consume nmr exchanges synchronously and use the same thread as defined by NMR ThreadPool

...

Child pages

Versions Compared

Old Version 14

New Version Current

Key

URI Options

Examples