Author: buildbot
Date: Wed Feb 27 00:25:21 2013
New Revision: 852140
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/application-server-specific-configuration-guide.html
websites/production/cxf/content/docs/ws-trust.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified:
websites/production/cxf/content/docs/application-server-specific-configuration-guide.html
==============================================================================
---
websites/production/cxf/content/docs/application-server-specific-configuration-guide.html
(original)
+++
websites/production/cxf/content/docs/application-server-specific-configuration-guide.html
Wed Feb 27 00:25:21 2013
@@ -123,11 +123,11 @@ Apache CXF -- Application Server Specifi
<div class="wiki-content">
<div id="ConfluenceContent"><p>This document provides app server-specific
configuration information for running Apache CXF.</p>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1361811507075 {margin-left: 1.5em;padding: 0px;}
-div.rbtoc1361811507075 ul {list-style: disc;margin-left: 0px;padding-left:
20px;}
-div.rbtoc1361811507075 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1361919802732 {margin-left: 1.5em;padding: 0px;}
+div.rbtoc1361919802732 ul {list-style: disc;margin-left: 0px;padding-left:
20px;}
+div.rbtoc1361919802732 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="rbtoc1361811507075">
+/*]]>*/</style><div class="rbtoc1361919802732">
<ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-JBossApplicationServer">JBoss
Application Server</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-WebLogic">WebLogic</a></li><ul><ul><li><a
shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Putjarsinendorsedfolder">Put
jars in endorsed folder</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Packwarinanear%2Cdeploytheearwithweblogicapplication.xml">Pack
war in an ear, deploy the ear with
weblogic-application.xml</a></li></ul></ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Websphere">Websphere</a></li><ul><li><a
shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-ForWebSphereVersions%3C6.1.0.29">For
WebSphere Versions < 6.1.0.29</a></li><ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-NoWebServicesFeaturePackforWebSphereinstalled">No
Web Services Feature Pack for
WebSphere installed</a></li><ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-putjarintheendorsedfolder">put
jar in the endorsed folder</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Addyourownclassloader">Add
your own class loader</a></li></ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-WebServicesFeaturePackforWebSphereInstalled">Web
Services Feature Pack for WebSphere Installed</a></li></ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-ForWebSphere6.1.0.29%2CV7andV8">For
WebSphere 6.1.0.29+, V7 and V8</a></li></ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Glassfish">Glassfish</a></li><li><a
shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-OC4J">OC4J</a></li><ul><li><a
shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Disclaimer">Disclaimer</a></li><li><a
shape="rect" href="#ApplicationServerSpecificConfigur
ationGuide-Background">Background</a></li><ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Configurationoverview">Configuration
overview</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-OracleOC4Jclassloading">Oracle
OC4J class loading</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Neededcomponents">Needed
components</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Preparingstaxapi">Preparing
stax-api</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-ReplacetheOracleXMLparserwithXerces">Replace
the Oracle XML parser with Xerces</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-GetridofOC4JJAXWSlibraries">Get
rid of OC4J JAX-WS libraries</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-swappingOracle%7B%7Bwsdl.jar%7D%7Dwith%7B%7Bwsdl4j.jar%7D%7Dand%7B%7Bjaxb.jar%7D%7DAPIwit
h%7B%7Bjaxbapi2.0.jar%7D%7D">swapping Oracle <tt>wsdl.jar</tt> with
<tt>wsdl4j.jar</tt> and <tt>jaxb.jar</tt> API with
<tt>jaxb-api-2.0.jar</tt></a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Deployingapplications">Deploying
applications</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-OracleFAQ">Oracle
FAQ</a></li><ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-I%27mgetting%7B%7Bjava.lang.ClassCastException%3Aorg.apache.xerces.jaxp.DocumentBuilderFactoryImpl%7D%7D">I'm
getting <tt>java.lang.ClassCastException:
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</tt></a></li><li><a
shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-IcannotgetWSDL%28gettingHTTP500accesingmyCXFserviceWSDLwith">I
cannot get WSDL (getting HTTP 500 accesing my CXF service WSDL with
http://myshot/myservice?wsdl)</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-I%27mgett
ing%7B%7Bjava.lang.NoSuchMethodException%3Aoracle.j2ee.ws.wsdl.extensions.soap.SOAPBodyImpl.getElementType%28%29%7D%7D">I'm
getting <tt>java.lang.NoSuchMethodException:
oracle.j2ee.ws.wsdl.extensions.soap.SOAPBodyImpl.getElementType()</tt></a></li><li><a
shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Icannotgetittoworkstill">I
cannot get it to work still</a></li></ul></ul></ul><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-IntegrationwithApplicationServerFAQ">Integration
with Application Server FAQ</a></li><li><a shape="rect"
href="#ApplicationServerSpecificConfigurationGuide-Resources">Resources</a></li></ul></div>
<h2><a shape="rect"
name="ApplicationServerSpecificConfigurationGuide-JBossApplicationServer"></a>JBoss
Application Server</h2>
@@ -136,7 +136,7 @@ div.rbtoc1361811507075 li {margin-left:
Starting from JBoss AS 6 M4, the default webservices stack is internally based
on Apache CXF; as a consequence users might experiment classloading issues with
classes from both the CXF libraries and its dependencies if included in
deployments and not properly isolated. Please refer to the relevant JBoss AS
documentation for details on how to turn on classloading isolation on the
application server version in use.</p>
<p>In particular, when willing to run Apache CXF based applications on top of
JBoss AS 7 series, users have basically two options:</p>
-<ul><li>use JBoss AS as if it was a servlet container with no WS
functionalities: this basically implies disabling the webservices subsystem for
the user deployment, hence preventing the AS webservices stack from processing
the ws endpoint deployment and letting the CXF libs included in the archive
deal with any WS invocations when CXFServlet is hit; the webservices subsystem
is turned off by adding a jboss-deployment-descriptor.xml as follows to the ws
endpoint deployment:
+<ul><li>use JBoss AS as if it was a servlet container with no WS
functionalities: this basically implies disabling the webservices subsystem for
the user deployment, hence preventing the AS webservices stack from processing
the ws endpoint deployment and letting the CXF libs included in the archive
deal with any WS invocations when CXFServlet is hit; the webservices subsystem
is turned off by adding a jboss-deployment-structure.xml as follows to the ws
endpoint deployment:
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-xml">
<span class="code-tag"><jboss-deployment-structure xmlns=<span
class="code-quote">"urn:jboss:deployment-structure:1.2"</span>></span>
Modified: websites/production/cxf/content/docs/ws-trust.html
==============================================================================
--- websites/production/cxf/content/docs/ws-trust.html (original)
+++ websites/production/cxf/content/docs/ws-trust.html Wed Feb 27 00:25:21 2013
@@ -238,10 +238,20 @@ If an STSClient is not found from the ab
<p>CXF supports some of the new functionality defined in the WS-Trust 1.4
specification. The currently supported features are listed below.</p>
-<h3><a shape="rect" name="WS-Trust-ActAs%282.2.10%29"></a>ActAs (2.2.10)</h3>
+<h3><a shape="rect" name="WS-Trust-ActAs"></a>ActAs</h3>
<p>The ActAs capability allows an initiator to request a security token that
allows it to act as if it were somebody else. This capability becomes
important in composite services where intermediate services make additional
requests on-behalf of the true initiator. In this scenario, the relying party
(the final destination of an indirect service request) may require information
about the true origin of the request. The ActAs capability allows an
intermediary to request a token that can convey this information.</p>
-<p>The following code fragment demonstrates how to use an interceptor to
dynamically set the content of the ActAs element in the STS RST. The value may
be a string containing well-formed XML or a DOM Element. The contents will be
added to the RST verbatim. Note that this interceptor is applied to the
secured client, the initiator, and not to the STSClient's interceptor chain.</p>
+<p>The content of the ActAs element to be sent in the STS RequestSecurityToken
call can be set in one of two ways:</p>
+
+<ol><li>By specifying a value for the JAX-WS property
SecurityConstants.STS_TOKEN_ACT_AS ("ws-security.sts.token.act-as")</li><li>By
specifying a value for the STSClient.actAs property.</li></ol>
+
+
+<p>For either case, the value can be one of the following:</p>
+
+<ul><li>A String</li><li>A DOM Element</li><li>A CallbackHandler object to use
to obtain the token</li></ul>
+
+
+<p>For example, the following code fragment demonstrates how to use an
interceptor to dynamically set the content of the ActAs element in the STS RST,
by specifying a value for SecurityConstants.STS_TOKEN_ACT_AS. Note that this
interceptor is applied to the secured client, the initiator, and not to the
STSClient's interceptor chain.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@@ -255,9 +265,7 @@ If an STSClient is not found from the ab
@Override
<span class="code-keyword">public</span> void handleMessage(Message
message) <span class="code-keyword">throws</span> Fault {
-
message.put(SecurityConstants.STS_TOKEN_ACT_AS, ...);
-
}
}
</pre>
@@ -277,20 +285,24 @@ If an STSClient is not found from the ab
<span class="code-tag"><property name=<span
class="code-quote">"actAs"</span> value=<span
class="code-quote">"..."</span>/></span>
<span class="code-tag"><property name=<span
class="code-quote">"properties"</span>></span>
<span class="code-tag"><map></span>
- <entry key=<span
class="code-quote">"ws-security.sts.token.properties"</span>
- value=<span
class="code-quote">"etc/bob.properties"</span>/>
- <entry key=<span
class="code-quote">"ws-security.callback-handler"</span>
- value=<span
class="code-quote">"interop.client.KeystorePasswordCallback"</span>/>
- <entry key=<span
class="code-quote">"ws-security.signature.properties"</span>
- value=<span
class="code-quote">"etc/alice.properties"</span>/>
- <entry key=<span
class="code-quote">"ws-security.encryption.properties"</span>
- value=<span
class="code-quote">"etc/bob.properties"</span>/>
+ ...
<span class="code-tag"></map></span>
<span class="code-tag"></property></span>
<span class="code-tag"></bean></span>
</pre>
</div></div>
+<h3><a shape="rect" name="WS-Trust-OnBehalfOf"></a>OnBehalfOf</h3>
+<p>The OnBehalfOf capability allows an initiator to request a security token
on behalf of somebody else. The content of the OnBehalfOf element to be sent in
the STS RequestSecurityToken call can be set in one of two ways:</p>
+
+<ol><li>By specifying a value for the JAX-WS property
SecurityConstants.STS_TOKEN_ON_BEHALF_OF
("ws-security.sts.token.on-behalf-of")</li><li>By specifying a value for the
STSClient.onBehalfOf property.</li></ol>
+
+
+<p>For either case, the value can be one of the following:</p>
+
+<ul><li>A String</li><li>A DOM Element</li><li>A CallbackHandler object to use
to obtain the token</li></ul>
+
+
<h2><a shape="rect" name="WS-Trust-WSTrustusingSPNego"></a>WS-Trust using
SPNego</h2>
<p>As of CXF 2.4.7 and 2.5.3, CXF contains (client) support for WS-Trust using
SPNego. See the following <a shape="rect" class="external-link"
href="http://coheigea.blogspot.com/2012/02/ws-trust-spnego-support-in-apache-cxf.html";
rel="nofollow">blog</a> for an explanation of what this entails, and how to
run some system tests in CXF for this feature. </p>
