Sun™ ONE Studio 4 update 1 Release Notes

(formerly Forte™ for Java™)


(Community and Enterprise Editions)

Introduction

These release notes represent the combined release notes for both the Community and Enterprise Editions of the Sun™ Open Net Environment Studio 4 product.

The Sun™ ONE Studio 4 update 1 Release Notes contain information from the Sun™ ONE Studio 4 (formerly Forte for Java) Release Notes, with the addition of significant features or the addition or 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 use with the Sun ONE Application Server) or no earlier than 1.3.1 (for use with other servers).

What's New: Enhancements and New Features

Ant Support

Debugger (Java)

Form Editor 

J2EE Application Development

Sun ONE Studio 4's J2EE™ modules provide support for Enterprise JavaBeans™ providers and for assemblers and deployers of J2EE applications.

Wizards and other GUI-based features support the following tasks:

JAR Packager 

Miscellaneous IDE Changes 

Native Connector Tool

Available with the Solaris™ 8 operating environment, SPARC™ platform edition only; Sun ONE Studio 7, Compiler Collection (formerly Forte™ Developer 7) required.

The Native Connector Tool enables you to wrap C and C++ functions and data objects and expose them as Java classes. This tool can help ease the transition to new Java projects. In addition, you can use the tool to enable the deployment of legacy code as services.

To learn the basic steps for using the Native Connector Tool, print the 2-page quick start guide at /opt/s14studio/docs/nct_quickstart.pdf (if your Sun ONE Studio 4 software is not installed in /opt, ask your system administrator for the equivalent path on your system).

To run through a demonstration of the tool, choose Help > Helpsets > Native Connector Tool Help from the main window and select the Using NCT by Example topic from the table of contents.

Output Window 

The Sun ONE Studio 4 Output window has been re-implemented to behave more like a console; it has the following new features:

Program Performance Analysis Tools

Available with the Solaris™ 8 operating environment, SPARC™ platform edition only; Forte™ Developer 7 required.

The performance analysis tools help you assess the performance of your program, identify potential performance problems, and locate the part of the code where the problems occur. The tools collect timing data and hardware event data and trace calls to library routines, and display metrics of performance for functions, source lines and instructions. You can also see a timeline of the performance data.

For Java programs, you can collect and analyze timing and hardware counter data. The performance metrics are displayed on a per-method basis for methods that are compiled with the Java HotSpot™ virtual machine. Compiled methods often use the majority of the time, so these tools are a complement to other tools that display data for interpreted methods.

Limitations: You must use a version of the Java 2 SDK no earlier than 1.4 to collect data, and you must use the collect command to collect data. You cannot see metrics for interpreted methods, or for source lines.

For C, C++ and Fortran programs, or for functions in these languages that are called from Java programs, you can collect all types of data and use the full capabilities of the performance analyzer.

You can collect data and start the Performance Analyzer from the Debug menu if you have the Solaris Native Languages Support module. The same module provides support in the Explorer for performance data sets, which are called experiments. Double-click on an experiment to start the Performance Analyzer.

To use the performance analysis tools, you must have access to the Sun ONE Studio 7, Compiler Collection software release.

Projects 

RMI (in EE, can be added to CE via Autoupdate)

The RMI Module has the following enhancements for this release:

Solaris Native Languages Support

Available with the Solaris™ 8 operating environment, SPARC™ platform edition only; Forte™ Developer 7 required.

The Solaris Native Languages Support module provides support for editing and compiling code written in the following programming languages:

In addition, the module enables you to debug and analyze the performance of code written in:

To learn about the basic steps, print the two-page Solaris Native Languages Support Quick Start Guide at /opt/s1studio/docs/solaris_nat_lang_quickstart.pdf. If your Sun ONE Studio 4 software is not installed in the /opt directory,
ask your system administrator for the equivalent path on your system.

Source Editor 

Version Control System Support 

WebLogic

WebLogic Plug-in does not support CMP Version 1.x EJBs

The EJB 2.0 specification describes two versions of CMP entity beans: CMP version 1.x and CMP version 2.x. CMP version 1.x
entity beans follow the EJB 1.1 CMP specification. CMP version 2.x entity beans follow the EJB 2.0 CMP specification.

Sun ONE Studio supports the development of both CMP version 1.x and 2.x entity beans. However, the WebLogic Plug-in does
not support the deployment of any EJB module or J2EE application that contains a CMP version 1.x entity bean. Therefore, if you
want to use Sun ONE Studio to deploy a CMP Version 1.x entity bean to the WebLogic server, you must upgrade the bean to CMP
version 2.x. Refer to the Programming Series documentation, Building Enterprise JavaBeans Components, Appendix A for upgrade
instructions.

Web Services

Passwords in UDDI Registries System Option

Note that this Option is located under category "Distributed Application Support".
Passwords entered in the "Registries" custom property editor of this option are not stored as encrypted.  They are stored as text in a java serialization file under your Netbeans user data directory.  If you do not want a password to be stored in this manner, then do not enter passwords into this screen.  If no password is entered, then you will have to enter the UDDI login password when you run the wizard which publishes a Web Service to UDDI.
 

Early Access Customers Must use New UDDI Registries

This release supports only UDDI Version 2 registries. Thus the list of built-in registries that you used for the early access release is no longer correct, because it references only UDDI Version 1 registries.  To get the new list of built-in registries, edit the "Registries" property for the "UDDI Registries" global option and delete every row in the JTable at the top of the window.  Then press OK. Now edit the Registries property again, and you will see that the list has been reset to contain only UDDI Version 2 registries.

Support for Direct Business Method Calls

Web Services do not support Java classes that are not Java Bean-compliant. For example, all beans must have getters, setters, and a constructor.

Using KSOAP with Web Services
  1. Use the Autoupdate Center to get the kjava-emulator_linux.nbm (_sol.nbm or _win.nbm) 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.

For further information about MIDlets, review the Sun ONE Studio 4 ME documentation.

Using an External J2SDKEE with Web Services

Complete the following steps to update the Reference Implementation security settings:

For J2SDKEE 1.3

  1. Open the server policy file located in the your_drive:\j2sdkee1.3\lib\security directory of your J2EE installation.
  2. Update the following line:
    from
    permission java.io.FilePermission "<<ALL FILES>>","read";
    to
    permission java.io.FilePermission "<<ALL FILES>>","read, write, delete";
  3. Restart the RI

For J2SDKEE 1.4

  1. Open the server policy file located in the your_drive:\j2sdkee1.4\lib\security directory of your J2EE installation.
  2. Update the following line:
    from
    permission java.io.FilePermission "<<ALL FILES>>","read, write ";
    to
    permission java.io.FilePermission "<<ALL FILES>>","read, write, delete";
  3. Restart the RI

Limitations

BEA WebLogic

The BEA WebLogic 6.1, SP2 and 7.0 Application Servers have been certified by Sun ONE Studio 4 with the J2SE
SDK or JRE 1.3.1 only. If you use a BEA WebLogic server, ensure that you are using the J2SE SDK or JRE 1.3.1; do
not run the IDE with the J2SE SDK 1.4 or JRE 1.4.

Currently the Weblogic Plugin supports both 6.1 SP2 and 7.0 servers. Latest Weblogic Platform support is
available at the following URL.
http://e-docs.bea.com/wls/certifications/certifications/overview.html#1038205.

There is a limitation on using Sun ONE AS plugin and Weblogic plugin. Sun ONE AS plugin requires JDK 1.4.0_02 or above. (It uses latest JDK 1.4 APIs) where as Weblogic Plugin requires the same JDK supported by the weblogic server.

With the WebLogic plugin you cannot create a CMP bean from multiple tables, although WebLogic 7.0 has this new feature in the server.

When using WebLogic 7, the Weblogic plugin will by default use the JDK 1.3.1_03 installed with Weblogic 7. Using Jdk1.3.1_04 or higher will cause a server error while reading deployed archives.

If you wish, you can specify the JDK to be used by the WebLogic servers through the property "JDK Home" on the Weblogic server registry nodes in Runtime Tab.

Forte X-Designer

When you set your help browser to XD/Help and request help you obtain a second X-Designer main window and do not obtain XDHelp.

If you still need to use XDhelp browser, in addition to the Netscape browser, your system administrator can address this by replacing the xdhelp symlink with a real link at <INSTALL-DIR>/platform/sparc-SunOS/prod/bin.

To do so, your administrator can enter the following commands at that location:

$ rm xdhelp
$ ln xdesigner xdhelp

I18N Limitation

Because Sun Linux 5.0 does not have locale-specific or localized components for viewing fonts and performing input of locale specific characters in a GUI
for locales that use multibyte and some other locales, Sun Linux 5.0 is not supported for use in other locales.

Installation

You can only use spaces in installer path names on the Windows platform.

J2EE Web Tier Development

System Requirements

 

Operating Systems, Orbs, Databases, and Version Control Systems

Note that on all platforms the recommended Netscape version is 6.2.

The following table describes Operating Systems, ORBs, databases, and version control systems supported by this release.

Platforms

The Sun ONE Studio 4 edition has been tested on the following platforms for CE and EE and we recommend you use these platforms.

*Sun ONE Studio 4, FCS edition has received limited testing for the following platforms::
  • Windows NT4, SP6 for both CE and EE editions
  • Windows 98 2nd Edition (CE only)
  • Solaris™ 8 SPARC (32-bit kernel mode)
  • Solaris™ 9 SPARC (32-bit kernel mode)

The J2EE Reference Implementation 1.3 Server is bundled with the Sun ONE Studio 4 installer.

BEA WebLogic 6.1 SP2 and 7.0 Application -- J2EE 1.3 Plus J2EE 1.3 Features has been tested with Solaris™ 8 operating environment, SPARC™ platform edition and the Windows 2000 platform.

The Sun ONE Studio 4 update 1, WebLogic Server Deployment Module is available as an NBM from the Sun ONE Studio Update Center.

NOTE:Sun ONE Studio 4 requires J2SE SDK v. 1.4.0_02 or a version no earlier than 1.3.1_01. See the information at the top of this Note.

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.

Due to a bug in JDK releases 1.4.0_02 and 1.4.1rc, an unusual number of error messages sometimes appear in the IDE console. To avoid the
problem, consider using JDK version 1.4.0.

Debugger

JPDA Debugger on Windows uses sockets for a connection between two Java virtual machines by default. It might create an attempt to contact a firewall or an Internet provider. If this problem occurs, start the Sun ONE Studio 4 IDE with a shared memory connection by using the following command:

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

J2EE RI Web Server and HTTP Monitor

How to enable the HTTP Monitor for the J2EE RI web server:

  1. Uncomment the filter setting for HTTPMonitorFilter in conf/web.xml.
  2. Restart the RI Server.

J2EE Web Tier Development

JSTL Standard taglib Replacements for FFJ tags
Sun ONE Studio 4.0 has replaced the proprietary set of custom tags with the JSP Standard Tag Library (JSTL).

This note describes the correspondences between the previous set of tags and the standard tag library. The JSTL is contained in the following .jar files. available from the Tag Library Repository: standard.jar, containing the JSTL itself, js.jar, containing the expression language interpreter, jstl.jar, containing the auxiliary interfaces required for you to integrate your custom tags, and jaxen-full.jar and saxpath.jar, containing the APIs needed for the XML tags, especially the XPath capability.

1. Jar files

The proprietary FFJ tags came in 3 jar files: ietags.jar, dbtags.jar, and tptags.jar; containing, respectively, the presentation tags, the database access tags, and the transparent persistence tags.

JSTL uses the JSP1.2 feature of allowing multiple tld files in a single jar. It provides several sets of tlds: core, which contains iteration, and conditional tags; sql, which contains the database access tags; fmt, which contains formatting tags, and xml, which contains xslt tags. There is no equivalent for transparent persistence.

2. Expression language vs runtime expression values

With the proprietary FFJ tags, the only way to get dynamic data into attribute values was to use runtime expression values (rtexpr values), also called scriptlet expressions.

With JSTL, rt expr values are available, but also there is the addition of expression language support, such as javascript or spel. Expression languages greatly simplify access to java data structures, method calls and such, without the need for scriptlet expressions. For example, you can access fields of a query row like this: 

    <c:forEach var="row" items="${query.rows}">
         <c:expr value="${row.NAME}">
    </c:forEach>

3. taglib declarations

To use tlds from JSTL, you need a taglib declaration for each tld that you are going to use. Each one has two versions, one for rt expression attribute values and one for expression language attribute values. Each one also has a recommended prefix. Here are the taglib declarations you will need for each:

Core, with expression language attribute values:
<%@taglib uri="http://java.sun.com/jstl/core" prefix="c" %>
Core, with rt expression (scriplet expression) attribute values:
<%@taglib uri="http://java.sun.com/jstl/core-rt" prefix="c" %>

Sql, expression language:
<%@taglib uri="http://java.sun.com/jstl/sql" prefix="sql" %>
sql, rt expression values:
<%@taglib uri="http://java.sun.com/jstl/sql-rt" prefix="sql" %>

Formatting, expression language:
<%@taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %>
Formatting, rt expression values:
<%@taglib uri="http://java.sun.com/jstl/fmt-rt" prefix="fmt" %>

XML, expression language:
<%@taglib uri="http://java.sun.com/jstl/xml" prefix="x" %>
XML, rt expression values:
<%@taglib uri="http://java.sun.com/jstl/xml-rt" prefix="x" %>

Sun ONE Studio 4- Standard Tag Library correspondences

Tag(s) Replacement
ietags.jar
presentation tags
(iteration and conditional) 		Use the core tld, which contains iteration (forEach and forEachToken), and conditionals. 
  iterator  over collections,
  field,
  fieldIterator
use <forEach var="varname" items="(expression that evaluates to a collection)"> for the iterator tag.

Use the expression language to access fields of varname instead of the field tag. <expr value="${varname.myField}"/>

There isn't a good equivalent for fieldIterator for accessing bean properties. 

  iterator  over JDBC ResultSets 
                     (or RowSets),
  field,
  fieldIterator
use the sql query to generate results, and then use the expression language to access the "Rows" of the results. Then forEach will iterate over the rows. Elements of the row can be accessed individually by name. For example: 
       <sql:query var="myQuery" datasource="${myDataSource}" />
       <c:forEach var="row" items="${myQuery.rows}">
         <c:expr value="${row.NAME}"/>
       </c:forEach>
The fieldIterator tag corresponds to the columns of the results, and can be used as follows: 
Getting column names:
    <c:forEach var="columnName" items="${myQuery.columnNames}">
       metaData: <c:expr value="${columnName}"/> 

    </c:forEach>

Iterating over column values:
       <sql:query var="myQuery" datasource="${myDataSource}" />
       <c:forEach var="row" items="${myQuery.rowsByIndex}">
            <c:forEach var="column" items="${row}">
                <c:out value="${column}"/>
            </c:forEach>
       </c:forEach>

  if

  choose
    when
    otherwise

  switch
    case
    default
The JSTL library has equivalent conditional tags.

Use if for if

use choose / when / otherwise for either choose / when / otherwise or switch / case/ default .

database tags
dbtags.jar
use the sql tags. 
  connection
The setDataSource tag maintains connections, and provides a jdbc data source in its variable. For example: 
    <sql:setDataSource
        var="example"
        driver="${myDbDriver}"
        url="${myDbUrl}"
	user="${u}"
	password="${pw}"
    />

  query
use <sql:query> for SELECT queries. 
updates and 
  transaction
use <sql:transaction ...> .. <sql:update ... > .. </sql:transaction> for inserts, updates, or deletes. For example: 
        <sql:transaction dataSource="${example}">

          <sql:update var="newTable" dataSource="${example}">
            create table mytable (
              nameid int primary key,
              name varchar(80)
            )
          </sql:update>
        
          <sql:update var="updateCount" dataSource="${example}">
            INSERT INTO mytable VALUES (1,'Paul Oakenfold')
          </sql:update>
          <sql:update var="updateCount" dataSource="${example}">
            INSERT INTO mytable VALUES (2,'Timo Maas')
          </sql:update>
          <sql:update var="updateCount" dataSource="${example}">
            INSERT INTO mytable VALUES (3,'Paul van Dyk')
          </sql:update>
        
        
          <sql:query var="deejays" dataSource="${example}">
            SELECT * FROM mytable
          </sql:query>
        
        </sql:transaction>

  cleanup
Not needed.

Bugs and Issues

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

Correction to GSG

EE GSG Appendix B, Table B-1 Port Usage, under Java Web Services Developer Pack UDDI Server, ports 8095 and 8089 should say $FORTE4J_HOME/jwsdp/uddi_base/conf as the directory containing the server.xml file.

General IDE Issues

Ant Support

Debugger (Java)


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

Beans

Examples

Form Editor

Forte X-Designer

When you access the Online Documentation Access for Forte X-Designer through the Help menu, the following broken links are present:

When you use Help >Viewer >Use XD/Help, Forte X-Designer gives the following message when you try to access the Help... command of the Help menu:

Failed to read file: No such file or directory

The workaround is to use Help >Viewer >Use Netscape.

Internationalization (I18N)

For Internationalization bugs, please refer to the Knowledge Base.

Installation

4739175 Description: Can't install EE in silent mode

The installer always takes soldevInstall as yes , installs Solaris™ Platform developer modules, and expects fccpath while installing ide; finally creates an install.log with the following error:

Setup.product.install, com.sun.installer.PostInstallSolDevAction, err, FCC Path not specified

Workaround: Uninstall the Solaris™ Platform developer modules, if necessary, by using the uninstaller.

JAR Packager

J2EE EJB Builder Issues

J2EE Application Assembly Issues

J2EE Reference Implementation and Web Server

J2EE Web Tier

Native Connector Tool

Available with the Solaris™ 8 operating environment, SPARC™ platform edition only; Sun ONE Studio 7, Compiler Collection (formerly Forte™ Developer 7) required.

Output Window

Program Performance Analysis Tools

Available with the Solaris™ 8 operating environment, SPARC™ platform edition only; Forte™ Developer 7 required.

The following bugs can be fixed by installing the Performance Analyzer patch, number 111705-01. The following bugs can be fixed by installing the appropriate patches to the Solaris™ 8 operating environment, SPARC™ platform edition.

Projects

Solaris Native Languages Support Problems and Incompatibilities

Available with the Solaris™ 8 operating environment, SPARC™ platform edition only; Forte™ Developer 7 required.

Sun ONE Studio 7, Compiler Collection Integration Set-Up

The Solaris Native Languages Support module provides support for mixed language development with the Java™ programming language, C programming language, C++ programming language, and Fortran programming language for the Solaris™ operating environment. To use the Solaris Native Languages Support module you must:

For more information about configuring the IDE to enable the IDE to locate the Sun ONE Studio 7, Compiler Collection, choose Help > Helpsets > Solaris Native Languages Support Help from the IDE's main window. Then expand Setting Up Your Solaris Native Languages Support Environment and click How the IDE Finds the Compilers and Tools to Use. Also see the forte_fcc man page in the install-path/man/man1 directory.

Solaris Native Languages Support Environment
External Editors

Solaris Native Languages Debugger (Solaris 8 operating environment, SPARC platform edition only)

Source Editor

Version Control System Support

Web Services

Accessing Web Services through a HTTP proxy
In order for a web service client to talk to a web service thru a HTTP proxy (for instance, thru a firewall), add the following lines in the generated client proxy class to the getNewCall method before the "return call;" line:

org.apache.soap.transport.http.SOAPHTTPConnection connection = new org.apache.soap.transport.http.SOAPHTTPConnection();
connection.setProxyHost(System.getProperty("http.proxyHost"));
connection.setProxyPort(Integer.parseInt(System.getProperty("http.proxyPort")));
call.setSOAPTransport(connection);

Now you can use the normal java HTTP proxy system properties:
-Dhttp.proxyHost & -Dhttp.proxyPort

RMI Module Configuration

The Java Web Service module creates all the necessary files for implementing and consuming web services in Java using the open standards compliant JAX-RPC technology. In accordance with these standards, some of the files generated on behalf of the user implement the interface "java.rmi.Remote". By default, the RMI module provided in the Enterprise Edition automatically detects when new files are created in the IDE that implement the "java.rmi.Remote" interface, and asks the user whether they wish to track additional properties on the file relevent to deploying the objects to an RMI server. Generally, users implementing web services will be deploying these objects only to an HTTP server or J2EE-compliant application server, so RMI service is not necessary. You should respond "No" if the RMI Module prompts them to track these properties. If you want to deactivate this detection process, they can do so by selecting

Tools-Options-Distributed Application Support-RMI Settings

and setting the Detect Remote option to false.

Errors with Existing XML Operations using Static Methods
If you have an XML operation that was created in a previous version of Sun ONE Studio, and that uses a static method, you will get a compile error because of changes made in the metadata of the XML operation and the way its code is generated.
Use the following steps to remove the method from the XML operation and then re-add it:

  1. Expand the XML operation node to display the Methods node.
  2. Expand the Methods node to display the methods for this XML operation.
  3. Right click on the static method and select Delete to remove the reference to this method.
  4. Add the method by right clicking the XML operation node and selecting Add Method. Then, select the static method and click OK.

Enabling a Sun ONE Studio 3-based Apache Soap Service with XML Operations with Complex to work in Sun ONE Studio 4

A Sun ONE Studio 3-based Apache SOAP service with XML Operations with complex types will work in Sun ONE Studio 4 only with an Apache SOAP based client. To enable it to work with a JAX-RPC based client, the user must regenerate the service in Sun ONE Studio 4 (so that the service will then be using JAX-RPC instead of Apache SOAP).

If you have built web services on Sun ONE Studio 4, there are a few manual steps required to make the application work in Sun ONE Studio 4, update 1:

  1. Refetch WSDL on the existing client. This triggers the regeneration of all required files for the Apache SOAP client.
  2. Create a new J2EE application. Add the existing service and any EJB modules that were included in the original J2EE application.
  3. Change DefaultContext to the appropriate context.
  4. Deploy and run the application or client.

4682823 Description: EJB's without a remote interface not supported.
When the method that is exposed as a web service comes from an EJB, that EJB should have a remote interface. By default only local interfaces are created when you create a new BMP or CMP EJB. When you create these EJBs using the first page of the EJB creation wizard, make sure that you create remote interfaces by selecting "Remote Interface only" or "Both Remote and Local Interfaces" in the Component Interfaces pane.

4686715, 4686818 Description: Cannot publish to external UDDI registries from the Solaris and Linux platforms.
This problem will occur after pressing the Finish button in the "Publish to UDDI" wizard (this menuitem is associated with a Web Service). After pressing Finish, you will get one of two exceptions, either SSLException: Unrecognized SSL handshake or ClassNotFoundException: com/sun/xml/registry/uddi/bindingsv2/#text.
Therefore, on the Linux platform, the IDE can only publish to the Internal UDDI Registry. However, public registries generally provide browser-based tools from which you can publish your service outside the IDE.

4686758 Description: Publishing to internal UDDI registry causes exception.
There is a known issue that intermittent exceptions occur when publishing to internal UDDI registry servers. This bug is most likely to appear when running in the Solaris operating environment using the Java 2 SDK v. 1.4.
Often when user authentication is requested and the following exception is thrown from internal UDDI registry:
com.sun.registry_server.UnknownUserException:
XMLDBUserAuth.getAccountInfo(...):
Exception: org.apache.xnode.XNodeException: XNodeStoreImpl.writeXNode(...):
Exception: org.xmldb.api.base.XMLDBException: Java Runtime Error, while
writing node 'testuser' to collection 'authinfo'
There is currently no known work around. If the error occurs, re-try the activity.

4711368 Description: I18N - UDDI: Can not get the Name and Description from external UDDI registry
Workaround:To create Web Service client for external UDDI registry, download or prepare WSDL file which describes that published service, and create the Web Service client from that WSDL file.

You can also use "Search for Service using a web browser and paste the Server Key below" option instead of searching by wizard.

4715612 Description: Internal UDDI registry cannot start in a multi-user installation on Solaris.
If the IDE is installed by root, but used by a non-root user on Solaris, starting the internal UDDI registry from IDE will throw an exception unless the superuser manually grants permissions. This can be done in a variety of ways, depending on how your security is configured. For example:

(1) login as root
(2) cd s1s4-install-directory/jwsdp
(3) chmod ug+w conf
(4) cd s1s4-install-directory/jwsdp/conf
(5) chmod ug+w server.xml

4727773 Description: Deletion of gen and binding directory corrupts web service.

4727814 Description: JAX-RPC RI can't handle 2 Address classes with the same method name in xml operations even though they exist in different packages.
Workaround: Rename the Address tag in the XML Operation.

4727168 Description: Serialization classes property doesn't allow you to Add rt.jar classes.
Workaround: mount rt.jar from the jdk

4733551 Description: Web service application built in Sun ONE Studio 4.0 cannot be deployed in Sun ONE Studio 4.1.
Workaround: Recreate the J2EE application in Sun ONE Studio 4.1.

4736401 Description: Error running web service application deployed to WebLogic Server.
User sees exception message: "[ERROR] http - -no endpoint specified".

Work Around: If you are starting the WebLogic Server (6.1 and 7.0) from the IDE, you need to add the following value to the "Startup Java Options" property for the server instance:
-Djavaplugin.enabled=true

If you are starting the server using the WebLogic startup script, you need to add the same value to the JAVA_OPTIONS variable.

4736947 Description: Runtime error with JAX-RPC web service in Sun ONE Application Server 7: (deserialization error: unexpected XML mreader state. expected: END but found: START: String_2). The problem occurs when a client tries to invoke an overloaded method and the web service was regenerated after the client was generated. The client might invoke the wrong version of the method.

Workaround: Regenerate the client after every generation of the web service. To do this, right-click the client node in the Explorer, and choose Refetch WSDL.

4739216 Description: Compatibilty: New JAX Client running old soap service get deserialization error.
When a web service client created using Sun ONE Studio 4 is re-built using Sun ONE Studio 4, update 1, if the service uses overloaded methods, this error may appear:
Modeler error: Ambiguous Operation name for overloaded method direct invocation
Workaround Refetch the WSDL.

4735451 Description: Sun ONE Application Sever: Welcome page (intermittently) fails to come up.
Workaround: Reload the browser page.

4737524 Description: No serializer is registered for (class java.lang.String,{..XMLSchema}string

4737462 Description: RuntimeException: Unable to find node named 'definitions'.
Workaround: In the WSDL, replace '.' with '_' in the binding names.

4739438 Description: Web Service Wizard is remembering last architecture entered

4733752 Description: Create Web Service from WSDL caches ejb folder intead of using current directory.
Subsequent web service EJBs are created in the original directory.

4732997 Description: Web service does not compile if package name and name of web service are the same.
Workaround: Follow standard naming conventions for packages (lowercase) and classes (mixed case).

4739216 Description: Compatibilty: New JAX Client running old soap service get deserialization error.
When a web service client created using Sun ONE Studio 4 is re-built using Sun ONE Studio 4, update 1, if the service uses overloaded methods, this error may appear:
Modeler error: Ambiguous Operation name for overloaded method direct invocation
Workaround: Refetch the WSDL.

4740290 Description: KomodoException_SOAPSerializer class generated in userspace for Webcentric apps.
This occurs with webcentric applications only.

4740030 Description: "Existing" test client not updated if change runtime property.
Workaround: Delete the client and create a new test client

4740213 Description: incorrect code is generated for complex array fields in the input elements.
XML operations do not support array inputs.

4740292 Description: Renaming web serivce does not rename SOAP URL.
Workaround: Manually update the soap rpc url after doing a rename. When you change the soap rpc url you must do a generate on the service and a refetch of the client WSDL.

4741049 Description: WS builds long SoapBuildeClass names for W2000 and hence deploy fails on Sun ONE Studio Application Server 7.
Try the following scenarios: shorten web service name and shorten the absolute path.

Accessibility

Documentation

Sun ONE Studio 4 product documentation is provided in accessible formats that are readable by assistive technologies. This includes the Sun ONE Studio 4, Forte™ X-Designer User's Guide within the product distribution, and programming guides, Getting Started Guides, and tutorials on the docs.sun.com site.

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:

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 are as follows:

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:

The Jar tool makes copies of the files and writes them to the current directory. The directory structure is reproduced according to the package structure in the archive.

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

4. Open the file ide.css in a text editor. Edit the file to your preferences and save the file.

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:

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.

Removal of Features

With the Sun ONE Studio 4 release,  three features that were previously available in prior versions of Sun ONE Studio 4 (formerly Forte for Java) have been removed. Those features are Forte Code Management Software, Transparent Persistence, and Forte ESP.

These features will continue to be available as part of  Forte for Java, release 3.0 until December 31, 2002.  Sun will not EOL  (End of Life) Forte for Java, release 3.0 before the end of 2002.

Many Sun ONE Studio  Framework Extension Partner offerings as well as new technologies developed in Sun ONE Studio 4 are available as migrations paths for users of these features. For your reference, the Sun Microsystems General EOL Support Statement follows.
 

Sun General EOL Support Statement

Support is available for EOL versions of the Sun ONE software products for five years from the last ship date, as follows:

Forte TeamWare Options


TeamWare is based on the SCCS (Source Code Control System) model. Most code management tools are either based on SCCS or have migration tools to import SCCS data; the generic VCS module in Sun ONE Studio 4 can import SCCS data.
Additionally, Sun has contacted Merant and Rational and these companies can work with TeamWare users to transition their code to their solutions.

Transparent Persistence Options

The JDBC tools in Sun ONE Studio 4 will provide the technology for database connections. 

Thought, Inc. will also work with Sun ONE Studio 4 users on their O/R Mapping needs if JDBC is not sufficient.

Forte ESP Options

Forte ESP users should migrate to a standards based solution for Web Services. Sun's release of Sun ONE Studio 4 offers these standards
based solutions.  Additionally there are many partners doing work in the Web Services arena that could provide assistance.

For a full listing of Sun ONE Studio Partner offerings, see: 

http://forte.sun.com/ffj/partnerprograms/partnerlist.html

Other Documentation

Books

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

Community Edition

Enterprise Edition

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

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.

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. SunSolve account holders can access Native Connector Tool, Forte X-Designer, Performance Analyzer, and Solaris Native Languages Support bug information through SunSolve.

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 modules 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 use 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 choose 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/ffj/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.

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

VIM REFERENCE MANUAL, by Bram Moolenaar

SUMMARY. Vim is Charityware. You can use and copy it as much as you like, but you are encouraged to make a donation to orphans in Uganda. See |iccf| below.

DETAILS. There are no restrictions on distributing an unmodified copy of Vim. Parts of Vim may also be distributed, but this text must always be included. You are allowed to include executables that you made from the unmodified Vim sources, your own usage examples and Vim scripts.

If you distribute a modified version of Vim, you are encouraged to send the maintainer a copy, including the source code. Or make it available to the maintainer through ftp; let him know where it can be found. If the number of changes is small (e.g., a modified Makefile) e-mailing the diffs will do. When the maintainer asks for it (in any way) you must make your changes, including source code, available to him. The e-mail address to be used is <maintainer@vim.org>

The maintainer reserves the right to include any changes in the official version of Vim. This is negotiable. You are not allowed to distribute a modified version of Vim when you are not willing to make the source code available to the maintainer.

The current maintainer is Bram Moolenaar <Bram@vim.org>. If this changes, it will be announced in appropriate places (most likely www.vim.org and comp.editors). When it is completely impossible to contact the maintainer, the obligation to send him modified source code ceases. It is not allowed to remove these restrictions from the distribution of the Vim sources or parts of it. These restrictions may also be used for previous Vim releases instead of the text that was included with it. The Open Publication License applies to the Vim documentation, see |manual-copyright|.

*iccf* *ICCF*

If you are happy with Vim, please express that by reading the rest of this file. You can also have a look here (these are mirrors):

http://www.vim.org/iccf/

http://iccf-holland.org/

*kcc*

Kibaale Children's Centre (KCC) is located in Kibaale, a small town in the south of Uganda, near Tanzania, in East Africa. The area is known as Rakai District. The population is mostly farmers. Although people are poor, there is enough food. But this district is suffering from AIDS more than any other part of the world. Some say that it started there. Estimations are that 10 to 30% of the Ugandans are infected with HIV. Because parents die, there are many orphans. In this district about 60.000 children have lost one or both parents, out of a population of 350.000. And this is still continuing.

The children need a lot of help. The KCC is working hard to provide the needy with food, medical care and education. Food and medical care to keep them healthy now, and education so that they can take care of themselves in the future. KCC works on a Christian base, but help is given to children of any religion.

The key to solving the problems in this area is education. This has been neglected in the past years with president Idi Amin and the following civil wars. Now that the government is stable again, the children and parents have to learn how to take care of themselves and how to avoid infections. There is also help for people who are ill and hungry, but the primary goal is to prevent people from getting ill and to teach them how to grow healthy food. Most of the orphans are living in an extended family. An uncle or older sister is taking care of them. Because these families are big and the income (if any) is low, a child is lucky if it gets healthy food. Clothes, medical care and schooling is beyond its reach. To help these needy children, a sponsorship program was put into place. A child can be financially adopted. For a few dollars a month KCC sees to it that the child gets indispensable items, is healthy, goes to school and KCC takes care of anything else that needs to be done for the child and the family that supports it. Besides helping the child directly, the environment where the child grows up needs to be improved. KCC helps schools to improve their teaching methods. There is a demonstration school at the centre and teacher trainings are given. Health workers are being trained, hygiene education is carried out and households are stimulated to build a proper latrine. I helped setting up a production site for cement slabs. These are used to build a good latrine. They are sold below cost price.

There is a small clinic at the project, which provides children and their family with medical help. When needed, transport to a hospital is offered. Immunization programs are carried out and help is provided when an epidemic is breaking out (measles and cholera have been a problem). Summer 1994 to summer 1995 I spent a whole year at the centre, working as a volunteer. I have helped to expand the centre and worked in the area of water ,and sanitation. I learned that the help that the KCC provides really helps. Now that I'm back in Holland, I would like to continue supporting KCC. To do this I'm raising funds and organizing the sponsorship program. Please consider one of these possibilities:

1. Sponsor a child: $15 a month. (Holland: fl 27,50)

2. Sponsor a child and the improvement of its environment: $25 a month (Holland: fl 45)

3. Sponsor the health team: Any amount a month or quarter

4. A one-time donation

Compared with other organizations that do child sponsorship the amounts are very low. This is because the money goes directly to the centre. Less than 5% is used for administration. This is possible because this is a small organization that works with volunteers. If you would like to sponsor a child, you should have the intention to do this for at least one year.

How do you know that the money will be spent right? First of all you have my personal guarantee as the author of Vim. I trust the people that are working at the centre, I know them personally. Further more, the centre is co-sponsored and inspected by World Vision, Save the Children Fund and International Child Care Fund. The centre is visited at least once a year to check the progress (at our own cost). I have visited the centre myself in 1996, 1998 and 2000. If you have any further questions, send me e-mail: <Bram@vim.org>. The address of the centre is: Kibaale Childrens Centre, p.o. Box 1658, Masaka, Uganda, East Africa

Sending money:

USA and Canada: Contact Kibaale Children's Fund (KCF) in Surrey, Canada. They take care of the Canadian sponsors for the children in Kibaale. You can send them a one time donation directly. Please send me a note so that know what has been donated because of Vim. Ask KCF for information about sponsorship. Kibaale Children's Fund c/o Pacific Academy, 10238-168 Street, Surrey, B.C. V4N 1Z4 Canada Phone: 604-581-5353

If you make a donation to Kibaale Children's Fund (KCF) you will receive a tax receipt which can be submitted with your tax return (under the Free Trade Agreement tax receipts issued by an organization registered in Canada are fully accepted by the IRS in the USA). Holland: Transfer to the account of "Stichting ICCF Holland" in Venlo. This will allow for tax deduction (if you live in Holland)! Postbank, nr. 4548774

Germany: We are currently working on a way to make donations that allow for a tax return. Check the ICCF web site for the latest information: http://iccf-holland.org/donate.html

World: Use a postal money order. That should be possible from any country, mostly from the post office. Use this name (which is in my passport): "Abraham Moolenaar". Use Euro for the currency if possible.

Europe: Use a bank transfer if possible. Your bank should have a form that you can use for this. See "Others" below for the swift code and IBAN number. Until December 2001 a eurocheque can still be used, which is preferred, because it has no costs for us. You must write the amount in Dutch Guilders (DFL). Send it to the address below. Any other method should work. Ask for information about sponsorship.

Credit Card: You can use PayPal to send money with a Credit card. This is the most widely used Internet based payment system. It's really simple to use. Use this link to find more info: https://www.paypal.com/affil/pal=Bram%40moolenaar.net. The e-mail address for sending the money to is: Bram@iccf-holland.org. Unfortunately, the extra cost is a bit high. The other methods are preferred.

Others: Transfer to one of these accounts if possible: Postbank, account 4548774,Swift code: INGB NL 2A, IBAN: NL47 PSTB 0004 5487 74, under the name "stichting ICCF Holland", Venlo

If that doesn't work: Rabobank Venlo, account 3765.05.117, Swift code: RABO NL 2U under the name "Bram Moolenaar", Venlo. Otherwise, send a cheque in US dollars to the above address. Minimal amount: $70 (my bank does not accept smaller amounts for foreign cheques, sorry)

Address to send cheques to: stichting ICCF Holland,Bram Moolenaar,Clematisstraat 30,5925 BE Venlo, The Netherlands

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

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