cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r952719 - in /websites/production/cxf/content: cache/docs.pageCache docs/31-migration-guide.html
Date Tue, 26 May 2015 14:47:03 GMT
Author: buildbot
Date: Tue May 26 14:47:02 2015
New Revision: 952719

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/31-migration-guide.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/31-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/31-migration-guide.html (original)
+++ websites/production/cxf/content/docs/31-migration-guide.html Tue May 26 14:47:02 2015
@@ -116,7 +116,7 @@ Apache CXF -- 3.1 Migration Guide
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h3 id="id-3.1MigrationGuide-MajorNotes">Major Notes</h3><ul><li>CXF
3.1 no longer supports Java 6. &#160; You must use Java 7 or Java 8.</li><li>The
JAX-WS/Simple frontend ServerFactoryBean will automatically call reset at the end of the create()
call. &#160; This allows resources to be cleaned up and garbage collected sooner. &#160;However,
it also prevents multiple calls to create() from sharing the same ServerInfo/EndpointInfo/etc...
objects like they would we 3.0.x. &#160; That sharing has caused many problems in the
past due to sharing of properties (like token caches) that are stored on those objects so
the new behavior is more "correct", but it is different than previous versions so care must
be taken while upgrading.</li><li>The Karaf features.xml file for CXF 3.1 no longer
will install spring or spring-dm when installing the "cxf" feature. &#160;If you require
spring/spring-dm, you will need to install those features prior to installing the CXF 
 feature.</li></ul><h3 id="id-3.1MigrationGuide-Securitychanges">Security
changes</h3><ul><li>The STS (Security Token Service) now issues tokens using
the RSA-SHA256 signature algorithm by default (previously RSA-SHA1), and the SHA-256 digest
algorithm (previously SHA-1).</li><li>Some security configuration tags have been
renamed from "ws-security.*" to "security.*", as they are now shared with (some of) the JAX-RS
stack. The old tags will continue to work as before however without any change. See the <a
shape="rect" href="security-configuration.html">Security Configuration </a>page for
more information.</li><li>The SAML/XACML functionality previously available in
the cxf-rt-security module is now in the cxf-rt-security-saml module.</li><li>If
you are explicitly specifying the SAML version in a SAML CallbackHandler, then this is changed
in CXF 3.1 due to the migration to use OpenSAML 3.1. The version is now set on the SAMLCallback
using a org.apache.wss4j.common.saml.bean.Version cla
 ss. Previously there was a dependency on OpenSAML's SAMLVersion class.</li></ul><h3
id="id-3.1MigrationGuide-NewFeatures">New Features</h3><ul><li>The CXF
JAX-WS code generator has a new option "seiSuper" that can be used to specify additional super
interfaces for the SEI. &#160;This makes the code nonportable to other JAX-WS containers.
&#160; The primary use would be to add AutoCloseable to the interface to allow use of
the clients in Java7 try with resource blocks.</li><li>New Metrics feature for
collecting metrics about a CXF services. &#160; Codahale/DropWizard based collector included.</li><li>New
Throttling feature for easily throttling CXF services. &#160;Sample included that uses
the Metrics component to help make the throttling decisions.</li><li>New Logging
feature for more advanced logging than the logging available in cxf-core</li><li>New
Metadata service for SAML SSO to allow you to publish SAML SSO metadata for your service provider.</li><li><p>The
"cxf" frontend to t
 he JAX-WS code generator (-fe cxf) now generates code that is a bit more "Java7" friendly
as the return type of the getPort(...) calls is a sub-interface of the SEI that also implements
AutoCloseable, BindingProvider, and Client. &#160; Code that used to look like:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<div id="ConfluenceContent"><h3 id="id-3.1MigrationGuide-MajorNotes">Major Notes</h3><ul><li>CXF
3.1 no longer supports Java 6. &#160; You must use Java 7 or Java 8.</li><li>The
JAX-WS/Simple frontend ServerFactoryBean will automatically call reset at the end of the create()
call. &#160; This allows resources to be cleaned up and garbage collected sooner. &#160;However,
it also prevents multiple calls to create() from sharing the same ServerInfo/EndpointInfo/etc...
objects like they would we 3.0.x. &#160; That sharing has caused many problems in the
past due to sharing of properties (like token caches) that are stored on those objects so
the new behavior is more "correct", but it is different than previous versions so care must
be taken while upgrading.</li><li>The Karaf features.xml file for CXF 3.1 no longer
will install spring or spring-dm when installing the "cxf" feature. &#160;If you require
spring/spring-dm, you will need to install those features prior to installing the CXF 
 feature.</li></ul><h3 id="id-3.1MigrationGuide-Securitychanges">Security
changes</h3><ul><li>The STS (Security Token Service) now issues tokens using
the RSA-SHA256 signature algorithm by default (previously RSA-SHA1), and the SHA-256 digest
algorithm (previously SHA-1).</li><li>Some security configuration tags have been
renamed from "ws-security.*" to "security.*", as they are now shared with (some of) the JAX-RS
stack. The old tags will continue to work as before however without any change. See the <a
shape="rect" href="security-configuration.html">Security Configuration </a>page for
more information.</li><li>The SAML/XACML functionality previously available in
the cxf-rt-security module is now in the cxf-rt-security-saml module.</li><li>If
you are explicitly specifying the SAML version in a SAML CallbackHandler, then this is changed
in CXF 3.1 due to the migration to use OpenSAML 3.1. The version is now set on the SAMLCallback
using a org.apache.wss4j.common.saml.bean.Version cla
 ss. Previously there was a dependency on OpenSAML's SAMLVersion class.</li><li>It
is now possible to "plug in" custom WS-SecurityPolicy validators if you wish to change the
default validation logic for a particular policy.</li></ul><h3 id="id-3.1MigrationGuide-NewFeatures">New
Features</h3><ul><li>The CXF JAX-WS code generator has a new option "seiSuper"
that can be used to specify additional super interfaces for the SEI. &#160;This makes
the code nonportable to other JAX-WS containers. &#160; The primary use would be to add
AutoCloseable to the interface to allow use of the clients in Java7 try with resource blocks.</li><li>New
Metrics feature for collecting metrics about a CXF services. &#160; Codahale/DropWizard
based collector included.</li><li>New Throttling feature for easily throttling
CXF services. &#160;Sample included that uses the Metrics component to help make the throttling
decisions.</li><li>New Logging feature for more advanced logging than the logging
available in cx
 f-core</li><li>New Metadata service for SAML SSO to allow you to publish SAML
SSO metadata for your service provider.</li><li><p>The "cxf" frontend to
the JAX-WS code generator (-fe cxf) now generates code that is a bit more "Java7" friendly
as the return type of the getPort(...) calls is a sub-interface of the SEI that also implements
AutoCloseable, BindingProvider, and Client. &#160; Code that used to look like:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[(AddNumbersPortType
port = service.getAddNumbersPort();
 ((BindingProvider)port).getRequestContext()
         .put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, address);



Mime
View raw message