Author: buildbot
Date: Wed Jan 23 11:48:08 2013
New Revision: 847641
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/features.html
websites/production/cxf/content/fediz-configuration.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/features.html
==============================================================================
--- websites/production/cxf/content/docs/features.html (original)
+++ websites/production/cxf/content/docs/features.html Wed Jan 23 11:48:08 2013
@@ -121,9 +121,9 @@ Apache CXF -- Features
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><h1><a shape="rect"
name="Features-What%27sFeature"></a>What's Feature</h1>
-<p>A Feature is something that is able to customize a Server, Client, or Bus,
typically adding capabilities. For instance, there may be a LoggingFeature
which configures one of the above to log each of their messages.<br
clear="none">
-By default the initialize methods all delegate to
initializeProvider(InterceptorProvider), If you're simply adding interceptors
to a Server, Client, or Bus, this allows you to add them easily.</p>
+<div id="ConfluenceContent"><h1><a shape="rect"
name="Features-FeaturesinCXF"></a>Features in CXF</h1>
+
+<p>A Feature in CXF is a way of adding capabilities to a Server, Client or
Bus. For example, you could add the ability to log messages for each of these
objects, by configuring them with a LoggingFeature. To implement a Feature, you
must subclass AbstractFeature below. By default the initialize methods all
delegate to initializeProvider(InterceptorProvider), so if you're simply adding
interceptors to a Server, Client, or Bus, this allows you to add them
easily.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@@ -131,22 +131,22 @@ By default the initialize methods all de
<span class="code-keyword">public</span> void initialize(Server server,
Bus bus) {
initializeProvider(server.getEndpoint(), bus);
}
-
+
<span class="code-keyword">public</span> void initialize(Client client,
Bus bus) {
initializeProvider(client, bus);
}
-
+
<span class="code-keyword">public</span> void initialize(Bus bus) {
initializeProvider(bus, bus);
}
-
+
<span class="code-keyword">protected</span> void
initializeProvider(InterceptorProvider provider, Bus bus) {
<span class="code-comment">// you could customized the interceptors in
the provider here
</span> }
/**
* Convenience method to extract a feature by type from an active list.
- *
+ *
* @param features the given feature list
* @param type the feature type required
* @<span class="code-keyword">return</span> the feature of the specified
type <span class="code-keyword">if</span> active
@@ -169,11 +169,13 @@ By default the initialize methods all de
</pre>
</div></div>
-<h1><a shape="rect" name="Features-Writingandconfigurethefeature"></a>Writing
and configure the feature</h1>
-<p>CXF provides several features for configure different capabilities, such as
logging, failover, policies, addressing , reliable messaging. You can go to the
<a shape="rect" href="featureslist.html" title="FeaturesList">FeaturesList</a>
for information.</p>
+<h1><a shape="rect" name="Features-WritingandconfiguretheFeature"></a>Writing
and configure the Feature</h1>
+
+<p>CXF provides several features to configure commonly used capabilities, such
as logging, failover, policies, addressing, reliable messaging. You can go to
the <a shape="rect" href="featureslist.html"
title="FeaturesList">FeaturesList</a> for more information.</p>
-<h2><a shape="rect" name="Features-Writingafeature"></a>Writing a feature</h2>
-<p>It is very easy to write a new feature , your feature just need to extends
the AbstractFeature and implement initializeProvider or write customizing code
for configuring client or server interceptors. Here is an example for
implementing the logging feature.</p>
+<h2><a shape="rect" name="Features-WritingaFeature"></a>Writing a Feature</h2>
+
+<p>It is very easy to write a new feature, your feature just need to extends
the AbstractFeature and implement initializeProvider or write customizing code
for configuring client or server interceptors. Here is an example for
implementing the logging feature.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@@ -181,9 +183,9 @@ By default the initialize methods all de
<span class="code-keyword">private</span> <span
class="code-keyword">static</span> <span class="code-keyword">final</span>
<span class="code-object">int</span> DEFAULT_LIMIT = 100 * 1024;
<span class="code-keyword">private</span> <span
class="code-keyword">static</span> <span class="code-keyword">final</span>
LoggingInInterceptor IN = <span class="code-keyword">new</span>
LoggingInInterceptor(DEFAULT_LIMIT);
<span class="code-keyword">private</span> <span
class="code-keyword">static</span> <span class="code-keyword">final</span>
LoggingOutInterceptor OUT = <span class="code-keyword">new</span>
LoggingOutInterceptor(DEFAULT_LIMIT);
-
+
<span class="code-object">int</span> limit = DEFAULT_LIMIT;
-
+
@Override
<span class="code-keyword">protected</span> void
initializeProvider(InterceptorProvider provider, Bus bus) {
<span class="code-keyword">if</span> (limit == DEFAULT_LIMIT) {
@@ -208,34 +210,35 @@ By default the initialize methods all de
<span class="code-keyword">public</span> void setLimit(<span
class="code-object">int</span> lim) {
limit = lim;
}
-
+
/**
* Retrieve the value set with {@link #setLimit(<span
class="code-object">int</span>)}.
* @<span class="code-keyword">return</span>
*/
<span class="code-keyword">public</span> <span
class="code-object">int</span> getLimit() {
<span class="code-keyword">return</span> limit;
- }
+ }
}
</pre>
</div></div>
-<h2><a shape="rect" name="Features-Addingfeatureprogrammatically"></a>Adding
feature programmatically</h2>
-<p>To add the feature to both server and client, you can use the Feature
annotation on the service class</p>
+<h2><a shape="rect" name="Features-AddingaFeatureprogrammatically"></a>Adding
a Feature programmatically</h2>
+
+<p>To add the feature to both server and client, you can use the Feature
annotation on the service class</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
-
+
@org.apache.cxf.feature.Features (features = <span
class="code-quote">"org.apache.cxf.jaxws.service.AnnotationFeature"</span>)
<span class="code-keyword">public</span> class HelloServiceImpl <span
class="code-keyword">implements</span> HelloService {
<span class="code-keyword">public</span> <span
class="code-object">String</span> sayHi() {
<span class="code-keyword">return</span> <span
class="code-quote">"HI"</span>;
}
- }
-
+ }
+
</pre>
</div></div>
-<p>You can also add the feature to the server by using ServerFactoryBean ,or
the client by using the ClientFactoryBean</p>
+<p>You can also add the feature to the server by using ServerFactoryBean, or
the client by using the ClientFactoryBean</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@@ -255,9 +258,9 @@ clientFactoryBean.setFeatures(<span clas
</pre>
</div></div>
-<h2><a shape="rect"
name="Features-Addingafeaturethroughconfiguration"></a>Adding a feature through
configuration</h2>
-<p>Here are some examples on using configuration files to add features.<br
clear="none">
-You can find more information about the CXF provides features at <a
shape="rect" href="featureslist.html" title="FeaturesList">FeaturesList</a>.</p>
+<h2><a shape="rect"
name="Features-AddingaFeaturethroughconfiguration"></a>Adding a Feature through
configuration</h2>
+
+<p>Here are some examples on using configuration files to add features. You
can find more information about the CXF provides features at <a shape="rect"
href="featureslist.html" title="FeaturesList">FeaturesList</a>.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-xml">
<beans xmlns=<span
class="code-quote">"http://www.springframework.org/schema/beans";</span>
@@ -273,24 +276,24 @@ http://cxf.apache.org/jaxws http://cxf.a
<span class="code-tag"><cxf:features></span>
<span class="code-tag"><cxf:logging/></span>
<span class="code-tag"></cxf:features></span>
- <span class="code-tag"></cxf:bus></span>
+ <span class="code-tag"></cxf:bus></span>
<span class="code-tag"><bean id=<span
class="code-quote">"myfeature"</span> class=<span
class="code-quote">"com.example.Myfeature"</span>/></span>
-
- <span class="code-tag"><span class="code-comment"><!-- adding the
feature to the client --></span></span>
- <jaxws:client id=<span class="code-quote">"client"</span>
- serviceClass=<span
class="code-quote">"org.apache.hello_world_soap_http.Greeter"</span>
- wsdlLocation=<span class="code-quote">"wsdl/hello_world.wsdl"</span>>
- <span class="code-tag"><jaxws:features></span>
- <span class="code-tag"><bean ref=<span
class="code-quote">"myfeature"</span> /></span>
- <span class="code-tag"><jaxws:features></span>
+
+ <span class="code-tag"><span class="code-comment"><!-- adding the
feature to the client --></span></span>
+ <jaxws:client id=<span class="code-quote">"client"</span>
+ serviceClass=<span
class="code-quote">"org.apache.hello_world_soap_http.Greeter"</span>
+ wsdlLocation=<span
class="code-quote">"wsdl/hello_world.wsdl"</span>>
+ <span class="code-tag"><jaxws:features></span>
+ <span class="code-tag"><bean ref=<span
class="code-quote">"myfeature"</span> /></span>
+ <span class="code-tag"><jaxws:features></span>
<span class="code-tag"></jaxws:client></span>
-
+
<span class="code-tag"><span class="code-comment"><!-- adding the
feature to the server --></span></span>
<span class="code-tag"><jaxws:server id=<span
class="code-quote">"server"</span> serviceBean=<span
class="code-quote">"org.apache.hello_world_soap_http.GreetImpl"</span>
address=<span
class="code-quote">"http://localhost:8080/simpleWithAddress";</span>></span>
- <span class="code-tag"><jaxws:features></span>
- <span class="code-tag"><bean class=<span
class="code-quote">"com.example.Myfeature"</span>/></span>
- <span class="code-tag"></jaxws:features></span>
+ <span class="code-tag"><jaxws:features></span>
+ <span class="code-tag"><bean class=<span
class="code-quote">"com.example.Myfeature"</span>/></span>
+ <span class="code-tag"></jaxws:features></span>
<span class="code-tag"></jaxws:server></span>
<span class="code-tag"></beans></span>
Modified: websites/production/cxf/content/fediz-configuration.html
==============================================================================
--- websites/production/cxf/content/fediz-configuration.html (original)
+++ websites/production/cxf/content/fediz-configuration.html Wed Jan 23
11:48:08 2013
@@ -178,7 +178,7 @@ Finally, the audience URI is validated a
<div class="table-wrap">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">XML element </th><th colspan="1" rowspan="1"
class="confluenceTh">Name </th><th colspan="1" rowspan="1"
class="confluenceTh">Use </th><th colspan="1" rowspan="1"
class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> audienceUris </td><td colspan="1" rowspan="1"
class="confluenceTd"> Audience URI </td><td colspan="1" rowspan="1"
class="confluenceTd"> Required </td><td colspan="1" rowspan="1"
class="confluenceTd"> The values of the list of audience URIs are verified
against the element <tt>AudienceRestriction</tt> in the SAML token
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
certificateStores </td><td colspan="1" rowspan="1" class="confluenceTd">
Trusted certificate store </td><td colspan="1" rowspan="1"
class="confluenceTd"> Required </td><td colspan="1" rowspan="1"
class="confluenceTd"> The list of keystores (JKS, PEM) inclu
des at least the certificate of the Certificate Authorities (CA) which signed
the certificate which is used to sign the SAML token.<br clear="none">
If the file location is not fully qualified it needs to be relative to the
Container home directory </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> trustedIssuers </td><td colspan="1" rowspan="1"
class="confluenceTd"> Trusted Issuers </td><td colspan="1" rowspan="1"
class="confluenceTd"> Required </td><td colspan="1" rowspan="1"
class="confluenceTd"> There are two ways to configure a trusted issuer (IDP).
Either you configure the subject name and the CA(s) who signed the certificate
of the IDP (<tt>certificateValidation=ChainTrust</tt>) or you configure the
certificate of the IDP and the CA(s) who signed it
(<tt>certificateValidation=PeerTrust</tt>)</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> maximumClockSkew </td><td colspan="1"
rowspan="1" class="confluenceTd"> Maximum Clock Skew </td><td colspan="1"
rowspan="1" class="confluenceTd"> Optional </td><td colspan="1" rowspan="1"
class="confluenceTd"> Maximum allowable time difference between
the system clocks of the IDP and RP.<br clear="none">
-Default 5 seconds. </td></tr></tbody></table>
+Default 5 seconds. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> tokenReplayCache </td><td colspan="1" rowspan="1"
class="confluenceTd"> Token Replay Cache </td><td colspan="1" rowspan="1"
class="confluenceTd"> Optional </td><td colspan="1" rowspan="1"
class="confluenceTd"> The <a shape="rect" class="external-link"
href="http://svn.apache.org/viewvc/cxf/fediz/trunk/plugins/core/src/main/java/org/apache/cxf/fediz/core/TokenReplayCache.java?view=markup";>TokenReplayCache</a>
implementation to use to cache tokens. The default is an implementation based
on EHCache. </td></tr></tbody></table>
</div>
@@ -191,7 +191,7 @@ Default: URL including the Servlet Conte
The WS-Federation standard defines a list of predefined URIs for wauth <a
shape="rect" class="external-link"
href="http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223174997";
rel="nofollow">here</a>.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> roleURI </td><td colspan="1" rowspan="1"
class="confluenceTd"> Role Claim URI </td><td colspan="1" rowspan="1"
class="confluenceTd"> Optional </td><td colspan="1" rowspan="1"
class="confluenceTd"> NA </td><td colspan="1" rowspan="1" class="confluenceTd">
Defines the attribute name of the SAML token which contains the roles.<br
clear="none">
Required for Role Based Access Control. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> roleDelimiter </td><td colspan="1"
rowspan="1" class="confluenceTd"> Role Value Delimiter </td><td colspan="1"
rowspan="1" class="confluenceTd"> Optional </td><td colspan="1" rowspan="1"
class="confluenceTd"> NA </td><td colspan="1" rowspan="1" class="confluenceTd">
There are different ways to encode multi value attributes in SAML.
<ul><li>Single attribute with multiple values</li><li>Several attributes with
the same name but only one value</li><li>Single attribute with single value.
Roles are delimited by <tt>roleDelimiter</tt></li></ul>
-</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
claimTypesRequested </td><td colspan="1" rowspan="1" class="confluenceTd">
Requested claims </td><td colspan="1" rowspan="1" class="confluenceTd">
Optional </td><td colspan="1" rowspan="1" class="confluenceTd">
ClaimTypesRequested </td><td colspan="1" rowspan="1" class="confluenceTd"> The
claims required by the Relying Party are listed here. Claims can be optional.
If a mandatory claim can't be provided by the IDP the issuance of the token
should fail </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
homeRealm </td><td colspan="1" rowspan="1" class="confluenceTd"> Home Realm
</td><td colspan="1" rowspan="1" class="confluenceTd"> Optional </td><td
colspan="1" rowspan="1" class="confluenceTd"> NA </td><td colspan="1"
rowspan="1" class="confluenceTd"> Indicates the Resource IDP the home realm of
the requestor. This may be an URL or an identifier like urn: or uuid: and
depends on the Resource IDP imple
mentation. This value is part of the SignIn request as the <tt>whr</tt>
parameter </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
tokenValidators </td><td colspan="1" rowspan="1" class="confluenceTd">
TokenValidators </td><td colspan="1" rowspan="1" class="confluenceTd"> Optional
</td><td colspan="1" rowspan="1" class="confluenceTd"> NA </td><td colspan="1"
rowspan="1" class="confluenceTd"> Custom Token validator classes can be
configured here. The SAML Token validator is enabled by default.<br
clear="none">
+</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
claimTypesRequested </td><td colspan="1" rowspan="1" class="confluenceTd">
Requested claims </td><td colspan="1" rowspan="1" class="confluenceTd">
Optional </td><td colspan="1" rowspan="1" class="confluenceTd">
ClaimTypesRequested </td><td colspan="1" rowspan="1" class="confluenceTd"> The
claims required by the Relying Party are listed here. Claims can be optional.
If a mandatory claim can't be provided by the IDP the issuance of the token
should fail </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
homeRealm </td><td colspan="1" rowspan="1" class="confluenceTd"> Home Realm
</td><td colspan="1" rowspan="1" class="confluenceTd"> Optional </td><td
colspan="1" rowspan="1" class="confluenceTd"> NA </td><td colspan="1"
rowspan="1" class="confluenceTd"> Indicates the Resource IDP the home realm of
the requestor. This may be an URL or an identifier like urn: or uuid: and
depends on the Resource IDP imple
mentation. This value is part of the SignIn request as the <tt>whr</tt>
parameter </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
freshness </td><td colspan="1" rowspan="1" class="confluenceTd"> Freshness
</td><td colspan="1" rowspan="1" class="confluenceTd"> Optional </td><td
colspan="1" rowspan="1" class="confluenceTd"> NA </td><td colspan="1"
rowspan="1" class="confluenceTd"> The desired "freshness" of the token from the
IdP. This information is provided in the SignInRequest to the IdP (paramater
<tt>wfresh</tt>)</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
tokenValidators </td><td colspan="1" rowspan="1" class="confluenceTd">
TokenValidators </td><td colspan="1" rowspan="1" class="confluenceTd"> Optional
</td><td colspan="1" rowspan="1" class="confluenceTd"> NA </td><td colspan="1"
rowspan="1" class="confluenceTd"> Custom Token validator classes can be
configured here. The SAML Token validator is enabled by default.<br
clear="none">
See example <a shape="rect" class="external-link"
href="http://svn.apache.org/viewvc/cxf/fediz/trunk/plugins/core/src/test/java/org/apache/cxf/fediz/core/CustomValidator.java";>here</a></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> signingKey </td><td colspan="1"
rowspan="1" class="confluenceTd"> Key for Signature </td><td colspan="1"
rowspan="1" class="confluenceTd"> Optional </td><td colspan="1" rowspan="1"
class="confluenceTd"> Metadata signature </td><td colspan="1" rowspan="1"
class="confluenceTd"> If configured, the published WS-Federation <a
shape="rect" href="fediz-metadata.html" title="Fediz Metadata">Metadata
document</a> is signed by this key. Otherwise, not
signed.</td></tr></tbody></table>
</div>
