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 > 3.0 Migration Guide
Date Mon, 07 Mar 2011 15:13:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2036/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/3.0+Migration+Guide">3.0
Migration Guide</a></h2>
    <h4>Page  <b>added</b> by             <a href="https://cwiki.apache.org/confluence/display/~dkulp">Daniel
Kulp</a>
    </h4>
         <br/>
    <div class="notificationGreySide">
         
<h2><a name="3.0MigrationGuide-3.0MigrationGuide"></a>3.0 Migration Guide</h2>

<p>Right now, 3.0 is in VERY early planning stages.   This page is mostly collecting
lists of things we are planning on changing.  It is by no means an exhaustive list and it
may completely change depending on what gets done and such.</p>

<ul>
	<li>Combine common-utilities/api/core into just a cxf-kernel or similar.</li>
	<li>Pull the "wsdl" specific stuff from kernel into a webservices base package that
the webservices related things can pull and jaxrs doesn't have to.</li>
</ul>


<ul>
	<li>Resolve all the split package things that prevent the OSGi bundling from working
well.</li>
</ul>


<ul>
	<li>Likely move some of the other Abstract classes and such from kernel.   For example,
we now have a transports-common module.   Move the AbstractDestination and stuff there.</li>
</ul>


<ul>
	<li>Go through all the @Deprecated things and remove them.   Likewise, remove unused
method params (I know there are a couple on the Destination API) and such.</li>
</ul>


<ul>
	<li>POSSIBLY update various API's to pass in the Bus (or other objects) if  needed
instead of holding it as an instance variable.   That would allow singleton instances for
things like the transports and such.   For example, it would be good to register a "FooCXFTransport"
as an OSGi service that we could lookup later.   Right now, we couldn't do that unless you
only used a global bus, which isn't exactly what the purpose of the Bus is.</li>
</ul>


    </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/3.0+Migration+Guide">View
Online</a>
              |
       <a href="https://cwiki.apache.org/confluence/display/CXF20DOC/3.0+Migration+Guide?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
           </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message