Topic Index
Click on one of the letters below to jump immediately to that section of the index.
- | . | A | B | C | D | E | F | H | I | L | M | N | P | R | S | T | U | W | X
-sourcepro option [in 1.4.1 SourcePro C++ Compatibility]
.h++ products
using with HydraExpress [in 1.4.1 SourcePro C++ Compatibility]
Agent ports, default [in 3.2.2.1 Agent Ports]
Agent URL, setting [in 3.2.2.2 Setting the URL of the Agent]
Agent
startup and shutdown [in 3.2.1 Agent Startup and Shutdown]
AgentContext [in 5.3.1 Request Handling and Threading]
accessing Agent resources [in 5.3.1 Request Handling and Threading]
AJP13 connector [in 3.2.2 Agent Connectors]
Apache, configuring [in 3.4 Configuring Apache as an External Web Server]
Bobcat
now Agent servlet container [in 1.6 HydraExpress Mappings to LEIF Legacy Directory Structure]
was LEIF server [in 1.3 HydraExpress Libraries]
classes
naming conventions for [in A.1.2 Naming Conventions]
clients
logger to use [in 6.3 The Web Services Logger for Client Applications]
writing to a log [in 6.3 The Web Services Logger for Client Applications]
WSDL-defined client faults [in 7.3.2 Server Faults]
WSDL-defined faults [in 7.3 Faults]
code generator [in 1.2 HydraExpress Components]
code samples
client-side, for WSDL-defined faults [in 7.3.4 Generated Client-Side Code]
throwing WSDL-defined faults [in 7.3.2 Server Faults]
using loggers [in 6.3 The Web Services Logger for Client Applications]
Config [in 5.3.1 Request Handling and Threading]
connector properties [in 5.3.1 Request Handling and Threading]
connector configuration [in 3.2.2 Agent Connectors]
ConnectorImp [in 5.3 Creating a Custom Connector]
creating custom connectors [in 5.3 Creating a Custom Connector]
connectors [in 3.2.2 Agent Connectors]
AJP13 [in 3.2.2 Agent Connectors]
custom, creating [in 5.3 Creating a Custom Connector]
HTTP [in 3.2.2 Agent Connectors]
HTTPS [in 3.2.2 Agent Connectors]
consulting services [in B.1 Consulting Services and Training]
Core Library
location of header files [in 1.3.1 The Core Library]
directory
installation [in 2.2 The HydraExpress Directory Structure]
documentation, conventions [in A.1.1 Typographic Conventions]
documentation, list of [in 1.7 Documentation]
environment, setting
for HydraExpress [in 2.1 Configuring Your Environment]
error handling
servers [in 7.3.2 Server Faults]
examples
client faults [in 7.3.2 Server Faults]
server error handling [in 7.3.2 Server Faults]
shipped with HydraExpress [in 1.5 Shipped Examples]
Exception [in 7.1 Overview]
[in 7.1 Overview]
exceptions
HydraExpress [in 7.1 Overview]
SourcePro [in 7.2.2 Other Possible Exceptions]
Standard Library [in 7.2.2 Other Possible Exceptions]
to catch in generated samples [in 7.2.2 Other Possible Exceptions]
faults
how implemented on clients and servers [in 7.3.2 Server Faults]
implementation [in 7.3 Faults]
SOAP [in 7.1 Overview]
WSDL-defined faults [in 7.3.3 WSDL-Defined Faults]
handler chains
http [in 3.2.4 Handler Chains]
header files, location of in installation [in 1.3.1 The Core Library]
HTTP connector [in 3.2.2 Agent Connectors]
HTTPS connector [in 3.2.2 Agent Connectors]
HTTPS
configuring security [in 3.2.3 Configuring Secure Messaging with HTTPS]
HydraExpress
setting environment [in 2.1 Configuring Your Environment]
installation
location of Core header files [in 1.3.1 The Core Library]
libraries
12d [in 2.2 The HydraExpress Directory Structure]
15d [in 2.2 The HydraExpress Directory Structure]
primary libraries in HydraExpress [in 1.3 HydraExpress Libraries]
logger
client logging levels [in 6.3 The Web Services Logger for Client Applications]
custom logging formatter [in 6.2.1 Agent Logging Fundamentals]
custom [in 6.2.3 Creating and Using Custom Loggers]
default [in 6.2.1 Agent Logging Fundamentals]
global [in 6.2 The Agent Logger]
in client applications [in 6.3 The Web Services Logger for Client Applications]
levels, definitions of [in 6.2.1 Agent Logging Fundamentals]
[in 6.2.3.3 Creating a Rotating Log File]
[in 6.3 The Web Services Logger for Client Applications]
rotating [in 6.2.3.3 Creating a Rotating Log File]
separating messages [in 6.2.3.2.2 Separating Your Log Messages from the Agent Messages]
web services [in 6.3 The Web Services Logger for Client Applications]
MessageInfo
data structures [in 5.3.1 Request Handling and Threading]
messages
client code for WSDL-defined fault messages [in 7.3.4 Generated Client-Side Code]
example code for defining faults in WSDL [in 7.3.4 Generated Client-Side Code]
fault messages defined in WSDL [in 7.3.3 WSDL-Defined Faults]
separating log from Agent [in 6.2.3.2.2 Separating Your Log Messages from the Agent Messages]
multithreading
servlet container [in 3.3.3.1 Configuring Multiple Single-Thread Servlet Containers]
naming conventions for classes and methods [in A.1.2 Naming Conventions]
ports
Agent [in 3.2.2.1 Agent Ports]
issues with [in 3.2.2.1 Agent Ports]
project file
used in shipped examples [in 1.5.1 The Use of the HydraExpress Project File in Shipped Examples]
Rogue Wave Web site
technology access [in B.3 Web Access to Rogue Wave Technology]
rotating logger [in 6.2.3.3 Creating a Rotating Log File]
rwagent.xml
defined [in 3.2 Configuring the Agent]
rwsf::LogFormatter [in 6.2.1 Agent Logging Fundamentals]
rwsf::MessageInfo [in 5.3.1 Request Handling and Threading]
rwsfgen
code generator [in 1.2 HydraExpress Components]
RWxmsg
SourcePro exception class [in 7.2.2 Other Possible Exceptions]
security
customizing and configuring [in 3.2.3 Configuring Secure Messaging with HTTPS]
server faults [in 7.3.2 Server Faults]
servers
error handling [in 7.3.2 Server Faults]
faults [in 7.3 Faults]
servlet container
multithread and single thread issues [in 3.3.3.1 Configuring Multiple Single-Thread Servlet Containers]
servlet development in HydraExpress [in 1.2 HydraExpress Components]
servlets
configuring in web.xml [in 3.3 Configuring the Servlet Container]
[in 3.3.2 Configuring Individual Servlets in the Context-Level web.xml File]
single thread => See single-thread.
single-thread
accessing servlets [in 3.3 Configuring the Servlet Container]
[in 3.3.2 Configuring Individual Servlets in the Context-Level web.xml File]
attribute [in 3.3.3 Single-Thread and Multithread Issues]
SOAP
faults [in 7.1 Overview]
SoapFaultException [in 7.1 Overview]
[in 7.1 Overview]
[in 7.3.1 Client Faults]
SOAPworX
now Web services in HydraExpress [in 1.6 HydraExpress Mappings to LEIF Legacy Directory Structure]
SourcePro
compatibility [in 1.4.1 SourcePro C++ Compatibility]
exceptions [in 7.2.2 Other Possible Exceptions]
using older versions [in 1.4.1 SourcePro C++ Compatibility]
std::exception [in 7.2.2 Other Possible Exceptions]
technical support [in B.2 Technical Support]
threading
single-thread access to servlets [in 3.3 Configuring the Servlet Container]
[in 3.3.2 Configuring Individual Servlets in the Context-Level web.xml File]
training [in B.1 Consulting Services and Training]
URL
setting Agent [in 3.2.2.2 Setting the URL of the Agent]
Web server
configuring external [in 3.4 Configuring Apache as an External Web Server]
web services logger [in 6.3 The Web Services Logger for Client Applications]
Web services
library in HydraExpess [in 1.3 HydraExpress Libraries]
web.xml
global file [in 3.3 Configuring the Servlet Container]
[in 3.3.1 Configuring the Global web.xml File]
worker configuration
ajp13 [in 3.4.2.2 Configuring AJP13 Workers]
worker.properties [in 3.4.2 Configuring the Apache Web Server]
WSDL
client code for WSDL-defined faults [in 7.3.4 Generated Client-Side Code]
defining of fault messages [in 7.3.3 WSDL-Defined Faults]
example code for defining faults [in 7.3.4 Generated Client-Side Code]
throwing faults defined in WSDL [in 7.3.2 Server Faults]
XML binding
in HydraExpress [in 1.2 HydraExpress Components]
XML Object Link
now XML Binding in HydraExpress [in 1.6 HydraExpress Mappings to LEIF Legacy Directory Structure]
XmlName [in 7.3.2 Server Faults]
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.