cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache CXF Documentation > 2.6 Migration Guide
Date Tue, 20 Mar 2012 15:41:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2042/9/1/_/styles/combined.css?spaceKey=CXF20DOC&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/CXF20DOC/2.6+Migration+Guide">2.6
Migration Guide</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~dkulp">Daniel
Kulp</a>
    </h4>
        <br/>
                         <h4>Changes (1)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >h3. Runtime Changes <br>* The
syntax of WS-SecurityPolicy policies is enforced more strictly. Some policies that worked
with CXF &lt; 2.6 will not load in CXF 2.6 as a result. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">*
JMS Transport - when using TextMessage, CXF now leaves the contents as a String and uses java.io.Reader
and java.io.Writer to boost performance.   Previously, CXF would convert the Strings to/from
byte[] requiring use of encoders, increasing memory usage, etc...   However, some interceptors
and functionality in CXF (or user interceptors) may expect or require they InputStream/OutputStreams,
not Reader/Writer.   In those cases, you may need to change to use a BytesMessage.  For example,
the FastInfoset feature and GZIP features expect to work on InputStream/OutputStream and thus
would now work with TextMessage. <br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h3><a name="2.6MigrationGuide-NewFeatures"></a>New Features</h3>

<ul>
	<li>The big OSGi bundle used in the Karaf features.xml has been replaced with the individual
modules which are now all individual bundles.   The big OSGi bundle is still built, but some
features may not be available if that is used instead of the little bundles.</li>
	<li>New ability to configure HTTP Conduits from the OSGi config:admin service</li>
	<li></li>
</ul>




<h3><a name="2.6MigrationGuide-RemovedModules"></a>Removed Modules</h3>
<ul>
	<li>cxf-common-utilites was merged into cxf-api</li>
</ul>



<h3><a name="2.6MigrationGuide-APIChanges"></a>API Changes</h3>
<ul>
	<li>All API's that take or return "generic" classes have been update to properly define
the generic part.  For example, methods like:<br/>
"Class getServiceClass()" have been updated to be "Class&lt;?&gt; getServiceClass()"</li>
	<li>To resolve some of the "split-package" issues between jars, SOME (very few) classes
did have their packages changed.
	<ul>
		<li>org.apache.cxf.jaxb.JAXBUtils   -&gt;   org.apache.cxf.common.jaxb.JAXBUtils
  (and a couple other classes in that jaxb package)</li>
	</ul>
	</li>
</ul>




<h3><a name="2.6MigrationGuide-DependencyChanges"></a>Dependency Changes</h3>
<ul>
	<li>The org.apache.cxf.tools.* classes that were in cxf-api have been moved into cxf-tools-common
or cxf-tools-validator.</li>
	<li>The org.apache.cxf.ws.policy classes that were in cxf-api have been moved into
cxf-rt-ws-policy.</li>
	<li>cxf-common-utilities is no longer available.  All the classes in there were moved
into cxf-api to represent a complete "api".</li>
	<li>Various classes in cxf-rt-core and cxf-rt-ws-addr have been moved up to cxf-api
to resolve split-package issues.   Dependencies on cxf-rt-core would have transitively brought
in cxf-api anyway, so there should be little impact.</li>
	<li>Spring is now an optional component of the http-jetty transports module.</li>
</ul>



<h3><a name="2.6MigrationGuide-RuntimeChanges"></a>Runtime Changes</h3>
<ul>
	<li>The syntax of WS-SecurityPolicy policies is enforced more strictly. Some policies
that worked with CXF &lt; 2.6 will not load in CXF 2.6 as a result.</li>
	<li>JMS Transport - when using TextMessage, CXF now leaves the contents as a String
and uses java.io.Reader and java.io.Writer to boost performance.   Previously, CXF would convert
the Strings to/from byte[] requiring use of encoders, increasing memory usage, etc...   However,
some interceptors and functionality in CXF (or user interceptors) may expect or require they
InputStream/OutputStreams, not Reader/Writer.   In those cases, you may need to change to
use a BytesMessage.  For example, the FastInfoset feature and GZIP features expect to work
on InputStream/OutputStream and thus would now work with TextMessage.</li>
</ul>

    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/CXF20DOC/2.6+Migration+Guide">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=27835345&revisedVersion=7&originalVersion=6">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/CXF20DOC/2.6+Migration+Guide?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message