From jbossws-commits at lists.jboss.org Mon Oct 21 08:17:47 2013
Content-Type: multipart/mixed; boundary="===============5878126248711544132=="
MIME-Version: 1.0
From: jbossws-commits at lists.jboss.org
To: jbossws-commits at lists.jboss.org
Subject: [jbossws-commits] JBossWS SVN: r18028 -
stack/cxf/trunk/modules/dist/src/main/doc.
Date: Mon, 21 Oct 2013 08:17:46 -0400
Message-ID: <201310211217.r9LCHkiX006908@svn01.web.mwc.hst.phx2.redhat.com>
--===============5878126248711544132==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: asoldano
Date: 2013-10-21 08:17:46 -0400 (Mon, 21 Oct 2013)
New Revision: 18028
Modified:
stack/cxf/trunk/modules/dist/src/main/doc/Revision_History.xml
stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.=
xml
Log:
Updating documentation
Modified: stack/cxf/trunk/modules/dist/src/main/doc/Revision_History.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- stack/cxf/trunk/modules/dist/src/main/doc/Revision_History.xml 2013-10-=
21 12:16:07 UTC (rev 18027)
+++ stack/cxf/trunk/modules/dist/src/main/doc/Revision_History.xml 2013-10-=
21 12:17:46 UTC (rev 18028)
@@ -88,6 +88,20 @@
+
+ 4.2.2
+ Mon Oct 21 2013
+
+ Alessio
+ Soldano
+ alessio.soldano(a)jboss.com
+
+
+
+ JBossWS-CXF 4.2.2 documentation
+
+
+
Modified: stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User=
_Guide.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide=
.xml 2013-10-21 12:16:07 UTC (rev 18027)
+++ stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide=
.xml 2013-10-21 12:17:46 UTC (rev 18028)
@@ -438,15 +438,56 @@
=
Client configuration assignment
- JBossWS API comes with facility classes for assigning conf=
igurations when building up a client; JAXWS handlers can be read from clien=
t configurations as follows:
-
- import org.jboss.ws.api.configuration.ClientCo=
nfigUtil;
+
+ =
+ JAXWS Feature
+
+ The most practical way of setting a configuration is using
+ org.jboss.ws.api.configuration.ClientConfigFeature
+ , a JAXWS
+ Feature
+ extension provided by JBossWS:
+
+
+
+import org.jboss.ws.api.configuration.ClientConfigFeature;
+
+...
+
+Service service =3D Service.create(wsdlURL, serviceName);
+Endpoint port =3D service.getPort(Endpoint.class, new ClientConfigFeature(=
"META-INF/jaxws-client-config.xml", "Custom Client Config"));
+port.echo("Kermit");
+
+... or ....
+
+port =3D service.getPort(Endpoint.class, new ClientConfigFeature("META-INF=
/jaxws-client-config.xml", "Custom Client Config"), true); //setup properti=
es too from the configuration
+port.echo("Kermit");
+... or ...
+
+port =3D service.getPort(Endpoint.class, new ClientConfigFeature(null, tes=
tConfigName)); //reads from current container configurations if available
+port.echo("Kermit");
+
+
+
+ JBossWS internally parses the specified configuration file,=
if any, after having resolved it as a resources using the current thread =
context classloader. The
+ jbossws-jaxws-config schema
+ defines the descriptor contents and is included in the
+ jbossws-spi
+ artifact.
+
+
+
+ =
+ Explicit setup
+ Alternatively, JBossWS API facility classes can be used =
for assigning configurations when building up a client; JAXWS handlers can =
be read from client configurations as follows:
+
+ import org.jboss.ws.api.configuration.Client=
ConfigUtil;
import org.jboss.ws.api.configuration.ClientConfigurer;
=
...
=
Service service =3D Service.create(wsdlURL, serviceName);
-Endpoint port =3D (Endpoint)service.getPort(Endpoint.class);
+Endpoint port =3D service.getPort(Endpoint.class);
BindingProvider bp =3D (BindingProvider)port;
ClientConfigUtil.setConfigHandlers(bp, "META-INF/jaxws-client-config.xml",=
"Custom Client Config 1");
port.echo("Kermit");
@@ -465,19 +506,19 @@
=
...
=
-configurer.setConfigHandlers(bp, null, "Container Custom Client Config"); =
//reads from container configurations
+configurer.setConfigHandlers(bp, null, "Container Custom Client Config"); =
//reads from current container configurations if available
port.echo("Kermit");
-
- ... similarly, properties are read from client configurati=
ons as follows:
-
- import org.jboss.ws.api.configuration.ClientCo=
nfigUtil;
+
+ ... similarly, properties are read from client configura=
tions as follows:
+
+ import org.jboss.ws.api.configuration.Client=
ConfigUtil;
import org.jboss.ws.api.configuration.ClientConfigurer;
=
...
=
Service service =3D Service.create(wsdlURL, serviceName);
-Endpoint port =3D (Endpoint)service.getPort(Endpoint.class);
+Endpoint port =3D service.getPort(Endpoint.class);
=
ClientConfigUtil.setConfigProperties(port, "META-INF/jaxws-client-config.x=
ml", "Custom Client Config 1");
port.echo("Kermit");
@@ -496,19 +537,20 @@
=
...
=
-configurer.setConfigProperties(port, null, "Container Custom Client Config=
"); //reads from container configurations
+configurer.setConfigProperties(port, null, "Container Custom Client Config=
"); //reads from current container configurations if available
port.echo("Kermit");
-
-
- The default
- ClientConfigurer
- implementation parses the specified configuration file, if any=
, after having resolved it as a resources using the current thread context =
classloader. The
- jbossws-jaxws-config schema
- defines the descriptor contents and is included in the
- jbossws-spi
- artifact.
-
+
+
+ The default
+ ClientConfigurer
+ implementation parses the specified configuration file, if a=
ny, after having resolved it as a resources using the current thread contex=
t classloader. The
+ jbossws-jaxws-config schema
+ defines the descriptor contents and is included in the
+ jbossws-spi
+ artifact.
+
+
--===============5878126248711544132==--