cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache CXF Documentation > 2.3 Migration Guide
Date Fri, 30 Jul 2010 01:47:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/1810/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.3
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" >** @FastInfoset to turn on FastInfoset
support <br>** @Logging to turn on and control various Logging functionality <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">**
@EndpointProperty to configure endpoint properties <br></td></tr>
            <tr><td class="diff-unchanged" >* SOAP/JMS spec implementation <br>*
SDO databinding <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
</div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h2><a name="2.3MigrationGuide-Newfeatures"></a>New features</h2>
	<li>New annotations of java first use cases
		<li>@WSDLDocumentation annotation to add documentation nodes to generated wsdl</li>
		<li>@SchemaValidation annotation to turn on schema validation</li>
		<li>@DataBinding to set the databinding used (if other than JAXB)</li>
		<li>@GZIP to turn on GZIP compression</li>
		<li>@FastInfoset to turn on FastInfoset support</li>
		<li>@Logging to turn on and control various Logging functionality</li>
		<li>@EndpointProperty to configure endpoint properties</li>
	<li>SOAP/JMS spec implementation</li>
	<li>SDO databinding</li>

<h2><a name="2.3MigrationGuide-APIchanges"></a>API changes</h2>
	<li>As part of cleaning up the API's and use of generics in the API's, the InterceptorProvider
API changed it's methods from:
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
List&lt;Interceptor&gt; getOutInterceptors();
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
List&lt;Interceptor&lt;? <span class="code-keyword">extends</span> Message&gt;&gt;
<p>While binary compatible (type erasure makes the raw signatures the same), it's not
SOURCE compatible as you may need to update the types of variables used to hold the lists.
 Generally, just do the same change.   Add <tt>&lt;? extends Message&gt;</tt>
to the declaration of the Interceptor.</p></li>

<h2><a name="2.3MigrationGuide-Runtimechanges"></a>Runtime changes</h2>
	<li>In 2.2.x and earlier, mustUnderstand=true headers were sent into the endpoint (in
the List&lt;Header&gt;) and only checked after the endpoint is done processing.  If
the endpoint doesn't process them, only afterword is the mustUnderstand fault raised.   With
2.3.x, mustUnderstand=true headers are checked prior to dispatch.   If an endpoint requires
mustUnderstand headers to be passed in, it must be configured so the runtime knows to allow
them through.  To do so, add a endpoint property named "endpoint-processes-headers" that is
either a string of the qname of the header to pass in or a collection of string of qnames
of headers to pass in.   (We'll be adding an annotation or other means to configure this shortly)</li>

	<li>SOAP/JMS - CXF now support the <a href=""
class="external-link" rel="nofollow">w3c SOAP/JMS spec</a>.  Existing SOAP/JMS stuff
should continue working, but users are encouraged to start using the standard configurations.</li>

	<li>Provider&lt;Source&gt; and Dispatch&lt;Source&gt; - when specifying
a generic "Source" type, CXF now provides a streaming SAXSource object.   Previously, CXF
would load the whole message into a DOM and provide a DOMSource.  Applications that expect
a DOMSource will need to be updated to accept the SAXSource or provide configuration to force
to DOMSource.   There is now a configuration property for the Endpoint of "source-preferred-format"
which can be set to:
		<li>"dom" -&gt; DOMSource</li>
		<li>"sax" -&gt; SAXSource  (cxf StaxSource)</li>
		<li>"stream" -&gt; StreamSource</li>
		<li>"cxf.stax" -&gt;  StaxSource</li>
		<li>"stax" -&gt; javax.xml.transform.stax.StAXSource if avail, StaxSource otherwise</li>

		<li>The set of root classes is now of type Set&lt;java.lang.reflect.Type&gt;
to permit generics.</li>
		<li>The class Type is renamed to AegisType to reduce confusion and conflict with java.lang.reflect.Type.</li>

<h2><a name="2.3MigrationGuide-Configchanges"></a>Config changes</h2>
        <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