Hi,
This issue was resolved, tracked by SMX4-1016[1].
Seems we need cut a new release for SMX4.4.
Also, per the discussion[2] today, I fixed the wrong embedded wss4j
lib issue in servicemix-cxf-bc-installer.zip, to pick up it we have
to re-cut components and servicemix3.4 also.
NOTES, this issue only affect SMX3.4(it's ok when use servicemix-cxf-
bc.jar in SMX4.4 as we refer wss4j.jar from cxf features.xml), so I'm
not so sure it's a show stopper, as JBI is kind of deprecated and
we suggest users try with SMX4.x for a long time and almost all our
endeavor focus on SMX4.x, anyway community will make this decision.
[1]https://issues.apache.org/jira/browse/SMX4-1016
[2]http://servicemix.396122.n5.nabble.com/Re-CXF-TLS-configuration-td5073601.html
Best Regards
Freeman
On 2011-12-16, at 下午1:08, Johan Edstrom wrote:
Perfect!
I think that'll take care of most issues, I tested all the cxf
samples + a bunch of blueprint NS handling things.
/je
On Dec 15, 2011, at 10:01 PM, Freeman-2 wrote:
Hi Johan,
Thanks for this info, I was testing apache-servicemix-jbi-4.4.0
kit, that's
why I can't reproduce.
Now I can see this problem with full distro, the problem is that
the war
feature which installed with example-cxf-* cause this problem, we
can add
war to the featuresBoot for full and the regular distro also to fix
it.
Regards
Freeman
--
View this message in context:
http://servicemix.396122.n5.nabble.com/VOTE-Release-ServiceMix-4-4-0-take-2-tp5078716p5079320.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
