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.5 Migration Guide
Date Fri, 23 Sep 2011 08:58: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.5+Migration+Guide">2.5
Migration Guide</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~ay">Aki
Yoshida</a>
    </h4>
        <br/>
                         <h4>Changes (3)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-unchanged" >h3. New Features <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">
* WS-RM is being updated to support 1.1 <br> * WS-RM components are fully JMX instrumented
<br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">
* WS-RM is being updated to support 1.1. Also included are some feature improvements such
as sequence demarcation by WS-RM client. <br> * WS-RM components are fully JMX instrumented.
Various status information about the WS-RM processing such as sequences, retries, acknowledgments
can be monitored over JMX. <br></td></tr>
            <tr><td class="diff-unchanged" > * WS-MetadataExchange support for
server side.  CXF services will now respond properly to WS-MEX requests. <br> <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" > * The default bus ID used for the
Bus MBean servers when running in OSGi now contains the bundle context SymbolicName to make
identifying the appropriate Bus easier. <br> * Many calls that can result in Security
checks are now wrapped via AccessControll.doPrivileged calls which can allow finer grained
control of the permissions that CXF requires.   See https://issues.apache.org/jira/browse/CXF-2683
. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">
* An empty partial response message will be returned as an HTTP 202 response with no content
instead of an HTTP 200 with an empty SOAP body message. <br></td></tr>
            <tr><td class="diff-unchanged" > <br> <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h3><a name="2.5MigrationGuide-NewFeatures"></a>New Features</h3>
<ul>
	<li>WS-RM is being updated to support 1.1. Also included are some feature improvements
such as sequence demarcation by WS-RM client.</li>
	<li>WS-RM components are fully JMX instrumented. Various status information about the
WS-RM processing such as sequences, retries, acknowledgments can be monitored over JMX.</li>
	<li>WS-MetadataExchange support for server side.  CXF services will now respond properly
to WS-MEX requests.</li>
</ul>


<h3><a name="2.5MigrationGuide-Removedmodules"></a>Removed modules</h3>
<ul>
	<li>All the JBI related modules have been removed from CXF.  If using CXF with JBI,
it's recommended to use the ServiceMix CXF JBI components.  Any code that those modules needed
from past versions of CXF will be moved into those ServiceMix components.</li>
</ul>



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



<h3><a name="2.5MigrationGuide-RuntimeChanges"></a>Runtime Changes</h3>
<ul>
	<li>If a MBeanServer is available in the Spring context or as an OSGi server (when
running in OSGi), the InstrumentationManger will be automatically enabled and will use that
MBeanServer and the CXF MBeans will be registered.</li>
	<li>The default bus ID used for the Bus MBean servers when running in OSGi now contains
the bundle context SymbolicName to make identifying the appropriate Bus easier.</li>
	<li>Many calls that can result in Security checks are now wrapped via AccessControll.doPrivileged
calls which can allow finer grained control of the permissions that CXF requires.   See <a
href="https://issues.apache.org/jira/browse/CXF-2683" class="external-link" rel="nofollow">https://issues.apache.org/jira/browse/CXF-2683</a>
.</li>
	<li>An empty partial response message will be returned as an HTTP 202 response with
no content instead of an HTTP 200 with an empty SOAP body message.</li>
</ul>



<h3><a name="2.5MigrationGuide-PropertyChanges"></a>Property Changes</h3>
    </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.5+Migration+Guide">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=27821383&revisedVersion=6&originalVersion=5">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/CXF20DOC/2.5+Migration+Guide?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message