cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache CXF Documentation > 2.4 Migration Guide
Date Mon, 21 Feb 2011 19:10:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2036/9/1/_/styles/combined.css?spaceKey=CXF20DOC&amp;forWysiwyg=true"
<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="">2.4
Migration Guide</a></h2>
    <h4>Page <b>edited</b> by             <a href="">Daniel
                         <h4>Changes (2)</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" >* LogBrowser console <br>* Transformation
feature <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
            <tr><td class="diff-added-lines" style="background-color: #dfd;">*
JIBX databinding <br></td></tr>
            <tr><td class="diff-unchanged" > <br>h3. API Changes <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h3><a name="2.4MigrationGuide-NewFeatures"></a>New Features</h3>

	<li>LogBrowser console</li>
	<li>Transformation feature</li>
	<li>JIBX databinding</li>

<h3><a name="2.4MigrationGuide-APIChanges"></a>API Changes</h3>

	<li>GZIP related interceptors/features have been moved out  of the http module so they
are usable with other transports such as JMS.  As such, their package has changed from org.apache.cxf.transport.http.gzip
to org.apache.cxf.transport.common.gzip</li>

	<li>XmlSchema has been updated from 1.4.x to 2.0.   As such, any use of XmlSchema classes
may have changed.  In particular, XmlSchema 2.0 uses Java 5 collections which changes how
it's used.   Also, many static utility methods that existed in org.apache.cxf.common.xmlschema.XmlSchemaUtils
have now been merged directly into the XmlSchema API's and are no longer needed or available.</li>

	<li>WSS4J has been updated from 1.5.x to 1.6.</li>

<p>See <a href="" class="external-link" rel="nofollow">Colm's
blog</a> for and ongoing list of things that are happening in WSS4J 1.6.   This page
will be updated as that solidifies.</p>

	<li>Neethi has been upgraded from 2.0.x to 3.0.    Due to deficiencies and restrictions
in the Neethi 2.0.x API's, CXF has maintained a semi-fork of various parts of Neethi in the packages.   With CXF 2.4.x and Neethi 3.0, the deficiencies in Neethi
have been addressed and the forked changes have been pushed down into Neethi and CXF can better
leverage enhancements and new functionality in Neethi directly without duplicating functionality.
   If you write custom policies for CXF, some changes will be required.  These include:
		<li>The CXF AssertionBuilder interface has been removed.   We now use the Neethi AssertionBuilders
and Assertions directly.</li>
		<li>The "getPolicy()" method of PolicyAssertion has been removed.  Policies that can
contain nested policies should implement the Neethi PolicyContainingAssertion interface directly.</li>
		<li>Neethi has been updated to be able to process WS-Policy 1.5 policies.  Thus, the
Assertion interface now has a isIgnorable() method that must be implemented.  An implementation
of returning false should be adequate and compatible with previous behavior.</li>
		<li>With the removal of the CXF AssertionBuilder and the implementation if the intersection
algorithm in Neethi, the "buildCompatible" method that was on the CXF AssertionBuilder is
no longer needed.   If a policy needs a custom intersect algorithm, they can now implement
the Neethi IntersectableAssertion interface.</li>
		<li>All locations in CXF that expected the CXF specific PolicyAssertion now expect
a normal Neethi Assertion.   If the Assertion needs specific logic to determine if it's been
asserted, it can implement the CXF PolicyAssertion interface, otherwise the default logic
will be used.</li>
		<li>Since Neethi has been updated to use Java 5 generics, you may need to update and
casts and warnings that may occur when calling the new methods that are now typed.</li>

<h3><a name="2.4MigrationGuide-RuntimeChanges"></a>Runtime Changes</h3>

	<li>The ExtensionManagerBus (mostly used when Spring is not available) has been updated
to completely support all the features including the WS-SecurityPolicy, WS-RM, etc... features.
  Previous WSDL documents that contained policy fragments may now behave differently as the
policies will be enforced.</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="">View
        <a href=";showCommentArea=true#addcomment">Add

View raw message