Introduction

The client reads a .soap file which contains the SOAP envelope to be sent. Examples of SOAP files are located in INSTALL_DIR/examples/filesystem/requests/. Each file is named appropriately based on the operation it contains. Use these files as models when creating your own .soap files. Make sure you modify the WS-Addressing header for the resource id to match the entry that is in the JNDI - configuration file and the resource id number for the instance you would like to invoke. This has to do with the home's implementation of getInstance() - and allows you to decide which instances are valid for sending requests.

@@ -92,17 +92,16 @@ alternative, you can use the following markers which are replaced at runtime:

$IP_ADDRESS$ - An attempt is made to determine the IP address at runtime. (Do not use on multi-homed systems).
$HOST_NAME$ - An attempt is made to determine the host name at runtime.
+ $IP_ADDRESS$ - An attempt is made to determine the IP address at runtime. (Do not use on multi-homed systems).
+ $HOST_NAME$ - An attempt is made to determine the host name at runtime.

The resourceIdentifierReferenceParameterName parameter represents the name of the WS-Addressing-header that is used to - extract a unique resource identifier to lookup a specific WS resource instance. This value should be a QName that includes the local - reference parameter name in the format - {target namespace}qualified name of a reference parameter - . If you omit - this entry, it is assumed that the service is a - SINGLETON - service and no resource id is expected in the + extract a unique resource identifier to lookup a specific WS-Resource instance. This value should be a QName that includes the local + reference parameter name in the format {namespaceURI}localPart, where namesapaceURI and localPart are the namespace and URI and local + part of the qualified name of the reference paramater that should contain the resource identifier. If you omit this entry, it is assumed that the service is a + SINGLETON service and no resource id is expected in the WS-Addressing headers.

Modified: webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/metadata.xml URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/metadata.xml?rev=226449&r1=226448&r2=226449&view=diff ============================================================================== --- webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/metadata.xml (original) +++ webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/metadata.xml Fri Jul 29 17:53:00 2005 @@ -8,11 +8,9 @@

Introduction -

Web services use metadata to describe what other endpoints need to know to interact with them. In particular, the metadata for a Web service includes the - service's description (WSDL or schema). There are two operations that are not defined by the WSRF specification that can be used in your services to retrieve metadata - about your services. The operations and messages are defined in the - WS-Metadata Exchange specification defined by Microsoft and - other industry contributors. +

Web services may have various metadata associated with them (e.g. the WSDL for the service or a set of Topic Space documents). The + WS-MEXWS-Metadata Exchange specification (defined by Microsoft + and other industry contributors) defines operations that can be provided by services to allow clients to retrieve these metadata documents.

@@ -59,8 +57,8 @@

Modify the JNDI Configuration File -

The JDNI configuration file must be modified to include a metadata resource for your service as well as configurations that define where your metadata files are located.

To update the JDNI configuration file to include metadata information:

The JNDI configuration file must be modified to include a metadata resource for your service as well as configurations that define where your metadata files are located.

To update the JNDI configuration file to include metadata information:

Using a text editor, open jndi-config.xml in the WEB-INF/classes directory.
Add the following JNDI resource block to the service, for which you would like to associate metadata: @@ -68,11 +66,12 @@ ]]>
The org.apache.ws.util.jndi.tools.MetadataConfigImpl object containing the metadata is available via JNDI using a Context lookup of - wsrf/services/{sevice_name}/metadata - i.e. ctx.lookup("wsrf/services/sushi/metadata"); + wsrf/services/{service_name}/metadata - i.e. ctx.lookup("wsrf/services/sushi/metadata");
In the metadata resource block, add a metadataConfig element that contains metadata configurations. The following examples demonstrate five different - methods of configuring where your metadata files are located. The files should be "reachable" at the configured locations.In the metadata resource block, add a metadataConfig element that contains metadata configurations. The configuration includes a dialect + attribute that defines the type of the data (xsd, wsdl, etc...) and an identifier attribute that uniquely identifies a particular document and is typically a targetNamespace. The + following examples demonstrate five different methods of configuring where your metadata files are located. The files should be "reachable" at the configured locations.
Modified: webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/singleton.xml URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/singleton.xml?rev=226449&r1=226448&r2=226449&view=diff ============================================================================== --- webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/singleton.xml (original) +++ webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/singleton.xml Fri Jul 29 17:53:00 2005 @@ -8,15 +8,15 @@
Introduction -
You can create a singleton service if only a single instance of a resource is required. If a service is a singleton, no resource ID is expected in the - WS-Addressing header. To create a singleton service, you must create a single instance of the resource in the generated home class and modify the deployed +
You can create a singleton service if only a single instance of a resource is required. If a service is a singleton, no resource ID parameter is expected in the + header of requests sent to the service. To create a singleton service, you must create a single instance of the resource in the generated home class and modify the deployed jndi-config.xml file.
Create a Single Instance -
Resource instances are created in the service's home class. For a singleton, set the createInstance method to null. This ensures - that only a single instance of the resource is created. For example:
+
Resource instances are created in the service's home class. For a singleton, specify an identifier of null when you call createInstance(). This + ensures that only a single instance of the resource is created. For example:
Modify the JNDI Configuration File -
To update the JDNI configuration file for a singleton:
+
To update the JNDII configuration file for a singleton service:
1. Using a text editor, open jndi-config.xml in the WEB-INF/classes directory.
2. From the ]]> block, remove the resourceIdentifierReferenceParameterName parameter. Modified: webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/validate.xml URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/validate.xml?rev=226449&r1=226448&r2=226449&view=diff ============================================================================== --- webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/validate.xml (original) +++ webservices/wsrf/trunk/src/site/content/xdocs/dev_guide/validate.xml Fri Jul 29 17:53:00 2005 @@ -8,20 +8,22 @@
  Introduction -
  All requests sent to the resource invocation framework are validated against any defined schemas. When validation fails, a fault that contains a detailed description of - exactly what is wrong with the XM is returned to the client. Request validation is performed using XMLBeans, which uses an in-memory - binary schema store. If the utmost performance is required, request validation can be disabled. -
  +
  All requests sent to the resource invocation framework are validated against any defined schemas types which have corresponding XMLBean classes located on the + classpath. When validation fails, a fault that contains a detailed description of exactly what is wrong with the XM is returned to the client. Request validation is performed using + XMLBeans, which uses an in-memory binary schema store. If the utmost performance is required, request validation can be disabled. +
  
  Disabling Schema Validation
  Schema validation is enabled by default. This means that all requests are validated. If you would like to disable this feature, you must set the - validateRequestXml property to false. The property must be set as a Java property before starting the container that is hosting Apache WSRF. - For example:
  + validateRequestXml system property to false. The property must be set as a Java property before starting the container that is hosting + Apache WSRF. For example:
  + -DvalidateRequestXml=false -
  If you are using Tomcat, you can set this property in the JAVA_OPTS variable before starting Tomcat. For example:
  +
  If you are using Tomcat, you can set this property in the JAVA_OPTS variable before starting Tomcat. For example:
  + set JAVA_OPTS=-DvalidateRequestXml=false - catalina.bat run + catalina.bat run
  Modified: webservices/wsrf/trunk/src/site/content/xdocs/release_notes.xml URL: http://svn.apache.org/viewcvs/webservices/wsrf/trunk/src/site/content/xdocs/release_notes.xml?rev=226449&r1=226448&r2=226449&view=diff ============================================================================== --- webservices/wsrf/trunk/src/site/content/xdocs/release_notes.xml (original) +++ webservices/wsrf/trunk/src/site/content/xdocs/release_notes.xml Fri Jul 29 17:53:00 2005 @@ -1,19 +1,24 @@ - - - -
  - WSRF Release Notes -
  - -
  - Change History -
  TODO
  -
  -
  - Known Issues -
  TODO
  -
  - + +
  + WSRF Release Notes +
  + +
  + Change History +
  Changes since the 1.0 Beta release:
  +
  +
  New and improved documentation including a Getting Started section and Developer Guide.
  +
  Updated Tutorial.
  +
  +
  +
  +
  + Known Issues +
  +
  TODO
  +
  +
  +