You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by bu...@apache.org on 2013/08/09 18:48:17 UTC

svn commit: r873754 - in /websites/production/cxf/content: cache/docs.pageCache docs/30-migration-guide.html

Author: buildbot
Date: Fri Aug  9 16:48:17 2013
New Revision: 873754

Log:
Production update by buildbot for cxf

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

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

Modified: websites/production/cxf/content/docs/30-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/30-migration-guide.html (original)
+++ websites/production/cxf/content/docs/30-migration-guide.html Fri Aug  9 16:48:17 2013
@@ -182,6 +182,9 @@ Apache CXF -- 3.0 Migration Guide
 
 
 <ul><li>Many of our interfaces/classes that held onto constants were either removed or moved.  In particular XmlSchemaConstants was removed (use the Constants from the XmlSchema library directly), WSDLConstants was moved from api to rt-wsdl, SOAPConstants was removed (most are available in WSDLConstants).  Goal is to reduce some memory usage and help startup time and reduce a lot of duplication.</li></ul>
+
+
+<ul><li>The direct dependency on a javax.mail implementation has been removed and the CXF maven poms will not pull one in transitively anymore. For MOST users, this is not a problem.  However, if your application uses MTOM or Soap w/Attachments or similar that requires some of the DataContentHandlers that are part of the mail implementations, you may need to re-add this to your classpath.</li></ul>
 </div>
            </div>
            <!-- Content -->