NonStop SOAP for Java User's Manual

Using the Administration Tools
NonStop SOAP for Java User’s Manual—523860-001
5-13
Using the Apache Admin Tool (Web-Based)
•
page: the object is available until the target JSP page (in this case, the
rpcrouter.jsp) sends a response back or the request is forwarded to another
page (if you are using the standard deployment mechanism this is unlikely to
happen).
•
request: the object is available for the complete duration of the request,
regardless of forwarding.
•
session: the object is available for the complete duration of the session.
•
application: any page within the application may access the object. In
particular, successive service invocations belonging to different sessions will
share the same instance of the object. Be aware to observe that the value of
this attribute can have important security implications. The page and request
scopes assure the isolation of successive calls. In addition, application scope
implies that all service objects are shared among different users of the SOAP
server.
•
Method list— Defines the names of the method that can be invoked on this
service object.
•
Provider type—Indicates whether the service is implemented using Java, a
scripting language, or a user-defined provider. If you are using a user-defined
provider, you also need to specify the fully qualified class name of the provider, as
well as any options (key/value pairs) that you wish to pass to it.
•
For Java services, Provider class—Fully specified class name of the target
object that services the request.
•
For Java services, Use static class—If set to "Yes" the class method made
available is a static method, and no object is instantiated. When static invocation is
used, the "scope" property is not applicable.
•
Type mappings—To control the serialization and deserialization of specific Java
types to and from XML in a particular encoding style, you may need to provide
serialization and deserialization classes that know how to perform the correct
conversions for those types. The SOAP server already includes serialization
classes for most basic types in the SOAP encoding style, as well as a Bean
encoding class that can provide a generic serialization of a bean in terms of its
properties. Since different types may require additional support for correct
serialization, the SOAP server maintains a registry of Serializers and Deserializers.
The registry is accessible to service administrators through the SOAP
Administration tool, as well as through a program API. To register a (de)serializer
class, the class must implement the Serializer or Deserializer interfaces. For more
information, see org.apache.soap.util.xml.Serializer and
com.org.apache.soap.util.Deserializer.
•
Default Mapping Registry—Fully-qualified classname of a customized registry
that will manage the serializer/deserializers for the service. Must be a subclass of
org.apache.soap.encoding.SOAPMappingRegistry. In the XML deployment