Hi, I have a simple bridging route defined as
The toBean has a WS-Policy attached that demands a UsernameToken. As per the CXF documentation I try to set the username and password on the toBean like this: However, it seems those properties are simply discarded, and the CXF Policy Interceptor complains: "No username available." That also seems to be true for arbitrary properties. If I set the properties on the toBean instead, they do seem to be applied there (which isn't helping in this case, but anyway). Is there a reason why unknown properties are swallowed on the consumer side? Is there a way to avoid that? Thanks, Jens -- View this message in context: http://camel.465427.n5.nabble.com/Setting-properties-on-Camel-CXF-consumer-endpoints-tp5719195.html Sent from the Camel - Users mailing list archive at Nabble.com.
