Complete Contents
Introduction
Chapter 1 About Netscape Application Server Extensions
Chapter 2 About the Netscape Extension Builder
Chapter 3 Introduction to Netscape's Interface Definition Language
Chapter 4 Designing a Netscape Extension
Chapter 5 Generating Output Files
Chapter 6 Completing Method Stubs
Chapter 7 Using Template Streaming
Chapter 8 Managing State and Session Information
Chapter 9 Using Object Pools
Chapter 10 Compiling the Extension Source Code
Chapter 11 Deploying and Managing a Netscape Extension
Chapter 12 Example Extension: HelloWorld
Appendix A C++ Helper Functions
Appendix B Java Helper Static Methods
Appendix C Java Class Decorations
Appendix D Reserved Words
Appendix E The ConnManager.cpp File
Glossary
Next Contents Index


Introduction

The Developer's Guide explains how to build extensions, which are services residing in Netscape Application Server. Extensions enable legacy systems, third-party solutions, and shared services to be integrated into Netscape Application Server applications without the need to rebuild the original functionality.

Developer's Guide is broken into the following parts:


Syntax Conventions
Symbol
Indicates
[ ]
An optional item
< >
A term that you substitute with an actual value

Place holder for commands not listed in an example


Programming Language Conventions
You can build an extension using either Java or C++. Some tasks are significantly different depending on the language used. In this case, the topics are usually presented in separate sections.

For other tasks, the basic approach is the same for both languages, but there are slight differences in syntax. When this is the case, text is marked as applying specifically to Java or C++. For example, paragraphs that distinguish between C++ and Java implementation of accessors would read as follows:

C++
The global function is KET_Get_<service_module> and the function signature is found in <NEB_ROOTDIR>\extensions\include\access_<service_module>.h.

Java
The static method is get<service_module> in class access_<service_module>.


Operating System Conventions
You can build extensions on Unix or Windows NT. Differences between the two operating systems are explained as needed. In many cases, the only difference is the specification of pathnames, which require a forward slash (/) on Unix and a backward slash (\) on Windows NT. Developer's Guide uses the following conventions for pathnames on either operating system:

Pathname
Indicates
<NEB_ROOTDIR>
Directory in which you installed NEB.
<NAS_ROOTDIR>
Directory in which you installed NAS.

The Windows NT naming convention is used when describing files that are equivalent on both operating systems—that is, when the only difference is the pathname separators. For example:

<NEB_ROOTDIR>\my_extension\cpp\CClass.cpp

 

Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.