Sun[tm] ONE Studio 4 update 1, Mobile Edition Release Notes
(formerly Forte[tm] for Java[tm], Mobile Edition)

• Introduction
• What's New: Enhancements and New Features
  • The Mobile Edition Customized Environment
  • Redistributing the Mobile Edition
  • Core Modules New Features
• System Requirements
• Supported Platforms
• Module Notes
• Installation Bugs and Issues
• Mobile Edition Bugs and Issues
• Core IDE Bugs and Issues
• Accessibility
• Other Documentation
• Update Center
• NetBeans[TM] Open Source Project
• Third-Party Licenses and Attributions

Introduction

The Sun™ Open Net Environment (Sun ONE) Studio 4 Update 1, Mobile Edition Release Notes contain information originally contained in the Sun[tm] ONE Studio 4, Mobile Edition (formerly Forte™ for Java™ 4, Mobile Edition) Release Notes, with the addition of significant features and the addition and deletion of bugs specific to this update release.

NOTE: Sun ONE Studio 4 requires the Java™ 2 Software Development Kit, Standard Edition (J2SE™ SDK) v. 1.4.0_02 (for the Sun ONE Application Server) or a version no earlier than 1.3.1_01 (for use with other servers).

For more information about the J2ME Wireless Toolkit that is packaged with the Mobile Edition, and to see the release notes for version 1.0.4 of the toolkit, see the J2ME Wireless Toolkit Release Notes in the <s1studio_home>\emulator\j2mewtk-1.04-<xxx> directory of your installation. Note that some of the information might not apply. For example, tools such as the KToolbar have not been integrated into the Mobile Edition.

What's New: Enhancements and New Features

The Sun^TM ONE Studio 4, Mobile Edition IDE is specially customized to support and facilitate the development of CLDC/MIDP applications for the J2ME^TM platform. It combines the technologies of the J2ME Wireless Toolkit with the Sun ONE Studio programming environment to provide the following:

• Integrated compilation, preverification, and execution of MIDlets and MIDlet suites
• Automatic generation of JAD and JAR files
• Integrated source-level debugging of MIDlets
• Code completion against J2ME APIs
• The ability to preset default compiler/preverifier on a per project basis
• Integration with third party emulator/SDKs through the Unified Emulator Interface
• Templates for creating MIDlets and MIDlet suites
• An integrated default emulator
• The ability to dynamically switch emulators for each MIDlet suite
• An Update Center tool that enables you to add modules and extend other features of the IDE

Added in Sun ONE Studio 4 update 1

• The J2ME Wireless Toolkit has been updated from version 1.0.3 to 1.0.4_01.
• Utilities in the Wireless Toolkit enable you to test application performance.

The Mobile Edition Customized Environment

To provide the simplest yet most comprehensive environment possible, Sun has removed some core modules of the Sun ONE Studio 4, Community Edition IDE. These features are unsupported by the J2ME platform, or are unnecessary for creating mobile device applications.

Note that some removed modules are still described in the core IDE help, due to their integral importance to programmers working on the J2SE^TM platform.

You can add many of the removed modules to the Mobile Edition IDE by using the Update Center.

The following table describes some of the modules that might be available from the Update Center. The table lists each module's name and a description of the module.

Redistributing the Mobile Edition

The following files are a Redistributable, subject to the terms and conditions of the Binary Code License (BCL) and its Supplemental Terms.

1. Files that comprise the Core IDE, stored in directories <s1studio-home>, _uninst, bin, docs, lib, sources, and system.
2. Files that comprise the Core IDE as described in 1), and additional modules stored in the modules directory.

Core Modules

The following section describes enhancements and new features for the core IDE modules included in the Mobile Edition.

Ant Support

• The bundled version of Ant has changed from 1.3 to 1.4.1.
  
  
• You can create a shortcut to any target in an existing Ant script. You can save the shortcut as a menu item, toolbar button, keyboard shortcut, or project link.
  
  
• The Create Properties File wizard and Add Property command enable you to easily store and manage an Ant script's properties in an ant.properties file.
  
  
• You can run any target in an existing Ant script from the contextual menu of the Ant script's Explorer node.
  
  
• The module provides better annotation and highlighting of build errors in an Ant script's output.

Debugger

• You can now filter the variables that are displayed in the Debugger Window.



• The Debugger window has been redesigned to enable viewing of different views simultaneously. You can define which views are displayed with toggle buttons in the window's toolbar.



• Breakpoints are now organized into groups, which allows you to enable, disable, or remove multiple breakpoints as a single unit.

JAR Packager (core)

• JAR contents files are now called JAR recipe files.

 
• Each entry in a JAR recipe file is now represented by a subnode of the JAR recipe's node in the Explorer. This makes it easier to make property changes to each entry.

Miscellaneous IDE Changes 

• When creating a new text file, you can specify the extension to use via a panel in the New Wizard.
  
   
• Some keyboard shortcuts have been changed. Refer to the online help page, "Keyboards Shortcuts" for a summary.

• The ability to append to or replace environment variables from within the IDE has been modified, such as for services for compiling and running programs. See the online help topic, "Managing Environment Variables". 

• The IDE does not automatically restart every time you complete an update through the Update Center. In the Update Center wizard, you can choose to wait to have the new modules installed the next time you launch the IDE.

• In MDI mode, frames have a contextual menu that has commands for minimizing, maximizing, closing, and attaching/detaching from MDI. See the online help topic, "Using a Multiple Document Interface".

Output Window 

• You can now enter information directly into the Output Window when running Commands that require user input.

 
• Custom text selection is provided.

 
• Coloring/tagging of defined lines.

 
• Error messages in the Output Window, such as those produced when compiling, running build scripts, or validating XML documents, are linked to the line where the error occurred in the Source Editor.

 
• You can now set a limit on window history.

 
• Command in the window's context menu to initiate or stop redirection of output.

Projects 

• There is no longer a Project Settings window. All IDE settings are now handled in the Options window. You can configure settings by project or globally for all projects.

Source Editor 

• Annotations, in the form of special background color and icons, are now used to indicate special information about given lines in the Source Editor.

 
• Editor settings are now stored in XML files in your IDE user directory, so you can easily move your settings from one system to another or share them with another user.

Version Control System Support 

• The VCS Groups feature enables you to create and group links to related version-controlled files. You can organize these links into groups in the VCS Groups window. You can then run VCS commands on an entire group or on an individual link.

 
• The Revision Explorer has been replaced by the Versioning Explorer. The Versioning Explorer displays a tree view of all mounted VCS filesystems and their contents. Each file's Versioning Explorer node contains a full history of its revisions, branches, and commit logs.

 
• The IDE saves the advanced command options you use to run VCS commands. You can easily reload previous configurations of command options and set the default configuration for each command.

 
• CVS support now includes the Annotate and History commands. The built-in CVS client also added the Import and Export commands.

Using KSOAP with Web Services

NOTE: Web Services support is not included in the Sun ONE Studio 4, Mobile Edition. For Web Services support, you must be using Sun ONE Studio 4, Enterprise Edition, updated with the kjava.nbm and kjava-emulator_xxx.nbm modules as described below.

1. Use the Autoupdate Center to get the kjava-emulator_xxxxx.nbm (_linux.nbm, _sol.nbm or _win.nbm, depending on your platform) and the kjava.nbm
2. Create and deploy your service.
3. Set your generated clients Soap Runtime property to kSoap.
4. Generate the client proxy.
5. Set the client proxy's property sheet, in the execution tab, to the following:
   • Compiler: Preverify Compiler
   • Debugger: Emulator Debugger
   • Executor: Emulator Executor
6. Create a MIDlet class to call the client proxy.
7. Execute the MIDlet class.
   The MIDlet class calls the client proxy which, in turn, calls the web service and sends back the response.

System Requirements

The following table lists the system requirements needed to install a minimum configuration on any of the supported platforms. The first column lists the type of requirement: hardware system, memory, and necessary disk space. The right columns lists the requirements by platform: Solaris 8 operating environment, various Microsoft Windows platforms, and Linux.

Supported Platforms

Sun ONE Studio 4, Mobile Edition requires a Java^TM 2 SDK, v. 1.3.1, or 1.4.0_02.

The following lists the platforms upon which the Sun ONE Studio 4, Mobile Edition has been tested. The platforms upon which the J2ME, Wireless Toolkit 1.0.4_01 has been tested are also listed.

NOTE: The platforms supported by the Mobile Edition might differ from those supported by the emulator you plan to use. You should verify that both the Mobile Edition and the emulator you plan to use are supported on your particular platform.

Sun ONE Studio 4, Mobile Edition has been tested on the following platforms and we recommend you use these platforms:

• Microsoft Windows XP Professional
• Microsoft Windows 2000 Professional system (Service Pack 2)
• Red Hat Linux 7.2
• Solaris 8 operating environment (64-bit, SPARC platform)
• Solaris 9 operating environment (64-bit, SPARC platform)

This release has been tested on a limited basis on the following platforms:

• Microsoft Windows NT4 SP6 systems
• Microsoft Windows 98
• Solaris 8 operating environment (32-bit, SPARC platform)
• Solaris 9 operating environment (32-bit, SPARC platform)

The J2ME, Wireless Toolkit, version 1.0.4_01 has been tested on the following platforms and we recommend you use these platforms:

• Microsoft Windows NT 4.0 systems
• Microsoft Windows 2000 systems

The J2ME, Wireless Toolkit, version 1.0.4_01 has been tested on a limited basis with the following, unsupported systems:

• Microsoft Windows 98 Second Edition
• Solaris 8 operating environment
• Red Hat Linux 6.2
• Red Hat Linux 7.1

NOTE: Sun ONE Studio 4 requires J2SE SDK v. 1.4.0_02 or a version no earlier than 1.3.1_01.

Module Notes

General Considerations

On some Sun ONE Studio 4 configurations on the Solaris operating environment, Netscape will not be automatically started by the IDE In this situation, you should start Netscape manually, after which you will be able to use Netscape with the IDE correctly.

-J-Dnetbeans.debugger.jpda.transport=dt_shmem

Installation Bugs and Issues

Windows Platform

• The first time you start the IDE, you are prompted to specify the user directory for that edition. No default user directory name will be offered to you; however you are strongly advised to use $HOME/ffjuser40me (substituting the Windows equivalent of $HOME).
• You should not share user directories with older versions of the IDE or with different editions of Sun ONE Studio 4.

Mobile Edition Bugs and Issues

NOTE: Linked Bugs other than those available through SunSolve require a Java Developer Connection login to view.

• 4641426 Description: The J2ME Wireless Toolkit v.1.0.4_01 preverifier does not support JDK 1.4.0 classes. If you are using J2SE v.1.4, the default for the Preverify compiler is an internal compiler. If you want to use an external compiler or download an updated internal compiler, you need to configure the Preverify Compiler properties within the Mobile Edition to use the external compiler.
  
  Workaround: Choose Tools > Options > Building > Compiler Types. Click in the Java Compiler property field and select External Compilation from the menu. Click on the ellipsis(...) button in the External Compiler property field and add the switch -target 1.1 to the Arguments field. The syntax for the External Compiler property is: {jdk.home}{/}bin{/}javac -target 1.1 {debug info} {deprecation} {optimize} {outputdir} {encoding} {source opt} {bootclasspath.opt} {bootclasspath} -classpath {filesystems}{:} {classpath} {files}.
  
  
• 4636172 Description: When a MIDlet is executed or debugged outside of a suite, no application descriptor file is used for execution and the getAppProperty() method of the MIDlet returns null. Workaround: Debug the MIDlet suite that contains the MIDlet instead of debugging the MIDlet by itself.
  
  
• 4676586 Description: If you rename a MIDlet Suite using the contextual menu, the MIDlet Suite cannot be executed because the JAR file URL has not been changed. Workaround: Change the JAR URL property of the suite.
  
  
• 4666440 Description: If you are using JDK 1.4 with the J2ME Wireless Toolkit 1.0.4_01, you cannot debug code inside a MIDlet's constructor. Workaround: Check to see if the latest available version of the J2ME Wireless toolkit fixes this problem, use a different emulator, or place the code from the constructor into the MIDlet's method and place a breakpoint in the method.
  
  
• 4721207 Description: MIDlet suites with external libraries (libraries in user-defined classpaths) can be compiled, but cannot be executed. Workaround: Add the library to the MIDlet suite JAR file, then execute.
  


• The J2ME Wireless Toolkit emulator requires JDK 1.3.1 or higher. If you run the IDE with the -jdkhome switch pointing to JDK 1.3.1 or 1.4, but have a default system setting of 1.2.1 or below, the emulator will not be able to execute any programs.
  
  
• The Windows registry key used by Sun ONE Studio 4 Update 1, Mobile Edition is HKEY_CURRENT_USER\Software\Sun Microsystems, Inc.\Forte for Java\ME\4.0


• The Windows registry key used by the J2ME Wireless Toolkit, v. 1.0.4_01 is HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems, Inc.\J2ME Wireless Toolkit\1.0.4_01

Core IDE Bugs and Issues

Note: Linked Bugs other than those available through SunSolve require a Java Developer Connection login to view.

General IDE Issues

• 12496 Description: When right-clicking a node, the contextual menu appears in the upper-left corner of the screen. This bug only occurs with some Linux window managers.


Workaround: In the IDE's installation directory, open the bin directory. Open the ide.cfg file and add the following option:

-J-Dnetbeans.popup.linuxhack=true

• 11149 Description: When working in MDI mode, the Explorer incorrectly gets focus when you click on the property sheet. If open a file in the Source Editor, the Properties window displays the properties for node selected in the Explorer instead of the file selected in the Source Editor.
   
• 11020 Description: There are startup errors if you have an incompatible XML parser in the classpath.


Workaround: Remove all JAR files from {jdk_home}/jre/lib/ext.

Filesystems or items within filesystems must be mounted and selected for you to display the template list for creating new objects when using File > New, the "New Wizard".



• 19700 Description: When using the Sawfish window manager and J2SE SDK v. 1.4, clicking on one of the main menu items causes the menu to drop down in the wrong location.


Workaround: Upgrade the Sawfish window manager to version 1.0.1.
 
• 12557 Description: If you try to modify source while it is still being loaded, there is a deadlock in the IDE.

 
• 19217 Description: Sizes of split maximized windows not remembered after restart.

 
• 19077 Description: Deleting a workspace that has the editor open on it causes the editor to close on all workspaces.

 
• 12451 Description: Commands from popup menu not fully visible. The bottom part of the CVS filesystem menu (not the individually checked out files) displays behind the Windows quick launch bar.


Workaround: In the ide.cfg file, set the netbeans.screen.rect property. It describes the rectangle on the screen where the menus will be described. It was intended for the case where Windows user has a task bar that is not at the bottom or is more then one row tall. For example, if your screen is 1024x768 and you have a two row task bar at 20 pixels per row, then try

runide.exe -J-Dnetbeans.screen.rect=0,0,1024,728
 

• 17771 Description: When the persistent Properties window is open as its own frame, selecting any node under IDE Configuration | Look and Feel | Workspaces in the Tools window causes the node to be renamed "Properties of Properties of Properties...". This change reverts once you close and reopen the Tools window.


Workaround: Dock the Properties window into the Explorer or close the Properties window while working in the Tools window.
 
• 14522 Description: Position of minimized frames in MDI mode changes after restart of the IDE.

 
• 19521 Description: SDK memory leak on clipboard operations can lead to OutOfMemory error on Solaris and Linux. This might be related to an SDK memory leak (see http://developer.java.sun.com/developer/bugParade/bugs/4531274)
   
• 19133 Description: AccessControlException when using the IDE's scripting module to run a DynamicJava script.

 
• 19506 Description: On Windows, if you set up the IDE to use Netscape 6 as the web browser and attempt to start the browser from the IDE, an error dialog is thrown which says "Could not access the URL through the external browser." However, the browser is eventually opened with the correct URL.
  

  Also, three Netscape windows end up being opened - a blank one, one with the user's home page, and one with the URL from the IDE.
   

• 19589 Description: When exporting to a WAR-file manually or automatically (by starting the built-in Tomcat server), all linked directories and files are included in the file, but they are not placed in the directory where the link originally was. They are instead placed in the root directory, and the web app can not find them.

 
• 11338 Description: On some configurations, the IDE freezes on exit when the HTTP server is running.

 
• 4623152 Description: When running on the J2SE SDK, v. 1.4, the IDE occasionally crashes when you uninstall modules.

  For J2EE development, it may be necessary to allocate more memory for the IDE.

  For example to allocate 150 MB for use with the IDE, use the following command line option:

  runide -J-Xmx150m

  Also, to view memory usage and free memory, there is a feature that can be enabled in the main IDE toolbar. To enable, right-click on the Toolbar and click on the checkbox for the Memory menuitem. To free up memory, click on the Garbage Collect toolbar button. To view memory usage, mouse over the memory usage graph.

  For more information, see
  http://performance.netbeans.org/articles/hat-howto/index.html#mtoolbar

• 23136 Description: On Solaris(TM) operating environment, New from Template Wizard. To reproduce, select a node on the Filesystems Tab of the Explorer.
  Shift-F10 to bring up context menu Click right arrow on "new"; use the up and down arrows to select different components: The IDE locks up and you can no longer navigate via keyboard, using the mouse unlocks the IDE. This is reproducible in the Solaris 9 operating environment with the Java 2 SDK v. 1.4 but it is not reproducible with the Java 2 SDK v. 1.4.1.

• 19491 Description: Some objects in the IDE appear as XML nodes instead of their original node type. For example, in the Options window, VCS Generic filesystem nodes under IDE Configuration appear as XML nodes. Workaround: Start the IDE with the netbeans.xml.uselooks=true switch,
  then right-click the node and choose Set Look > Basic.
  

Ant Support

• 16102 Description: If you include international characters in your Ant script, editing the script in the Explorer rewrites the ISO-8859-1 encoding to UTF-8. This problem does not occur if you use the UTF-8 character encoding for the script and UTF-8 is your platform's default encoding.

Workaround: Edit Ant scripts with international characters only in the Source Editor.
 
• 21180 Description: Ant scripts that use Internal Compilation print compilation errors to the wrong Output window tab. When using the Java 2 SDK v.1.4.0 and running Ant scripts that use Internal Compilation, the IDE sends error output from all Internal Compilation tasks to the same Output window tab. All other output is displayed on a new Output window tab for each Ant script. Workaround: Do not use Internal Compilation with Ant scripts with the Java 2 SDK v.1.4.0.  Use a different compiler type such as Jikes or External Compilation or use a different version of the the Java 2 SDK.

Debugger (Java)

The following are bugs in specific versions of the SDK or Java virtual machine that cause problems when debugging in the IDE.

• 4420211 Description: When running the IDE on Microsoft Windows systems with SDK 1.3 and SDK 1.3.1, JPDA shared memory transport is not available unless you have {JDKHOME}/bin in the PATH variable when running the IDE.


Workaround: Include {JDKHOME}/bin in the PATH variable when running the IDE.
 
• 4362206 Description: The debugged process can sometimes crash with FATAL ERROR in native method: JDWP "util.c".

  
• 4409562 Description: When using shared memory transport with the JPDA debugger, the IDE can sometimes crash with an EXCEPTION_ACCESS_VIOLATION error. This error occurs for all SDK 1.3 releases on the Microsoft Windows system when using the Java Classic VM.

Internationalization (I18N)

For Internationalization bugs, please refer to the Knowledge Base.

JAR Packager

• 14130 Description: Sometimes unable to successfully add files to the already created JAR recap file.
  
  Workaround: Use Java 2 SDK, SE v1.4.0_02.

Output Window

• 17337: Description: Using CTRL-C to copy in the Output Window causes the window to scroll to the bottom. This is caused by the fact that the Output Window accepts CTRL-C as input.

Projects

• 18530: Description: The IDE permits you to select project's root node as a main class, although this option should be disabled. When the IDE is set in this way and the project is executed, a StackOverFlow exception occurs.

 
• 21326: Description: When a JAR recipe file is mounted in the Explorer, changing projects sometimes throws an error. No data loss occurs.

Source Editor

• 5697 Description: Sometimes an unselected Source Editor window receives key strokes. This is an old and difficult-to-reproduce issue. Several attempts have been made to fix it, but the problem still recurs for some users. The problem seems to have diminished in FFJ 4.0.

 

• 17061 Description: When using an external editor (such as vi or xemacs), code generated from templates with the New wizard may be corrupted due to a lost character.
  Workaround: Use the IDE's built-in Source Editor when you create objects from template.

Version Control System Support

• 19697 Description: Calling CVS commands on deleted files causes a java.lang.ClassCastException. This sometimes happens when you use the Delete command in the IDE on a file and then try to call a CVS command on the node of the deleted file.

 
• 19691 Description: When your userdir name contains a space, the CVS commit command does not automatically load additional commit information in the commit log. The commit command still executes correctly.
  Workaround: Use a userdir that does not include spaces.
  
  
• 22851 Description: Get All and Add All commands sometimes do not execute completely. If this happens, some files might not be retrieved or added successfully.
  Workaround: Expand all of the folders and subfolders in your source tree before running the command to reduce the probability that the commands will fail. If a command fails, kill the command, invoke Refresh recursively on appropriate node, and run command again.
  
  
• 22436 Description: When generic VCS filesystems are mounted, switching projects can sometimes cause the IDE to hang.

• 23470 Description: Keyboard substitution options for the CVS Import command do not work. If you import a directory that contains binary files with the "Binary (-kb)" option, the binary files are treated as text files and data loss occurs.
  Workaround: Import binary files outside of the IDE..

Accessibility

Documentation

Online Help Documentation

The IDE provides many accessibility features that enable you to read about and use the product in the manner that is most comfortable and convenient to you. These features include:

• Mnemonics and keyboard shortcuts
• Customizable fonts
• Customizable colors
• Customizable toolbars
• Customizable stylesheets

For information on the accessibility features of the IDE, open the the online help and click the Accessibility topic in the table of contents.

Modifying Cascading Style Sheets for Accessibility

The instructions in the online help for modifying the cascading style sheet require additional information.

Most help sets use the style sheet that is stored in modules/docs/usersguide.jar. If you change this style sheet, the display of most other help sets is also affected. The exceptions (which are not included with the Mobile Edition) are as follows:

• The Database Schema help set uses the style sheet stored in dbschema.jar.
• The Web Services help set uses the style sheet stored in xmlservices.jar.

To change the cascading style sheet for the online help:

1. In your IDE installation directory, navigate to modules/docs.

2. Use the jar command-line utility to unpack the JAR file.

On Microsoft Windows and UNIX systems, the command is:

jar xf jar-file

For jar-file, use one of the following:

• usersguide.jar - Style sheet for most help sets
• dbschema.jar - Database Schema online help
• xmlservices.jar - Web Services online help

3. In the extracted hierarchy, navigate to the directory that contains the style sheet you want to edit:

• General online help - org/netbeans/modules/usersguide
• CORBA - org/netbeans/modules/corba/docs
• Database Explorer - org/netbeans/modules/db/docs
• Database Schema - com/sun/forte4j/modules/dbmodel/docs
• Web Services - com/sun/forte4j/webdesigner/docs

5. For the Database Explorer help set only. Edit each HTML file in the help set by adding the following line before the </HEAD> tag:

<link rel="stylesheet" href="ide.css" type="text/css">

6. Return to modules/doc in your installation directory and update the JAR file. On Microsoft Windows and UNIX systems, the command is:

jar ufv jar-file input-file

For jar-file use the name of the original JAR file, for example,
usersguide.jar. For input-file use, one of the following:

• org for the Users Guide, CORBA, and Database Explorer help sets
• com for the Database Schema and Web Services help sets
  

Solaris Operating Environment

The Solaris operating environment allows you to set window behavior using the Window Style Manager. When using mnemonics with the IDE, the window behavior should be set to "Click In Window To Make Active."
If this option is not set, in some cases, a mnemonic can appear to fail.

Other Documentation

Books

The following books can be downloaded in PDF format at http://forte.sun.com//ffj/documentation/index.html.

Mobile Edition

Sun ONE Studio 4, Mobile Edition Getting Started Guide
Sun ONE Studio 4, Mobile Edition Tutorial

Community Edition

Sun ONE Studio 4, Community Edition Getting Started Guide
Sun ONE Studio 4, Community Edition Tutorial
Using Java Database Connectivity
Building Web Components

Enterprise Edition

Sun ONE Studio 4, Enterprise Edition for Java Getting Started Guide
Sun ONE Studio 4, Community Edition Getting Started Guide
Sun ONE Studio 4, Enterprise Edition Tutorial
Sun ONE Studio 4 Community Edition Tutorial
Building Web Services
Building Web Components
Building Enterprise JavaBeans Components
Building J2EE Applications

The following books are also available within the Sun ONE Studio product distribution:

Solaris Native Languages Support Quick Start Guide
Native Connector Tool Quick Start Guide
Forte X-Designer User's Guide

Online Help

You can access online help for the IDE by choosing Help > Help Sets menu item from the main window. The Help menu also includes links to the Sun ONE Studio Developer's Resources homepage and other useful URLs.

Examples

You can find tutorials and examples together under Sun ONE Studio Developer's Resources: at http://forte.sun.com/ffj/documentation/tutorialsandexamples.html..

Knowledge Base

You can find answers to many of your questions by accessing a large, searchable FAQ database. This database is a dynamic, growing knowledge base that offers customized searches based on your needs. The Knowledge Base is located at http://forte.sun.com/cgi-bin/WebX.

Access to Bugs

You can access most Sun ONE Studio bugs through Java Developer Connection's Bug Parade.

Choosing a Browser with the Setup Wizard

In the Setup wizard you will be able to choose the type of HTML browser you can use to both browse the documentation in addition to external websites such as the Sun ONE Studio Developer Web Resources site. If you have a browser such as Netscape or Internet Explorer installed, be sure to choose "External Browser" rather than "Swing HTML Browser". The Swing HTML Browser is intended only for browsing the documentation and does not work with with most web sites.

Update Center

You can dynamically update the IDE using the Update Center feature. When you connect to the Update Center, the IDE checks to see if there are new modules or new versions of already installed modules available. If new or updated modules are available, you can select which ones you would like. Then those modules are downloaded and installed in your IDE.

NOTE: Sun ONE Studio NBMs are available through the Sun ONE Studio Update Center folders.

The AutoUpdate Wizard enables you to install modules from the Update Center or to install modules (in the form of .nbm files) that have been previously downloaded to your system. For both methods, the modules are .nbm format.

If you choose to the Sun ONE Studio Update Center, you will need to enter your Update Center login and password. If you do not have an Update Center login and password, you need to obtain one by clicking on the Account Maintenance button on the wizard and by following the instructions provided.

If you do not register, you can leave the Login and Password fields blank and you can still connect to the Update Center and see generally available free modules. However, to obtain access to upgraded third party or Enterprise Editions, you must register.

The Update Center uses this login and password to track user entitlements to various products and modules. The IDE sends the login and password over HTTP when you connect to the Update Center. When you register with the Developer Resources web site to get the login and password, we do ask for some personal information, however you can chose to not be contacted by Sun. For more information on Sun's privacy policy,see the Developer Resources Site FAQs at http://forte.sun.com/feedback/sitefaq.html

If you need to set a proxy to get through a firewall, you can click Proxy Configuration on the first page of the wizard.

You also can update modules in the IDE without having to connect to an Update Center server.

To update the IDE offline:

1. Manually download the NBM file of the module you want to update.
2. Choose Tools > Update Center from the main window.
3. In the first page of the wizard, select the Install Manually Downloaded Modules button.
4. Proceed according to the instructions in the rest of the wizard.

By default, the IDE periodically asks you whether you want to connect to the Update Center to check for new updates. You can set the interval for this prompt or turn it off completely.

To set the frequency that you are prompted to check for updates:

1. Choose Tools > Options from the main window.
2. Select the Update Center node and set the Check Period property.

NetBeans Open Source Project

The Sun ONE Studio IDE is based upon the NetBeans Open Source Project, located at http://www.netbeans.org. NetBeans is a community-based project that fosters the use of the NetBeans IDE framework in new, creative ways. All developers are invited to join the effort to extend the NetBeans IDE and improve the framework upon which it is based in order to create an extremely powerful set of tools by and for the development community.

Third-Party Licenses and Attributions

A) The following software may be included in this product: JSP/Servlet; ANT, 1.4.1; Crimson v1.1; RegExp; SOAP RPC Runtime, v2.2; Xerces 1.4.3; JAXPv1.2 RE; Tomcat v4.0.1; Xalan v2.3.1; Xalan v2.2; Xerces2 Java Parser 2.0.0; Servlet API v2.2; Use of any of this software is governed by the terms of the license below:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistribution 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. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

The names "Apache JServ", "Apache JServ Servlet Engine" and "Java Apache Project" must not be used to endorse or promote products derived from this software without prior written permission. Products derived from this software may not be called "Apache JServ" nor may "Apache" nor "Apache JServ" appear in their names without prior written permission of the Java Apache Project. Redistribution of any form whatsoever must retain the following acknowledgment: This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

THIS SOFTWARE IS PROVIDED BY THE JAVA APACHE PROJECT "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 JAVA APACHE PROJECT 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.

Enhydra PUBLIC LICENSE Version 1.1 below:

1. Definitions. This license is a union of the following two parts that should be found as text files in the same place (directory), in the order of preeminence: [1] This file itself, named EPL.html, [2] The contents of the file opl.html, stating the general licensing policy of the software.

2. Precedence of the license parts. In case of conflicting dispositions in the parts of this license, the terms of the lower-numbered part will always be superseded by the terms of the higher numbered part.

3. Lutris Technologies, Inc. is License Author. For the purposes of this License the "License Author" defined in section 1.13 of OPL.html shall be Lutris Technologies, Inc., 1200 Pacific Ave., Santa Cruz, CA. 95060. (http://www.lutris.com) 4. Section 11 of the OPL.html:

11. MISCELLANEOUS. This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California, excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in, the United States of America: (a) unless otherwise agreed in writing, all disputes relating to this License (excepting any dispute relating to intellectual property rights) shall be subject to final and binding arbitration, with the losing party paying all costs of arbitration; (b) any arbitration relating to this Agreement shall be held in San Francisco County, California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to this Agreement shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in San Francisco County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License.

5. Exhibit A. "The contents of this file are subject to the Enhydra Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License on the Enhydra web site (http://www.enhydra.org). Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific terms governing rights and limitations under the License. The Initial Developer of the Enhydra Application Server is Lutris Technologies, Inc. The Enhydra Application Server and portions created by Lutris Technologies, Inc. are Copyright Lutris Technologies, Inc. All Rights Reserved. Contributor(s): ______________________________________. "

6. Exhibit B. Part of the software embedded in this product is Enhydra (Java[TM]/XML Application Server), a trademark of Lutris Technologies Inc. Portions created by Lutris are Copyright 1997-2000 Lutris Technologies (http://www.lutris.com). All Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY LUTRIS AND ANY EXPRESS 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 AUTHOR 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.

7. Trademarks. You shall not remove or alter any Lutris or Enhydra trademark or trade name placed in the Original Code by Lutris. All copies of the Covered Code distributed by You shall include any such Lutris and Enhydra trademarks and trade names, as well as all required notices provided for in Sections 3.5 and 3.6. Except for the foregoing obligation, You are granted no rights to reproduce or display any Lutris or Enhydra trademarks or trade names.

8. Section 1.10 of OPL The following shall be added to section 1.10: "Original Code" shall include, but is not limited to, all the files in the Java packages in coveredCode.html.

Section 3.2 of OPL 1.0 As used in section 3.2 of the OPL "Contact Means" shall mean the email address info@lutris.com

D) The following software may be included in this product: Xemacs and libdwarf . Use of any of this software is governed by the terms of the license below:

GNU GENERAL PUBLIC LICENSE Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble. The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Programor any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

E) The following software may be included in this product: SAC v1.0, 1.1; Flute v1.1; DOM (Document Object Model); SAC v1.1. Use of any of this software is governed by the terms of the license below:

W3C® SOFTWARE NOTICE AND LICENSE

Copyright © 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/

This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:

Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:

1.The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.

2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright © [$date-of-software] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"

3.Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.

F) The following software may be included in this product: OpenORB. Use of any of this software is governed by the terms of the license below:

The OpenORB Enterprise Suite is available as an Open Source project in harmony with the BSD-like license [license.txt]:

Copyright (C) 1999-2001 Intalio, Inc. All Rights Reserved.

Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of this document.

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 name "ExoLab" must not be used to endorse or promote products derived from this Software without prior written permission of ExoLab Group. For written permission, please contact info@exolab.org.

4. Products derived from this Software may not be called "ExoLab" nor may "ExoLab" appear in their names without prior written permission of ExoLab Group. Exolab is a registered trademark of ExoLab Group.

5. Due credit should be given to the ExoLab Group (http://www.exolab.org).

THIS SOFTWARE IS PROVIDED BY INTALIO, INC. AND CONTRIBUTORS ''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 INTALIO, INC. 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.