Hi
On 19/02/15 12:48, psd wrote:
Sergey Beryozkin wrote
It appears a bus allocated to the endpoint is different to the one where
the properties are set. If yes - you can have the endpoint linked to a
specific bus id
Hi Sergey,
Thanks for quick response, yes, that indeed seems to be the case, bus
allocated to endpoint is different than the one that has properties defined.
However, I thought if I define it with
<cxf:bus>
<cxf:properties>
<entry key="ws-security.enable.nonce.cache" value="false"/>
</cxf:properties>
</cxf:bus>
that should be the default bus & I shouldn't need to define bus on every
endpoint. Am I wrong in assuming?
I think you are right. I'm not sure though why this bus defined in the
context is not set as a default bus.
Can you please do an experiment: Have a single Spring context only,
single cxf:bus in that context and a single endpoint (with a non-local
transport). That should work as expected as far as the visibility of bus
properties are concerned. Then narrow it down to next configuration
where it breaks.
Let us know please what you observe
Thanks, Sergey
--
View this message in context:
http://cxf.547215.n5.nabble.com/Properties-defined-on-Bus-are-not-available-on-Endpoints-tp5754469p5754476.html
Sent from the cxf-user mailing list archive at Nabble.com.
