Hi Prasad
What I meant was to put a breakpoint in Message.getContextProperties -
these are the properties relevant to a given invocation and they have
the properties from the endpoint specific bus accumulated.
So start from:
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=rt/ws/security/src/main/java/org/apache/cxf/ws/security/wss4j/WSS4JUtils.java;h=0e891e605b6bce2bb1bcd547aa86a3d62ec422d4;hb=HEAD#l81
This is where the property is checked. The Message property cache has
already been prepared by then, so you can start earlier and put a
breakpoint in:
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=core/src/main/java/org/apache/cxf/message/MessageImpl.java;h=b08b0c5f9dd525fa954f6b5d47c5c2863c1e3427;hb=HEAD#l174
There you will see the bus properties being added to the current cache.
If a given bus has no the expected properties then as I suggested you'd
need to isolate the problem by starting from the simplest case where the
properties are available and then proceeding to incrementally updating
the configuration (as per your case) until it breaks - this will help to
figure out where the problem actually is
HTH
Sergey
On 19/02/15 16:42, psd wrote:
Hi Sergey,
Following your instructions, it really proving really difficult for me to
setup things with non-local transport..
could you please be able to let me know where did you see bus properties are
being checked?
I can see that Exchange properties are being copied in
ChainInitiationObserver.setExchangeProperties() method... but I couldn't
find same for Bus.. in fact the default bus ?
Thanks,
psd
--
View this message in context:
http://cxf.547215.n5.nabble.com/Properties-defined-on-Bus-are-not-available-on-Endpoints-tp5754469p5754484.html
Sent from the cxf-user mailing list archive at Nabble.com.
