iPlanetTM Application Server Third Party Integration

Release Notes

Integration with VisualCaféTM Version 1.0

Updated November 27, 2000

Contents

What's New

The iPlanetTM Application Server Third Party Tools Integration solution enables you to develop iPlanet Application Server applications with VisualCafé Enterprise Edition Version 4.0, or WebGain Studio Standard Edition Version 4.0.

The iPlanet Third Party Integration solution enables you to:

Issues and Limitations

The following issues have been addressed in this release and a workaround is provided.

ID Summary
402294 The Cancel button on the progress panel that appears while delivering an EJB to the server has no effect.
Workaround: Wait a few minutes and it will be active.
404321 In CMP implementation, there are problems when the primary key class is used; wherein a primary key class is created with a primary key field.
Workaround: Use the patch provided; see the patchreadme.html file located on your CD.
439729 Inner classes do not work correctly in servlets or EJBs in the iPlanet Application Server.
Workaround: Do not use inner classes.
461009 It is not possible to create a WAR or EJB JAR file without deploying to a server.
Workaround: Deploy or execute in the iPlanet Application Server, then use the WAR or JAR file from the Project area.
468749 Servlet name and package name consistency problems.
Workaround: Once a servlet is registered with the application server and a GUID is generated the registered name is not changable. You can find the registered name by using kregedit to look at the server configuration and compare the GUID with the GUID from the iPlanet Application Server tab of the Configure Servlets dialog. The registered name is the name that must be used in the Configure iPlanet Web Application dialog and Welcome Files fields. This ensures that the execution opens the browser to the right location. If the names don't match you will see a GX Error (GX2GX).
477369 Cache not refreshed when changing the descriptor in a Web Application or EJB.
Workaround: If you change the desciptor in a Web Application or EJB and redeploy you must restart the kjs process. This is done for you if you use the Execute or Run in Debugger commands, but not if you use the Execute in iPlanet Server command. Changes to your code do not require a restart.
512414 When creating a new Web Application, the project title is untitled even though a project name is specified.
Workaround: Save or close the project and reopen it, the title now appears correctly.
514431 Problem accessing an EJB from another EJB or web application.
Workaround: Modify the server CLASSPATH using the regedit. See Part 5 of the Third Party Integration with VisualCafé tutorial for specific instructions. This is not needed for the Execute or Run in Debugger commands because the CLASSPATH passed to the JVM is updated with any referenced EJBs.
518116 If the directory server is not up on the local machine, VisualCafé does not start up correctly.
Workaround: Make sure the directory server is running and then restart VisualCafé.
518157 Null pointer exception is encountered while creating a Web Application package.
Workaround: You must specify a package name for your web application.
523034 Execute and run in the debugger stops working.
Workaround:
  1. Move the iplanet_wg.jar file from the <vcafe>/bin/components directory and place it in a temporary directory.
  2. Launch VisualCafé.
  3. Exit VisualCafé.
  4. Place the iplanet_wg.jar file back in the <vcafe>/bin/components directory.
The debugger should work properly now.
None Problems using JDBC for CMP mapping.
Workaround: Add the driver to the sc.ini file.

Troubleshooting Tips

Fine tuning of descriptors: Use the iPlanet Deployment Tool for access to more descriptor fields such as security settings.

GX error: Encountered when the servlet is not on the server or is referenced using the wrong name. Check the names and verify that it was actually deployed.

Bind error: Encountered if a servlet is accessed when kjs is not ready or not running. Reboot your application server to eliminate this problem.

More server-side feedback: Instead of starting the server as a service, use the command kas -debug. This runs the server in a command window where more detailed error messages are displayed allowing you to verify the activity of the server. The stop server menus will not be able to stop the server if you start it this way.

More information: To get more messages from VisualCafé Enterprise Edition, add JAVA_COMPCMD=STACKTRACE at the end of your sc.ini file.

Reporting Problems

Online and telephone Technical support can be found at: http://iplanet.com/support/online/

For More Information

For all iPlanet Third Party Integration documentation, including updated release notes, refer to: http://docs.iplanet.com/docs/manuals/ide/

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.