Author: buildbot
Date: Wed Apr 1 08:57:05 2015
New Revision: 945920
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/cache/main.pageCache
websites/production/cxf/content/docs/31-migration-guide.html
websites/production/cxf/content/docs/a-simple-jax-ws-service.html
websites/production/cxf/content/setting-up-eclipse.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/cache/main.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 Wed Apr 1
08:57:05 2015
@@ -107,7 +107,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.   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.   This allows
resources to be cleaned up and garbage collected sooner.  However, it also
prevents multiple calls to create() from sharing the same
ServerInfo/EndpointInfo/etc... objects like they would we 3.0.x.   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.  If you
require spring/spring-dm, you will need to install those features prior to
installing the CXF
feature.</li><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></ul><p> </p><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.  This makes the code nonportable
to other JAX-WS containers.   The primary use would be to add
AutoCloseable to the interface to allow use of the clients in Java7 try with
resource blocks.</li></ul><p> </p><h3
id="id-3.1MigrationGuide-MajorDependencyChanges">Major Dependency
Changes</h3><ul><li>The Jetty based HTTP transport has been updated to support
Jetty 9 as well as Jetty 8.   However, support for Jetty 7 has been
dropped.</li><li>Due to the Jetty upgrade, support for running Jetty based
endpoints in Karaf 2.3.x has been dropped.</li><li>Support for usin
g JAX-WS 2.1 based API jars has been removed.  Java 7 (now required)
includes JAX-WS 2.2 so this should not be an issue.</li></ul></div>
+<div id="ConfluenceContent"><h3 id="id-3.1MigrationGuide-MajorNotes">Major
Notes</h3><ul><li>CXF 3.1 no longer supports Java 6.   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.   This allows
resources to be cleaned up and garbage collected sooner.  However, it also
prevents multiple calls to create() from sharing the same
ServerInfo/EndpointInfo/etc... objects like they would we 3.0.x.   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.  If you
require spring/spring-dm, you will need to install those features prior to
installing the CXF
feature.</li><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></ul><p> </p><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.  This makes the code nonportable
to other JAX-WS containers.   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.   Codahale/DropWizard based collector included.</li><li>New
Throttling feature for easily throttling CXF services.  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></u
l><p> </p><h3 id="id-3.1MigrationGuide-MajorDependencyChanges">Major
Dependency Changes</h3><ul><li>The Jetty based HTTP transport has been updated
to support Jetty 9 as well as Jetty 8.   However, support for Jetty 7 has
been dropped.</li><li>Due to the Jetty upgrade, support for running Jetty based
endpoints in Karaf 2.3.x has been dropped.</li><li>Support for using JAX-WS 2.1
based API jars has been removed.  Java 7 (now required) includes JAX-WS
2.2 so this should not be an issue.</li></ul></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/cxf/content/docs/a-simple-jax-ws-service.html
==============================================================================
--- websites/production/cxf/content/docs/a-simple-jax-ws-service.html (original)
+++ websites/production/cxf/content/docs/a-simple-jax-ws-service.html Wed Apr
1 08:57:05 2015
@@ -121,11 +121,11 @@ Apache CXF -- A simple JAX-WS service
<div id="ConfluenceContent"><p>This example will lead you through creating
your first service with doing "code first" development with JAX-WS.</p>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1419015888831 {padding: 0px;}
-div.rbtoc1419015888831 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1419015888831 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1427878593533 {padding: 0px;}
+div.rbtoc1427878593533 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1427878593533 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1419015888831">
+/*]]>*/</style><div class="toc-macro rbtoc1427878593533">
<ul class="toc-indentation"><li><a shape="rect"
href="#AsimpleJAX-WSservice-Settingupyourbuild">Setting up your
build</a></li><li><a shape="rect"
href="#AsimpleJAX-WSservice-WritingyourService">Writing your
Service</a></li><li><a shape="rect"
href="#AsimpleJAX-WSservice-Publishingyourservice">Publishing your
service</a></li><li><a shape="rect"
href="#AsimpleJAX-WSservice-Accessingyourservice">Accessing your
service</a></li></ul>
</div>
Modified: websites/production/cxf/content/setting-up-eclipse.html
==============================================================================
--- websites/production/cxf/content/setting-up-eclipse.html (original)
+++ websites/production/cxf/content/setting-up-eclipse.html Wed Apr 1 08:57:05
2015
@@ -108,83 +108,29 @@ Apache CXF -- Setting up Eclipse
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><p>Setting up an <a shape="rect"
class="external-link" href="http://www.eclipse.org/downloads/";
rel="nofollow">Eclipse</a> project to build CXF is pretty easy. There are
three parts to it:</p>
-
-<h3 id="SettingupEclipse-Requiredplugins">Required plugins</h3>
-<p>We use several Eclipse plugins to make building CXF a bit easier</p>
-<ul><li>Checkstyle - we use checkstyle to make sure we have consistent code
style as well as to find various types of bugs and other issues. <a
shape="rect" class="external-link"
href="http://eclipse-cs.sourceforge.net/update";
rel="nofollow">http://eclipse-cs.sourceforge.net/update</a></li><li>PMD - like
Checkstyle, we use PMD to find potential programming problems in the code.
Point the Eclipse auto-install thing at <a shape="rect" class="external-link"
href="http://pmd.sourceforge.net/eclipse";
rel="nofollow">http://pmd.sourceforge.net/eclipse</a></li><li>Subversion
plugins - there are a couple of these to enable Subversion checkins/checkouts
from within eclipse: <a shape="rect" class="external-link"
href="http://subclipse.tigris.org/update_1.4.x";
rel="nofollow">http://subclipse.tigris.org/update_1.4.x</a></li></ul>
-
-
-<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p> <img class="emoticon emoticon-information"
src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/information.png";
data-emoticon-name="information" alt="(info)"> While there exist Maven
plug-ins for Eclipse, team developer experience has found using them with CXF
<a shape="rect" class="external-link"
href="http://cxf.547215.n5.nabble.com/Using-the-Eclipse-Maven-plugin-for-CXF-tp575175p575176.html";
rel="nofollow">problematic</a> at best. We recommend importing the CXF source
code as Eclipse projects as shown below and/or using Maven externally (i.e.,
from a command-line window) as discussed on the <a shape="rect"
href="building.html">CXF build</a> page.</p>
-</div></div>
-
-<h4 id="SettingupEclipse-Toinstalltheplugins:">To install the plugins:</h4>
-<ul><li>Go to
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+<div id="ConfluenceContent"><p>Setting up an <a shape="rect"
class="external-link" href="http://www.eclipse.org/downloads/";
rel="nofollow">Eclipse</a> project to build CXF is pretty easy. There are three
parts to it:</p><h3 id="SettingupEclipse-Requiredplugins">Required
plugins</h3><p>We use several Eclipse plugins to make building CXF a bit
easier</p><ul><li>Checkstyle - we use checkstyle to make sure we have
consistent code style as well as to find various types of bugs and other
issues. <a shape="rect" class="external-link"
href="http://eclipse-cs.sourceforge.net/update";
rel="nofollow">http://eclipse-cs.sourceforge.net/update</a></li><li>PMD - like
Checkstyle, we use PMD to find potential programming problems in the code.
Point the Eclipse auto-install thing at <a shape="rect" class="external-link"
href="http://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/";
rel="nofollow">http://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/</a></li><li>Subversion
plugi
ns - there are a couple of these to enable Subversion checkins/checkouts from
within eclipse: <a shape="rect" class="external-link"
href="http://subclipse.tigris.org/update_1.4.x";
rel="nofollow">http://subclipse.tigris.org/update_1.4.x</a></li></ul><p> </p><div
class="panel" style="border-width: 1px;"><div class="panelContent">
+<p><img class="emoticon emoticon-information"
src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/information.png";
data-emoticon-name="information" alt="(info)"> While there exist Maven
plug-ins for Eclipse, team developer experience has found using them with CXF
<a shape="rect" class="external-link"
href="http://cxf.547215.n5.nabble.com/Using-the-Eclipse-Maven-plugin-for-CXF-tp575175p575176.html";
rel="nofollow">problematic</a> at best. We recommend importing the CXF source
code as Eclipse projects as shown below and/or using Maven externally (i.e.,
from a command-line window) as discussed on the <a shape="rect"
href="building.html">CXF build</a> page.</p>
+</div></div><h4 id="SettingupEclipse-Toinstalltheplugins:">To install the
plugins:</h4><ul><li><p>Go to</p><div class="preformatted panel"
style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>Help -> Install New Software -> Install
</pre>
-</div></div></li></ul>
-
-
-<ul><li>Click "Available Software Sites" and add the three remote sites listed
above. Select just those three.</li><li>Back on the Install window, select
"Work With: -<span style="text-decoration: line-through;">All Available
Sites</span>-, and choose the three plugins listed above.</li><li>Return to
"Available Software Sites" and reactivate the other remote sites (for
subsequent updates/installs).</li></ul>
-
-
-<p>Eclipse will then download and install those plugins.</p>
-
-<h3 id="SettingupEclipse-ExperimentalAlternative:M2Eclipse">Experimental
Alternative: M2Eclipse</h3>
-
-<p>Some of us are starting to experiment with using M2Eclipse. See <a
shape="rect" href="cxf-m2eclipse.html">this page</a> for instructions.</p>
-
-<h3 id="SettingupEclipse-Creatingaworkspace">Creating a workspace</h3>
-<p>First <a shape="rect"
href="http://cxf.apache.org/source-repository.html";>check out CXF</a> from
Subversion.</p>
-
-<p>To create a workspace, just run from the root directory of the CXF project
(see the <a shape="rect" href="http://cxf.apache.org/building.html";>build
page</a> for more detailed information):</p>
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+</div></div></li></ul><ul><li>Click "Available Software Sites" and add the
three remote sites listed above. Select just those three.</li><li>Back on the
Install window, select "Work With: -<span style="text-decoration:
line-through;">All Available Sites</span>-, and choose the three plugins listed
above.</li><li>Return to "Available Software Sites" and reactivate the other
remote sites (for subsequent updates/installs).</li></ul><p>Eclipse will then
download and install those plugins.</p><h3
id="SettingupEclipse-ExperimentalAlternative:M2Eclipse">Experimental
Alternative: M2Eclipse</h3><p>Some of us are starting to experiment with using
M2Eclipse. See <a shape="rect" href="cxf-m2eclipse.html">this page</a> for
instructions.</p><h3 id="SettingupEclipse-Creatingaworkspace">Creating a
workspace</h3><p>First <a shape="rect"
href="http://cxf.apache.org/source-repository.html";>check out CXF</a> from
Subversion.</p><p>To create a workspace, just run from the root directory of
the CXF proje
ct (see the <a shape="rect" href="http://cxf.apache.org/building.html";>build
page</a> for more detailed information):</p><div class="preformatted panel"
style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>> mvn -Pfastinstall
> mvn -Psetup.eclipse
</pre>
-</div></div>
-<p><strong>OR</strong></p>
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+</div></div><p><strong>OR</strong></p><div class="preformatted panel"
style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>> mvn install -Pfastinstall -Psetup.eclipse
</pre>
-</div></div>
-<p>This creates a new workspace in "../workspace" for use with CXF. </p>
-
-<p>If you don't want the workspace there, you can run: </p>
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+</div></div><p>This creates a new workspace in "../workspace" for use with
CXF.</p><p>If you don't want the workspace there, you can run:</p><div
class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
<pre>"mvn -Psetup.eclipse -Declipse.workspace.dir=path/to/workspace"
</pre>
-</div></div>
-
-<p>If you don't want the eclipse projects' output directory to be ./target
directory (by default) but ./eclipse-classes, you can run:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+</div></div><p>If you don't want the eclipse projects' output directory to be
./target directory (by default) but ./eclipse-classes, you can run:</p><div
class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
<pre>"mvn -Psetup.eclipse -Pset.eclipse.output"
</pre>
-</div></div>
-
-<p>What this does is create a workspace and imports our checkstyle rules, the
maven 2 repository, code format rules, import order rules, etc... into that
workspace. It also goes through each sub-project and creates the .project and
.classpath files. This process will take some time. It will down load source
jars for most of the dependencies and hook them up in the .classpath file as
well. Thus, while coding/debugging, you can trace right into the dependent
libraries. While running, you <strong><em>WILL</em></strong> see a bunch of
warnings and such flying by. There are a bunch of jars on ibiblio that do NOT
have source jars with them. Thus, you will see warning about those. Those
warnings are safely ignorable. As long as it says "BUILD SUCCESSFUL" at the
end, you should be OK.</p>
-
-<h3 id="SettingupEclipse-CreatetheprojectinEclipse">Create the project in
Eclipse</h3>
-<ul><li>In eclipse, switch to the workspace you created above.</li><li>Go To:
-<div class="preformatted panel" style="border-width: 1px;"><div
class="preformattedContent panelContent">
+</div></div><p>What this does is create a workspace and imports our checkstyle
rules, the maven 2 repository, code format rules, import order rules, etc...
into that workspace. It also goes through each sub-project and creates the
.project and .classpath files. This process will take some time. It will down
load source jars for most of the dependencies and hook them up in the
.classpath file as well. Thus, while coding/debugging, you can trace right into
the dependent libraries. While running, you <strong><em>WILL</em></strong> see
a bunch of warnings and such flying by. There are a bunch of jars on ibiblio
that do NOT have source jars with them. Thus, you will see warning about those.
Those warnings are safely ignorable. As long as it says "BUILD SUCCESSFUL" at
the end, you should be OK.</p><h3
id="SettingupEclipse-CreatetheprojectinEclipse">Create the project in
Eclipse</h3><ul><li>In eclipse, switch to the workspace you created
above.</li><li><p>Go To:</p><div class="preformatted
panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>File -> Import....
</pre>
-</div></div></li><li>Select "Existing Projects into Workspace" and hit
Next</li><li>Select root directory: enter the path to your trunk directory and
hit Next.</li><li>Select all the subprojects and hit Finish. Eclipse will
import and rebuild all the subprojects selected. This will take a
while.</li></ul>
-
-
-<p>That's all there is to it. From eclipse, all the unit tests and system
tests should be runnable. However, to build kits/jars and stuff, you still
need to use the command line "mvn" stuff.</p>
-
-
-<h4
id="SettingupEclipse-ImportingnewprojectsthatdependonCXFprojects">Importing new
projects that depend on CXF projects</h4>
-<p>With the latest version (2.5) of the maven-eclipse-plugin, when you run
"mvn eclipse:eclipse" on a project, if it knows where your workspace is, it
will see what projects are already defined and wire them in to the new project
instead of pointing at the jars in your ~/.m2/repository dir. Thus, debugging
is a lot easier. There are two ways to get it to know where your workspace
is:</p>
-
-<ol><li>Explicitly on the command line. When running eclipse:eclipse, add
-Declipse.workspace=/home/dkulp/working/workspace</li><li>Update your Maven
~/.m2/settings.xml to have a active profile that always sets these variables.
Thus, whenever the eclipse plugin looks for it, it know where the workspace is.
In settings.xml, do:
-<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[
-...
+</div></div></li><li>Select "Existing Projects into Workspace" and hit
Next</li><li>Select root directory: enter the path to your trunk directory and
hit Next.</li><li>Select all the subprojects and hit Finish. Eclipse will
import and rebuild all the subprojects selected. This will take a
while.</li></ul><p>That's all there is to it. From eclipse, all the unit tests
and system tests should be runnable. However, to build kits/jars and stuff, you
still need to use the command line "mvn" stuff.</p><h4
id="SettingupEclipse-ImportingnewprojectsthatdependonCXFprojects">Importing new
projects that depend on CXF projects</h4><p>With the latest version (2.5) of
the maven-eclipse-plugin, when you run "mvn eclipse:eclipse" on a project, if
it knows where your workspace is, it will see what projects are already defined
and wire them in to the new project instead of pointing at the jars in your
~/.m2/repository dir. Thus, debugging is a lot easier. There are two ways to
get it to know where your
workspace is:</p><ol><li>Explicitly on the command line. When running
eclipse:eclipse, add
-Declipse.workspace=/home/dkulp/working/workspace</li><li><p>Update your Maven
~/.m2/settings.xml to have a active profile that always sets these variables.
Thus, whenever the eclipse plugin looks for it, it know where the workspace is.
In settings.xml, do:</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[...
<activeProfiles>
<activeProfile>extra</activeProfile>
</activeProfiles>
@@ -200,16 +146,7 @@ Apache CXF -- Setting up Eclipse
</profiles>
...
]]></script>
-</div></div>
-By doing that, you can pretty much run eclipse:eclipse (or -Psetup.eclipse for
cxf projects) at any point and it will always wire the new project to depend on
the existing projects.</li></ol>
-
-
-<h3 id="SettingupEclipse-HowDoesThisAllWork,Anyway?">How Does This All Work,
Anyway?</h3>
-<p>If you are wondering about how all this manages to make Eclipse, Maven,
Checkstyle, and PMD <br clear="none">
-cooperate, see <a shape="rect"
href="connecting-maven-eclipse-checkstyle-and-pmd.html">Connecting Maven,
Eclipse, Checkstyle, and PMD</a>.</p>
-
-
-</div>
+</div></div><p>By doing that, you can pretty much run eclipse:eclipse (or
-Psetup.eclipse for cxf projects) at any point and it will always wire the new
project to depend on the existing projects.</p></li></ol><h3
id="SettingupEclipse-HowDoesThisAllWork,Anyway?">How Does This All Work,
Anyway?</h3><p>If you are wondering about how all this manages to make Eclipse,
Maven, Checkstyle, and PMD <br clear="none"> cooperate, see <a shape="rect"
href="connecting-maven-eclipse-checkstyle-and-pmd.html">Connecting Maven,
Eclipse, Checkstyle, and PMD</a>.</p></div>
</div>
<!-- Content -->
</td>
![https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/information.png"](https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/information.png"){kind=link}