You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by dk...@apache.org on 2017/09/13 15:05:57 UTC
svn commit: r1018111 [33/33] - in /websites/production/cxf/content: ./
cache/ docs/
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 Sep 13 15:05:52 2017
@@ -131,7 +131,7 @@ Apache CXF -- Setting up Eclipse
<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><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">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">...
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">...
<activeProfiles>
<activeProfile>extra</activeProfile>
</activeProfiles>
Modified: websites/production/cxf/content/source-repository.html
==============================================================================
--- websites/production/cxf/content/source-repository.html (original)
+++ websites/production/cxf/content/source-repository.html Wed Sep 13 15:05:52 2017
@@ -109,9 +109,9 @@ Apache CXF -- Source Repository
<!-- Content -->
<div class="wiki-content">
<div id="ConfluenceContent"><h2 id="SourceRepository-GitHub">GitHub</h2><p>To browse the sources via GitHub: <a shape="rect" class="external-link" href="https://github.com/apache/cxf" rel="nofollow">https://github.com/apache/cxf</a></p><p>You can fork that repository, commit changes to your fork, and submit pull requests through GitHub's pull request mechanisms.</p><p>The repository is dual-hosted, so it's also valid to use <a shape="rect" class="external-link" href="https://gitbox.apache.org/repos/asf?p=cxf.git">https://gitbox.apache.org/repos/asf?p=cxf.git</a></p><h3 id="SourceRepository-CheckingoutfromGIT">Checking out from GIT</h3><p>The source code can be checked out anonymously over HTTPs by doing:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">git clone https://github.com/apache/cxf.git</pre>
+<pre class="brush: bash; gutter: false; theme: Default" style="font-size:12px;">git clone https://github.com/apache/cxf.git</pre>
</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">git clone https://gitbox.apache.org/repos/asf/cxf.git</pre>
+<pre class="brush: bash; gutter: false; theme: Default" style="font-size:12px;">git clone https://gitbox.apache.org/repos/asf/cxf.git</pre>
</div></div><p> </p><h2 id="SourceRepository-FishEye">FishEye</h2><p>In addition you can use: <a shape="rect" class="external-link" href="https://fisheye.apache.org/browse/cxf">https://fisheye.apache.org/browse/cxf</a></p></div>
</div>
<!-- Content -->
Modified: websites/production/cxf/content/testing-debugging.html
==============================================================================
--- websites/production/cxf/content/testing-debugging.html (original)
+++ websites/production/cxf/content/testing-debugging.html Wed Sep 13 15:05:52 2017
@@ -130,7 +130,7 @@ Apache CXF -- Testing-Debugging
<p>There are generally two ways of running a test in a debugger.</p>
<ol><li>Within the IDE. If you <a shape="rect" href="setting-up-eclipse.html">setup eclipse</a> properly, almost all the tests are runnable directly in eclipse. Right click on the test and select "Run As -> JUnit Test" (or "Debug As"). The test should just run.</li><li>Externally via jpda. This is much harder. By default, mvn will fork the unit tests into a JVM that doesn't have JPDA enabled. However, it can be done. First, set your MAVEN_OPTS like:
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
export JPDA_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n"
export MAVEN_OPTS="-XX:MaxPermSize=192m -Xmx512M $JPDA_OPTS"
</pre>
Modified: websites/production/cxf/content/using-ws-policy-in-cxf-projects.html
==============================================================================
--- websites/production/cxf/content/using-ws-policy-in-cxf-projects.html (original)
+++ websites/production/cxf/content/using-ws-policy-in-cxf-projects.html Wed Sep 13 15:05:52 2017
@@ -122,7 +122,7 @@ Apache CXF -- Using WS-Policy in CXF pro
<h3 id="UsingWS-PolicyinCXFprojects-WSDLPolicyattachment">WSDL Policy attachment</h3>
<p>WS-Policies can be attached and referenced in WSDL elements. <a shape="rect" class="external-link" href="http://www.w3.org/TR/ws-policy-attach/" rel="nofollow">Web Services Policy 1.5 - Attachment </a> standard describes all possible alternatives. WS-Policies can be placed inside WSDL itself or referenced as external documents. CXF will automatically recognize, read and use policies defined or referenced in WSDL. Sample of attached policy is shown below:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
<wsdl:definitions name="HelloWorld" targetNamespace="http://apache.org/hello_world_soap_http"
…
<wsdl:service name="SOAPService">
@@ -143,7 +143,7 @@ Apache CXF -- Using WS-Policy in CXF pro
<p>It is possible to define policies directly in Spring configuration of client and service as jaxws feature. CXF will recognize and use configured WS-Policies:<br clear="none">
Client:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
<jaxws:client id="CRMServiceClient" name="{http://services.talend.org/CRMService}CRMServiceProvider"
xmlns:serviceNamespace="http://services.talend.org/CRMService"
serviceClass="org.talend.services.crmservice.CRMService"
@@ -161,7 +161,7 @@ Client:</p>
<p>Service:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
<jaxws:endpoint id="CRMService"
xmlns:serviceNamespace="http://services.talend.org/CRMService"
serviceName="serviceNamespace:CRMServiceProvider"
@@ -193,7 +193,7 @@ Implementation of <em>build()</em> metho
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
public class AuthorizationInterceptorProvider extends AbstractPolicyInterceptorProvider {
private static final long serialVersionUID = -5248428637449096540L;
private static final AuthorizationInInterceptor IN_AUTHZ_INTERCEPTOR = new AuthorizationInInterceptor();
@@ -215,7 +215,7 @@ public class AuthorizationInterceptorPro
</div></div>
<p>Assertion builder and policy interceptor provider can be registered using CXF bus extension mechanism: just create a file META-INF/cxf/bus-extensions.txt containing the following:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
org.company.AuthorizationInterceptorProvider::true
org.company.AuthorizationAssertionBuilder::true
</pre>
Modified: websites/production/cxf/content/ws-policy-framework.html
==============================================================================
--- websites/production/cxf/content/ws-policy-framework.html (original)
+++ websites/production/cxf/content/ws-policy-framework.html Wed Sep 13 15:05:52 2017
@@ -159,7 +159,7 @@ The transport may be included in this de
<p>The AssertionBuilder API is a concept from Neethi (slightly modified below as):</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
public interface AssertionBuilder {
// build an Assertion object from a given xml element
Assertion build(Element element);
@@ -172,7 +172,7 @@ public interface AssertionBuilder {
<h3 id="WS-PolicyFramework-Assertor">Assertor</h3>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
public interface Assertor {
// return the subset of assertions that this assertor can assert
List<Assertion> assert(List<Assertion> candidates);
@@ -186,7 +186,7 @@ Interceptors like the RM interceptor wou
<p>This is simply an extension of the InterceptorProvder interface:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
public interface AssertionInterceptorProvider extends InterceptorProvider {
}
</pre>
@@ -201,7 +201,7 @@ This API would be used by the PolicyEval
<p>Some of the schema types currently used in configuring the http and jms transports may be used as assertions. One advantage would be these types do not have to extend wsdl:tExtensibilityElement any mor. Instead the content of these elements could be verified by their respective assertion builders. Also, the types can be used much more flexibly as assertions than as extension elements registered for say the wsdl:port element only (as assertions, they can be attached to the port type or the port, the service, and even appear outside of wsdl in PolicyAttachment elements). The preferred (but not mandatory) transition would be from:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
<service name="GreeterService">
<port binding="tns:GreeterSOAPBinding" name="GreeterPort">
<http:address xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" location="http://localhost:9020/SoapContext/GreeterPort"/>
@@ -212,7 +212,7 @@ This API would be used by the PolicyEval
</div></div>
<p>to:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
<service name="GreeterService">
<port binding="tns:GreeterSOAPBinding" name="GreeterPort">
<http:address xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" location="http://localhost:9020/SoapContext/GreeterPort"/>
@@ -225,7 +225,7 @@ This API would be used by the PolicyEval
</div></div>
<p>or:</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">
<definition...>
...
<service name="GreeterService">
Modified: websites/production/cxf/content/xjc-utils.html
==============================================================================
--- websites/production/cxf/content/xjc-utils.html (original)
+++ websites/production/cxf/content/xjc-utils.html Wed Sep 13 15:05:52 2017
@@ -110,7 +110,7 @@ Apache CXF -- XJC Utils
<!-- Content -->
<div class="wiki-content">
<div id="ConfluenceContent"><p>The Apache CXF XJC-Utils subproject provides a bunch of utilities for working with JAXB to generate better or more usable code.</p><p>Currently, it consists of the following modules:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cxf-xjc-plugin.html">cxf-xjc-plugin</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Provides a maven wrapper around the JAXB XJC utility</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cxf-xjc-dv.html">cxf-xjc-dv</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Initialize fields mapped from elements/attributes with their default values</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cxf-xjc-ts.html">cxf-xjc-ts</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Implements the toString() method</p></td></tr
><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cxf-xjc-boolean.html">cxf-xjc-boolean</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Generate getters named getXXX() for Booleans instead of isXXX()</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cxf-xjc-wsdlextension.html">cxf-xjc-wsdlextension</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Adds extensions methods to allow generated beans to be used as WSDL4J extensors</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="cxf-xjc-bug671.html">cxf-xjc-bug671</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Provides a workaround for</p><a shape="rect" class="external-link" href="https://jaxb.dev.java.net/issues/show_bug.cgi?id=671" rel="nofollow">https://jaxb.dev.java.net/issues/show_bug.cgi?id=671</a><p>- Not needed for JAXB >=2.1.12</p></td></tr></tbody></table></div><div c
lass="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>In CXF versions prior to 2.3.0, the xjc plugins were shaded directly into the big cxf bundle jar. In 2.3.0, they were removed from the jar and are placed individually into the lib directory of the distribution. The xjc plugins are only code generation utilities and not used at all at runtime which is why they were pulled out.</p></div></div><p>The source code can be checked out anonymously over HTTP by doing:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">git clone https://git-wip-us.apache.org/repos/asf/cxf-xjc-utils.git
+<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">git clone https://git-wip-us.apache.org/repos/asf/cxf-xjc-utils.git
</pre>
</div></div><p>Building is similar to the <a shape="rect" href="building.html">build</a> instructions for the main CXF project.</p></div>
</div>