Known Issues for Web Application Development

Error displays when selecting a leaf node in the WorkSpace Navigator view.

If you open a Web Application Development (WAD) project, select WebContent > WEB-INF , and right-click web.xml, errors display in the Error Log view, including this message: Plug-in 'com.sybase.stf.jmt.workbench' contributed an invalid Menu Extension (Path: 'common.new.menu' is invalid): com.sybase.stf.jmt.workbench.wadFacesConfigWizardAction

Workaround: None. You can ignore the message.

Cannot deploy JSF project to EAServer 5.3.

If a JSF project works when you create it, but reports errors when you deploy it to EAServer, this typically indicates that the JDK used to create the project is different than the JDK used to run the project. For example, if you create a session EJB using JDK 1.5.x in Eclipse, and then attempt to deploy it to an EAServer that is started using JDK 1.4.x, an error occurs.

Workaround: If you are creating a J2EE component in Eclipse that will be deployed to EAServer, make sure the JDK in Eclipse is the same version running in the target EAServer. In Eclipse, choose the JDK using Window > Preferences > Java > Installed JREs. Also, you can update a project build path using Project > Properties > Java Build Path. See the EAServer help for instructions on how to start EAServer with JDK 1.4.x or JDK 1.5.x. Sybase recommends that you use JDK 1.5 with Sybase WorkSpace 2.0.

Error 404 when starting a JSP page on EAServer.

If EAServer has not completed its start up process before you start a JSP page, error 404 displays instead of the JSP page. This can happen even if you have seen "Server Started" on the console, and the server state in "Servers" view changed to "Started."

Workaround: When you see the following messages on the console, restart the JSP page:

The Management Console can be accessed at http://:8000/console

The Management Console can be accessed at http://:8001/console

If you import a DataWindow library (.pbl file) that was created in a previous version of WorkSpace (or another Sybase product) into a WorkSpace 2.0 WAD project, you may have issues using the DataWindows in a Web page. For example, after dropping a DataWindow into your Web page, you may see "Error loading: dw name."

Workaround: Manually migrate the DataWindow Library to the current version. Right-click the library name, and select Migrate.

Cannot invoke an Axis-based service in EAServer 5.x.

After deploying an EAServer Web services package profile to EAServer 5.X, you cannot invoke it because it cannot see the service from Enterprise Explorer. You see an error message in the Eclipse/.log that starts with:

!ENTRY com.sybase.stf.servers.wst 4 10001 2007-06-18 15:56:06.029

!MESSAGE plugin.internal_error

!STACK 0

WSTAdminException: java.lang.NullPointerException:java.lang.NullPointerException

Workaround: Restart WorkSpace JDK 1.5 (this means you must use EAServer 5.5, not EAServer 5.3, which does not support JDK 1.5). See the EAServer help for instructions. Sybase recommends JDK 1.5 with Sybase WorkSpace 2.0.