servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache ServiceMix > servicemix-cxfbc 2009.02
Date Sat, 19 Dec 2009 13:42:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=SM&amp;forWysiwyg=true"
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">servicemix-cxfbc
    <h4>Page  <b>added</b> by             <a href="">Gert
    <div class="notificationGreySide">
         <h3><a name="servicemix-cxfbc2009.02-Releasenotesservicemixcxfbc2009.02"></a>Release
notes - servicemix-cxf-bc-2009.02</h3>

<h4><a name="servicemix-cxfbc2009.02-Bug"></a>Bug</h4>
	<li><a href="" rel="nofollow">SMXCOMP-28</a>
- in-out cxf-bc async jms consumer with cxf-se provider loses messages under load with no
errors reported</li>
	<li><a href="" rel="nofollow">SMXCOMP-32</a>
- CXF-SE client proxies should support MTOM/attachments</li>
	<li><a href="" rel="nofollow">SMXCOMP-487</a>
- cxf bc provider lost faultstring and faultcode for incoming soap fault message from externel
	<li><a href="" rel="nofollow">SMXCOMP-493</a>
- STFlow doesn&apos;t work with servicemix-http/servicemix-cxf-bc</li>
	<li><a href="" rel="nofollow">SMXCOMP-500</a>
- ensure the cxf consumer&apos;s classloader is used for its interceptor chain</li>
	<li><a href="" rel="nofollow">SMXCOMP-504</a>
- ConcurrentModificationExceptions under heavy load in CXF BC</li>
	<li><a href="" rel="nofollow">SMXCOMP-509</a>
- cxfse:endpoint service and endpoint attributes do not influence nmr endpoint as expected</li>
	<li><a href="" rel="nofollow">SMXCOMP-511</a>
- cxf bc provider should close InputStream of response message</li>
	<li><a href="" rel="nofollow">SMXCOMP-536</a>
- potential memory leak for cxf continuation</li>
	<li><a href="" rel="nofollow">SMXCOMP-540</a>
- Registration/deregistration problem for consumer endpoint</li>
	<li><a href="" rel="nofollow">SMXCOMP-543</a>
- potentail cxf bc  tests hang with jms broker</li>
	<li><a href="" rel="nofollow">SMXCOMP-547</a>
- CXF-BC Component unable to use web services with parameter named &quot;Body&quot;
when useJBIWrapper=false</li>
	<li><a href="" rel="nofollow">SMXCOMP-555</a>
- Not correctly processed org.apache.axis2.AxisFault when using servicemix-cxf-bc as a web
service proxy, causes java.lang.NullPointerException in JbiInWsdl1Interceptor class</li>
	<li><a href="" rel="nofollow">SMXCOMP-557</a>
- cxf bc should honor implicitly used soap header</li>
	<li><a href="" rel="nofollow">SMXCOMP-573</a>
- cxf bc component shouldn&apos;t rely on the default bus</li>
	<li><a href="" rel="nofollow">SMXCOMP-584</a>
- when shutdown cxf bc consumer endpoint,  shouldn&apos;t  shutdown the cxf bc component&apos;s
	<li><a href="" rel="nofollow">SMXCOMP-585</a>
- cxf bc provider can&apos;t handle soap fault message correctly when there&apos;s
whitespace/tab/return in the fault details</li>
	<li><a href="" rel="nofollow">SMXCOMP-589</a>
- cxf bc provider shouldn&apos;t try to set fault message back to InOnly MessageExchange</li>
	<li><a href="" rel="nofollow">SMXCOMP-590</a>
- The is failing on IBM machines</li>
	<li><a href="" rel="nofollow">SMXCOMP-600</a>
- namespace will miss after changing from soap message to jbi message on mac osx</li>
	<li><a href="" rel="nofollow">SMXCOMP-607</a>
- Persistence-id of the component can&apos;t contain the minus char</li>
	<li><a href="" rel="nofollow">SMXCOMP-617</a>
- CXF-BCProvider and JbiOutWsdl1Interceptor generate classcast exception in case where JBI
messageExchange have newline characters in xml (formatted xml).</li>
	<li><a href="" rel="nofollow">SMXCOMP-618</a>
- should use StaxUtils.writeElement/Node with repairing "true" instead of add namespace explicitly</li>
	<li><a href="" rel="nofollow">SMXCOMP-628</a>
- ensure getBus() of CxfBcComponent not return null</li>
	<li><a href="" rel="nofollow">SMXCOMP-632</a>
- cxf bc consumer should support the case that there&apos;s soap header in the out Message</li>
	<li><a href="" rel="nofollow">SMXCOMP-633</a>
- check if the NormalizedMessage is fault in org.apache.servicemix.cxfse.interceptors.AttachmentInInterceptor</li>
	<li><a href="" rel="nofollow">SMXCOMP-636</a>
- Upgrade components to use Jencks 2.2</li>
	<li><a href="" rel="nofollow">SMXCOMP-671</a>
- should defer start org.apache.cxf.endpoint.Server to cxf bc consumer start method</li>
	<li><a href="" rel="nofollow">SMXCOMP-681</a>
- add xml-resolver dependency explicitly to ensure org/apache/xml/resolver/CatalogManager
is available</li>

<h4><a name="servicemix-cxfbc2009.02-Improvement"></a>Improvement</h4>
	<li><a href="" rel="nofollow">SMX4KNL-243</a>
- Start using <a href="" rel="nofollow"></a>
for Apache snapshots</li>
	<li><a href="" rel="nofollow">SMXCOMP-490</a>
- ensure cxf bc and se endpoint check exchange status at very first place</li>
	<li><a href="" rel="nofollow">SMXCOMP-548</a>
- when smx-cxf-bc use MTOM message over JMS transport, need specify jms message type as byte
to use real binary way to transfer the attachment</li>
	<li><a href="" rel="nofollow">SMXCOMP-549</a>
- add decoupled endpoint support for cxf bc provider</li>
	<li><a href="" rel="nofollow">SMXCOMP-550</a>
- cxf se should be able to extract operationName based on payload and servicemodel if using
doc/literal style in case that no operationName bound to the MessageExchange</li>
	<li><a href="" rel="nofollow">SMXCOMP-571</a>
- should put CxfBcProvider instance into cxf exchange for potentially later use</li>
	<li><a href="" rel="nofollow">SMXCOMP-574</a>
- CXF-BC and CXF-SE should allow separate configuration for non-default busCfg at component
	<li><a href="" rel="nofollow">SMXCOMP-591</a>
- cxf bc provider should be able to send exception back when something wrong during process
soap fault message</li>
	<li><a href="" rel="nofollow">SMXCOMP-649</a>
- CXF-BC raises a NullPointerException if the targetEndpoint is not found (without WSDL provided)</li>

<h4><a name="servicemix-cxfbc2009.02-NewFeature"></a>New Feature</h4>
	<li><a href="" rel="nofollow">SMXCOMP-482</a>
- Upgrade to CXF 2.2</li>
	<li><a href="" rel="nofollow">SMXCOMP-572</a>
- JbiJAASInterceptor should also support WS-Security X.509 Certificate Token Profile</li>
	<li><a href="" rel="nofollow">SMXCOMP-616</a>
- add schemaValidationEnabled flag for cxf bc endpoint</li>

<h4><a name="servicemix-cxfbc2009.02-Task"></a>Task</h4>
	<li><a href="" rel="nofollow">SM-1877</a>
- update wss4j to 1.5.8</li>
	<li><a href="" rel="nofollow">SM-1911</a>
- Upgrade Derby to</li>
	<li><a href="" rel="nofollow">SMX4-296</a>
- upgrade to cxf 2.2.2</li>
	<li><a href="" rel="nofollow">SMXCOMP-542</a>
- remove AbstractBindingFactory.DATABINDING_DISABLED dependency when build interceptor chain</li>
	<li><a href="" rel="nofollow">SMXCOMP-554</a>
- refactor tests to not use port 9000 so that the tests can pass with sonar plugin</li>
	<li><a href="" rel="nofollow">SMXCOMP-575</a>
- Intermittent failure in CxfBcRMSequenceTest.testInactivityTimeout()</li>
	<li><a href="" rel="nofollow">SMXCOMP-596</a>
- CxfBCPolicyTest intermittently failed on some box</li>
	<li><a href="" rel="nofollow">SMXCOMP-668</a>
- upgrade activemq version used in servicemix-cxf-bc tests to 5.3.0</li>

<h4><a name="servicemix-cxfbc2009.02-Test"></a>Test</h4>
	<li><a href="" rel="nofollow">SMXCOMP-498</a>
- several test failed caused by recent change in cxf</li>
	<li><a href="" rel="nofollow">SMXCOMP-533</a>
- Improve test coverage - ServiceMix :: CXF Binding Component</li>
	<li><a href="" rel="nofollow">SMXCOMP-535</a>
- Refactor CxfBcProviderTest</li>
	<li><a href="" rel="nofollow">SMXCOMP-539</a>
- add test to verify the PIC of cxf bc su will always use its own classloader even use same
jetty port with other SU</li>
	<li><a href="" rel="nofollow">SMXCOMP-551</a>
- update the expired certificate which are used for the security tests</li>
	<li><a href="" rel="nofollow">SMXCOMP-597</a>
- CxfBCSESystemTest failed due to recent change in cxf</li>
	<li><a href="" rel="nofollow">SMXCOMP-609</a>
- CxfBcProviderConsumerTest fails with an IBM JDK</li>
	<li><a href="" rel="nofollow">SMXCOMP-613</a>
- CxfBCConsumerAsynTest intermittently failed on some machine</li>
	<li><a href="" rel="nofollow">SMXCOMP-630</a>
- CxfBcAddressingTest.testExplicitMAPs failed caused by recent change in cxf</li>
	<li><a href="" rel="nofollow">SMXCOMP-669</a>
- add test to verify exception in code first way can be handled correctly by cxf bc/se</li>
	<li><a href="" rel="nofollow">SMXCOMP-676</a>
- CxfBcRMSequenceTest.testInactivityTimeout failed intermittently especially on some slow
windows machine</li>

    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message