On May 20, 2014, at 2:00 AM, Claus Ibsen wrote:
>
> And if there is an API breaking/change in CXF, we may need to upgrade
> the OSGi ranges for CXF to be [3,4)
This shouldn’t be an issue. At this point, any place where the API’s in CXF
are different, Camel uses a bit of reflection or proxi
Hi Claus,
Thanks for pointing that out, the build error is caused by the
WSPasswordCallback is removed in CXF 3.0.0, we need to do some work as we do in
the integration tests to avoid using WSPasswordCallback directly.
I just committed a quick for the the build error
camel-example-reportincide
Hi
I think the CXF upgrade broke some examples. I get this compile error now
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
(default-compile) on project camel-example-reportincident-wssecurity:
Compilation failure: Compilation failure:
[ERROR]
/Users/
