iPlanet Application Builder 6.0 Release Notes

Contents

Getting Help
Database Issues
Server Issues
IP Address Issues
Deployment Issues
Enterprise Java Beans Issues
User Interface Issues
Documentation Errata

Getting Help

Please use the Help -> Send Comments dialog box to send suggestions or comments about this release to the development team. Your comments will be read by the development team, but due to the large number of comments, the development team is unable to reply to each comment individually.

For product information such as an FAQ list, upgrades, or patches, please visit our website at http://docs/iplanet.com/docs/manuals

Database Issues

Problem: Different Source ID (SID) name than data source name.

Workaround: The Source ID (SID) name must be the same as your data source name for cross-platform compatibility. This is especially significant for databases such as Oracle that have different names.

For example: The tutorial source name cdx must be the same as the SID on your Solaris system.

Server Issues

Problem: On Solaris, the tcp_ip_abort_interval wait time is set to 4-8 minutes by default. This sets the start/stop of the server. Starting and stopping the server will not start the server for you.

Workaround: Change the default time interval to a desired specified time to avoid this default wait time setting.

Problem: During a test project sequence, manually stoping the web server from the services doesn't work.

Workaround: The Application Builder automatically stops/starts the web server during a test project sequence. To avoid this problem, do not manually stop the web server from the services.

On Solaris, during a test project sequence, it takes 2-3 minutes for the browser to launch and access the web server.

Deployment Issues

Problem: During the deployment process, the deployer locates your HTML files under the iAS root directory.

Workaround: To access your HTML page, you must:

  1. Copy the HTML files to the webroot directory on the deployed machine.

    For example: http://foo.bar.com/bar/index.html

  2. Make sure the links in your file work properly.

Another workaround is to:

  1. Leave the HTML files as they are.
  2. Change the URL pointer to http://foo.bar.com/NasApp/bar/index.html
  3. Make sure the URLs in your file are still pointing to the correct files.

Problem: During local deployment from within the Application Builder, only the KXS and KJS engines are started because they are the only engines necessary for testing.

Workaround: Always start the Application Server from the services.

  1. Start the Application Server from the services.
  2. Choose Deploy from within the Application builder (for local deployment).

    Local deployment overwrites your current classes.

Problem: When deploying on a Solaris machine with a module name in lower case in the registry, there is a problem with the event of the JSP handling a servlet request.

For example, if the Project on the local machine is called HelloWorld when deployed it gets converted to helloworld.

Therefore, If you have a JSP called foo.jsp on the deployed machine, when the JSP is called up, the KJS looks for helloworld/foo.jsp, which is not present.

Workaround: If your target server is a Solaris machine, use lower case names for project names.

IP Address Issues

Problem: Changing the IP Address option is not fully implemented.

Workaround: To change the IP Address:

  1. Enter the desired IP Address from within the Application Builder.
  2. Change all the IP addresses for the servers; including: the Directory Server, the Administration Server, the Web Server, and the IP Addresses of the engines such as KXS, KJS, KCS, and KAS.

Enterprise Java Beans Issues

Problem: The EJB wizard does not display some information such as the Isolation Level, Run as Mode, and Transaction Attribute if there is no method permission or security role specified for the method.

Workaround: Specify the Isolation level, Run as Mode, and Transaction Attribute. If they are not specified the default values are entered into the registry, and they do not appear in the XML file.

Problem: Importing EJBs without package names is not supported due to a known problem with the EJB compiler which expects the bean classes to have package names.

Workaround: To import an EJB without a package name into the Application Builder:

  1. Import the EJB.
  2. Run the EJB compiler with GS open.
  3. Open and edit the stubs and skeleton source files.
  4. Delete the package names.
  5. Save them to a different file.

Problem: Importing EJBs that don't have helper classes packaged in the jar files is not supported.

Workaround: This issue will be resolved with a Service Pack release.

User Interface Issues

Problem: Adding XML files from the Project -> Add Files is not supported.

Workaround: The XML files are generated by the tool itself, you do not need to add XML files.

Problem: Links created in the HTML Layout Editor do not get removed if you select and delete them.

Workaround: To remove the link (<a href>) tag:

  1. Select the complete link including the preceeding space.
  2. Press Delete.

Problem: Edit -> Replace is not supported.

Workaround: This issue will be resolved with a Service Pack release.

Problem: Undo -> Paste is not enabled when copying/pasting from within the Java Source Editor.

Workaround: This issue will be resolved with a Service Pack release.

Problem: Undo -> Delete is not enabled when deleting text from within the Java Source Editor.

Workaround: This issue will be resolved with a Service Pack release.

Problem: Selecting Add Existing Files from the drop-down menu and typing in the desired filename doesn't always work.

Workaround: When typing the filename instead of selecting the desired file from the drop-down menu, you must type the entire name completely.

Problem: When undoing a create link by dragging a servlet to a page, it doesn't undo the created link.

Workaround: To undo a created link you must select Undo twice since on the stack two undo events are generated.

Problem: The Remove All Styles button does not remove all the styles.

Workaround: The Remove All Styles button removes the bold, italic, underline, and list styles. It also changes the font styles to a default font.

Problem: When a user initiates a Copy to Clipboard unexpected content may be copied to the clipboard.

Workaround: Under certain rare circumstances, unexpected content may be copied to the clipboard when the copy to clipboard command is invoked while the value filed in the Property Inspector is being edited.

Documentation Errata

The iPlanet Application Builder documentation can be found at: http://docs/iplanet.com/docs/manuals

Select the Application Builder link to access the latest documentation including the most up-to-date Release Notes.

Copyright © 2000, Sun Microsystems Inc. All rights reserved.
Copyright © 2000, Netscape Communications Corporation. All rights reserved.

Sun, Sun Microsystems, the Sun logo, Java, iPlanet, and the Sun, Java, and iPlanet-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Netscape and the Netscape N logo are registered trademarks of Netscape Communications Corporation in the U.S. and other countries. Other Netscape logos, product names, and service names are also trademarks of Netscape Communications Corporation, which may be registered to other countries.