CXF 2.5.1 testing results

SAM feature

Currently SAM feature exported as interface “org.talend.esb.sam.agent.feature.EventFeature”.
Expected interface for CXF is “org.apache.cxf.feature.Feature”.
OOTB SAM doesn't enabled by default. Possible workarounds:

  1. Export feature as interface “org.apache.cxf.feature.Feature”. Inside container works fine; don't work in standalone mode.
  2. Ask CXF to check interface like Class.isAssignableFrom

Service Locator feature

Currently ServiceLocator feature is exported as interface “org.talend.esb.servicelocator.cxf.LocatorFeature”.
Expected interface for CXF is “org.apache.cxf.feature.Feature”.
ServiceLocator feature is not enabled by default.
Workarounds for SAM feature are also correct for ServiceLocator feature.

Bundles starting order

The order of bundles the same, but in container with cxf 2.5.1 we have 3 additional bundles:

[ 157] [Active     ] [            ] [       ] [   50] Apache ServiceMix :: Specs :: Activation API 1.4 (1.8.0)
[ 158] [Active     ] [            ] [       ] [   50] Apache ServiceMix :: Specs :: JAXB API 2.2 (1.8.0)
[ 159] [Active     ] [            ] [       ] [   50] Apache ServiceMix :: Specs :: Stax API 1.0 (1.8.0)

Registering Locator feature on CXF bus level

Tested with modified RAC: Locator feature enabled on bus level for client and service. Works as expected.

InstanceAlreadyExistsException exception after data service redeploy

Fixed.

Transport type JMS is not filled correctly in message events for JMS based requests

Fixed.

 
cxf-2.5.1-testing-results.txt · Last modified: 2012/01/05 00:28 by alexander
 
 
Recent changes RSS feed Driven by DokuWiki