cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache CXF Documentation > 2.5 Migration Guide
Date Mon, 24 Oct 2011 20:52:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2042/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.5
Migration Guide</a></h2>
    <h4>Page <b>edited</b> by             <a href="">Daniel
                         <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" > ** cxf:stop-endpoint busid endpointName
<br> ** cxf:start-endpoint busid endpointName <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">
* New WS-Notification Service and API&#39;s <br> * New Security Token Service <br></td></tr>
            <tr><td class="diff-unchanged" > <br>h3. Removed modules <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h3><a name="2.5MigrationGuide-NewFeatures"></a>New Features</h3>
	<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>
	<li>&lt;cxf:workqueue&gt; configuration to configure the workqueues that CXF
	<li>Karaf commands
		<li>cxf:list-endpoints <a href="/confluence/pages/createpage.action?spaceKey=CXF20DOC&amp;title=busid&amp;linkCreation=true&amp;fromPageId=27821383"
		<li>cxf:stop-endpoint busid endpointName</li>
		<li>cxf:start-endpoint busid endpointName</li>
	<li>New WS-Notification Service and API's</li>
	<li>New Security Token Service</li>

<h3><a name="2.5MigrationGuide-Removedmodules"></a>Removed modules</h3>
	<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>

<h3><a name="2.5MigrationGuide-APIChanges"></a>API Changes</h3>
	<li>The AlternativeSelector.selectAlternative method for selecting the Policy alternative
to use now requires a new List&lt;List&lt;Assertion&gt;&gt; parameter which,
on the server side, is the list of Alternatives that the incoming request matched.  The AlternativeSelector
can use that to aid in selecting the best response alternative to use.</li>
	<li>The PolicyEngine.getEffectiveServerResponsePolicy now takes an additional parameter
of the incoming policy alternatives that were matched.   It can be null for the previous behavior.</li>

<h3><a name="2.5MigrationGuide-RuntimeChanges"></a>Runtime Changes</h3>
	<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="" class="external-link" rel="nofollow"></a>
	<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>

<h3><a name="2.5MigrationGuide-PropertyChanges"></a>Property Changes</h3>
        <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