Does anyone know how
to cause a custom Transport's setMessageContextImpl() to be called during
processing of a message? I'm thinking that is where the Transport is supposed to
decode the message context's URL, right? setMessageContext() is final so I can't
use that...
Is there any
documentation on custom Transports? I can't find anything that explains this
process...
