Welcome to

ObjectStore Release 6.3

October 2005

This file provides the following information for ObjectStore™ Release 6.3:

Product Description

ObjectStore is an object-oriented database management system. It allows you to

ObjectStore includes the following installable components:

Supported Platforms

For information about supported platforms and other configuration information, see the ObjectStore Support Matrix at www.progress.com/realtime/techsupport/support_matrix.

Installing ObjectStore Release 6.3

PDF versions of the installation guide and release notes are in the same directory in the installation package as this README file. See Installing ObjectStore for Windows or Installing ObjectStore for UNIX for the following information:

You must use the Adobe Acrobat Reader 5.0 (or later) to view the PDF files. The Adobe Acrobat Reader is free and available from the Adobe Systems Web site.

New and Changed Features

The following major changes have been made to this release of ObjectStore:

These features are discussed more fully in the ObjectStore Release Notes.

Documentation

You can find a full set of product documentation as well as information about previous Service Packs on the ObjectStore Technical Support Web site at www.progress.com/realtime/techsupport/documentation. Documentation becomes available on the support Web site shortly after the software is released.

Optionally, you can install the documentation on one or more of your local systems. On Windows, if you installed the ObjectStore documentation, select Start->Programs->ObjectStore Win32->ObjectStore Documentation to display ObjectStore documentation in a Web browser.

On UNIX or Windows, if you installed the ObjectStore documentation, you can view the full documentation for ObjectStore by opening index.htm in the doc directory where ObjectStore is installed.

Before installation, PDF versions of the installation guide and release notes are in the same directory as this README file. After installation, the PDF documents are in the doc/pdf directory of your ObjectStore installation directory, along with PDF versions of the rest of the ObjectStore documentation. ObjectStore documentation is also provided in HTML format.

Last-Minute Information

The following sections provide information about Release 6.3 that is not included in the documentation.

New Keys for os_Dictionary

There are two new integer keys that can be used to specify the key type parameter when creating a dictionary:

Errors for Platform Information in Release Notes

In "Chapter 2: Platform and Release Compatibility" of the ObjectStore Release Notes, some of the information listed for platform compatibility is in error. For the most up-to-date information about supported platforms and other configuration information, see the ObjectStore Support Matrix at www.progress.com/realtime/techsupport/support_matrix.

Error About Namespace Usage in Release Notes

"Chapter 2: Platform and Release Compatibility" of the ObjectStore Release Notes states "ObjectStore public header files no longer contain using statements. If your pre-6.3 application depends on these statements, you must modify your application and recompile it with the 6.3 run-time libraries." This namespace issue statement is an error and you do not not need to change your pre-6.3 applications namespace usage.

Caution About Schema Evolution on Linux 32-bit

Before performing schema evolution for ObjectStore databases, release 6.2 or earlier, on the Linux 32-bit platform, contact technical support for information about how to evolve your schema. Technical support will provide a patch that prevents possible data corruption during schema evolution. For more information, see "Platform Configuration: Linux 32-Bit" in the ObjectStore 6.3 Release Notes.

Using OSJI on HP 32-bit Platforms

OSCI and OSJI libraries use the ANSI Standard C++ runtime (compiled with the -AA compiler option). Native applications must be compiled the -AA option and linked with the Standard C++ version of the JVM libraries. These libraries are distributed separately and may obtained from the same location where you download the JVM and RTE.

Also, when invoking the JVM, the -V2 option needs to be used. For example:

    java -V2 ...

See http://www.hp.com/products1/unix/java/infolibrary/prog_guide/JNI_java2.html#supportC++ under the heading "Support for C++ applications built with -AA and -AP options (PA-RISC)" for more information.

When using OSJI, it is possible for the Java heap and ObjectStore's persistent storage region (PSR) to interfere with each other. In such case, applications may fail with the following error:

	No handler for exception:
	ObjectStore internal error
	Fatal error Invalid argument(errno = 22)
	mmap failed: _Mmap_node::mmap  addr 50000000, len 
	0xc000000, prot 0, share 37, fd 8, off 0
	(err_internal)

One possible workaround is to limit the size of the heap that Java uses with the -Xmx option. Please see http://www.hp.com/products1/unix/java/infolibrary/prog_guide/expanding_memory.html#memory for details. Testing has shown that limiting the heap to 128MB (-Xmx128m) will work with most OSJI applications. However, depending on your application, different Java heap sizes may be needed.

If limiting the Java heap is not a viable workaround please contact ObjectStore Technical Support.

Schema Evolution for OSJI

If you are using the schema evolution API to evolve a schema, take note of the following.

There can be only a single schema evolution session created in an application, and there cannot be any other sessions in the application. You can only call Session.createSchemaEvolve if you have not previously called Session.create, and you cannot call Session.create if you have previously called Session.createSchemaEvolution. The OSJI classes in your CLASSPATH that you are evolving must be the new definitions of these classes, so you cannot perform persistent operations on the database that is being evolved using these classes before evolving the database.

Because of these requirements of OSJI schema evolution, we strongly suggest that you perform schema evolution as the only function of your schema evolution application.

Unexpected OSJI Exceptions with Multiple Threads on Windows

When an OSJI application on Windows platforms uses multiple threads in a single session, it is possible that a terminated thread can cause another still-running thread to throw an internal error. This internal error will then cause another error to be thrown which will disguise the actual problem. When a thread is terminated it is still associated with the session. If another thread relocates pages in the ObjectStore client, it will attempt to suspend the nominally terminated thread resulting in an error stating that SuspendThread has failed. The displayed error will read approximately:
  ObjectStore internal error
  SuspendThread failed for thread id NNN with error code 5 (err_internal)
This will be followed by another error:
  ObjectStore internal error
    ObjectStore internal lock hierarchy violation:attempting lock 
    (name = "schema info table" level = 3000) while holding lock 
    (name "LLPL-lock" leel = 500). (err_internal) 
The problem can be avoided by explicitly calling the Session.getCurrent().leave() method from the given thread as it completes its work. This method should be called for threads that explicitly join a session and for those that implicitly join a session.

Problems with the JMTL Simple RMI Example

If you run the JMTL Simple RMI example as delivered, it generates a java.lang.NullPointerException exception. In order to run this example properly, edit the deployment descriptor file jmtl-dd.xml and set the NumberOfMvccCaches element to 0.

Problem with OSJI pcount Demo Application with JDK 1.5

If you are running the OSJI pcount example application with JDK 1.5 on UNIX platforms, you need to set the DISPLAY environment variable. If you try to run the demo without setting the environment variable, you may see the following error message:

      Running the pcount demo.
           *** doall: Begin run of pcount demo
           java -Xmx128m -Xms128m -Ddb=pcount.odb com.odi.demo.pcount.OStorePersistentCounter
           Exception in thread "main" java.awt.HeadlessException:
           No X11 DISPLAY variable was set, but this program performed an operation which requires it.
                    at java.applet.Applet.(Applet.java:44)

Problems Caused by Primitive Types that Straddle Server Pages

If your schema uses the following, you need to be aware of a potential problem: The potential problem is that some primitive types and bit fields might straddle server page boundaries. This can happen when the alignment of the type is smaller than the size of the type. In most situations, you do not need to be concerned about this. However, if primitive types or bit fields do straddle server pages, this causes a problem in the following situations:

Schema Evolution with 6.2 Clients

If you try to evolve a 6.2 schema with a 6.2 schema evolution application or utility, and some primitive types or bit fields straddle server pages, the schema evolution facility initializes those types and fields to NULL. To avoid this, do one of the following:

Heterogeneous Applications

Primitive types or bit fields that straddle server pages can cause problems in a heterogeneous application that meets at least one of the following conditions:

Building and Running the OSNCI Travel Example

Before you build and run the ObjectStore .NET COM Interop ASP.NET travel example, you need to set the ASP.NET worker process to have permission to access the example directory and example database. For more information, see the readme file in the C:\ODI\osax\examples\travel directory.

WebLogic Server on Linux

If you are using WebLogic Server on Linux, be sure to add <bea_home>\weblogic81\server\lib\linux\i686 to your LD_LIBRARY_PATH environment variable.

Migrating 6.0 Applications that Use Anonymous enums

If you are migrating a 6.0 application to 6.3 and the application uses anonymous enums, you may have to perform schema evolution. Use the following procedure:

  1. Run the 6.3 version of ossg to generate the new schema for the application.
  2. Run the 6.3 version of osscheq against the newly generated schema and the existing database to see if schema evolution is needed.
  3. If schema evolution is needed, run the 6.3 version of ossevol.

For information about ossg, osscheq, and ossevol, see Managing ObjectStore. For information about migrating applications from ObjectStore 6.0 to ObjectStore 6.3.x, see the ObjectStore Migration Guide, which is available on the ObjectStore Documentation Web site.

Restriction on Leading doubles on AIX Platforms

If you are using the latest version of the AIX C++ compiler that is supported by this release of ObjectStore (for example, AIX5) and your application uses the packing pragma to pack a class that contains a double as its first member, ObjectStore will generate schema for the class that assumes a size that differs from the class size produced by the compiler. This discrepancy will result in a run-time error when the application allocates a persistent instance of the class.

The AIX Visual Age compiler forces classes that have a double as their first member to have a class size that is a multiple of 8 bytes. But the packing pragma can be used to override this restriction, as in the following example:

#pragma options align=packed
class foo {
public:
    double d;
    int i;
};

In this example, the AIX Visual Age compiler will produce instances of foo that are 12 bytes in size. But ObjectStore's schema-generation utility, ossg, will generate schema for foo that incorrectly assumes a size of 16 bytes. This discrepancy will result in a run-time error when the application attempts to allocate a persistent instance of foo.

The workaround is either to remove the pragma (in most cases, not a viable solution) or to order members of the class so that a double is not its first member, as in the following revision of foo:

#pragma options align=packed
class foo {
public:
    int i;
    double d;
};

In this case, ossg will generate schema for the class that agrees with the AIX Visual Age compiler about the alignment (8 bytes) and the size (12 bytes).

This restriction will be lifted in a future release of ObjectStore.

Problems with Inheritance Hierarchies on AIX Platforms

On AIX platforms, there is a known problem with inheritance hierarchies that involve the following:

If your schema appears to contain these characteristics and the ossg schema generator cannot generate schema, contact Technical Support. ossg can also fail to generate schema for inheritance hierarchies of more than two levels of virtual inheritance without repeated instances or virtual functions when neutralizing against the all32 architecture set.

Using the BankServer example

If you are running the CMTL BankServer example on Windows 2003, you may need to alter the Identity settings for the BankServer COM+ Application. Security settings and policy on your local machine may affect which users have the correct identity and privilege to launch certain COM+ Applications.

Obsolete ActiveX Interface for ObjectStore Documentation

The directory <install_dir>\osax\doc contains documentation for an obsolete ObjectStore component named ActiveX Interface for ObjectStore.

Version Number of ObjectStore Server and Cache Manager on Windows

The Windows control panel (Settings -> Control Panel -> Administrative Tools -> Services) incorrectly identifies the version number of the ObjectStore server and cache manager as R6.0. The correct version number of both services is R6.3.



License Information for Third-Party Products Used in ObjectStore

The following sections provide license information for third-party products used in ObjectStore.

SUN RPC Published by SUN Microsystems, Inc.

Sun RPC is a product of Sun Microsystems, Inc. and is provided for unrestricted use provided that this legend is included on all tape media and as a part of the software program in whole or part. Users may copy or modify Sun RPC without charge, but are not authorized to license or distribute it to anyone else except as part of a product or program developed by the user.

SUN RPC IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND INCLUDING THE WARRANTIES OF DESIGN, MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.

Sun RPC is provided with no support and without any obligation on the part of Sun Microsystems, Inc. to assist in its use, correction, modification or enhancement.

SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO THE INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS BY SUN RPC OR ANY PART THEREOF.

In no event will Sun Microsystems, Inc. be liable for any lost revenue or profits or other special, indirect and consequential damages, even if Sun has been advised of the possibility of such damages.

Sun Microsystems, Inc.
2550 Garcia Avenue
Mountain View, California 94043

Expat Published by Thai Open Source Software

Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

JTC/JThreads Published by Object Oriented Concepts

Portions of this program were created using JThreads/C++ by Object-Oriented Concepts, Inc.

Message Digest Algorithm

Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.

License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function.

License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work.

RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind.

These notices must be retained in any copies of any part of this documentation and/or software.

Apache License

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Ant License

                   The Apache Software License, Version 1.1
      Copyright (C) 2000-2003 The Apache Software Foundation. 
                      All rights reserved.
 
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met: 

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer. 

2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution. 

3. The end-user documentation included with the redistribution, if any,
   must include the following acknowledgment: "This product includes
   software developed by the Apache Software Foundation
   (http://www.apache.org/)." 

   Alternately, this acknowledgment may appear in the software itself, if
   and wherever such third-party acknowledgments normally appear.
 
4. The names "Ant" and "Apache Software Foundation" must not be used to
   endorse or promote products derived from this software without prior
   written permission. For written permission, please contact
   apache@apache.org. 

5. Products derived from this software may not be called "Apache", nor
   may "Apache" appear in their name, without prior written permission of
   the Apache Software Foundation. 

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE. 

This software consists of voluntary contributions made by many
individuals on behalf of the Apache Software Foundation. For more
information on the 
 
Apache Software Foundation, please see http://www.apache.org.

Xerces License

                   The Apache Software License, Version 1.1
          Copyright (C) 2000-2003 The Apache Software Foundation. 
                         All rights reserved.
 
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met: 

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer. 

2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution. 

3. The end-user documentation included with the redistribution, if any,
   must include the following acknowledgment: "This product includes
   software developed by the Apache Software Foundation
   (http://www.apache.org/)."

   Alternately, this acknowledgment may appear in the software itself, if
   and wherever such third-party acknowledgments normally appear. 

4. The names "Xerces" and "Apache Software Foundation" must not be used
   to endorse or promote products derived from this software without prior
   written permission. For written permission, please contact
   apache@apache.org. 

5. Products derived from this software may not be called "Apache", nor
   may "Apache" appear in their name, without prior written permission of
   the Apache Software Foundation. 

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE. 

This software consists of voluntary contributions made by many
individuals on behalf of the Apache Software Foundation. For more
information on the 
 
Apache Software Foundation, please see http://www.apache.org.



Copyright © 1989-2005 Progress Software Corporation. All rights reserved.