Rogue Wave banner
Previous fileTop of DocumentContentsIndex pageNext file
HydraExpress Web Service Development Guide
Rogue Wave web site:  Home Page  |  Main Documentation Page

16.2 How HydraExpress Uses Named Objects

The generated <servicecontextname>_objects.xml file defines the objects needed to run a service. For a simple service such as the DayOfWeek example, the required objects are the server implementation and the server skeleton, or binding. When instantiated, these objects are instances of rwsf::NamedObject.


An object configuration file client-objects.xml is also generated on the client side for the message pattern notification. See Section 9.2 for more information.

The <servicecontextname>_objects.xml file is loaded by the Agent at startup. The server first creates the objects and then stores them together in a context object specific to the service, an instance of rwsf::NamingContext. This context object acts like a global registry that gives access to the objects.

Each <servicecontextname>_objects.xml file contains a series of <naming-obj> elements, each of which defines a named object. Each element contains two sub-elements: <naming-name>, which defines an object's associated name, and <naming-class>, which defines the create method for instantiating the object.

This is the dayofweek_objects.xml file generated for the DayOfWeek example:

//1

Defines the service implementation object.

//2

Defines the binding object.



Previous fileTop of DocumentContentsIndex pageNext file

Copyright © Rogue Wave Software, Inc. All Rights Reserved.

The Rogue Wave name and logo are registered trademarks of Rogue Wave Software, and HydraExpress is a trademark of Rogue Wave Software. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.