Be sure the file is at the same directory level as the WEB-INF directory.
Be sure the file is at the same directory level as the WEB-INF directory.
<%@taglib uri="dbtags" prefix="jdbc" %>
<%@taglib uri="ietags" prefix="pr" %>
For dbtags: uri=dbtags location=dbtags.tld
For ietags: uri=ietags location=ietags.tld
<TD><pr:field name="id"/></TD>
to
<TD><pr:field name="id"> </pr:field> </TD>
For the ShopCart.jsp file, the import line (second line) should look like this:
<%@page import="java.util.*, Cart, CartLineItem" %>
For the PlaceOrder.jsp file, add the following import line after the first
line:
<%@page import="Cart, CheckOutBean" %>
The classes under the WEB-INF\lib directory are not in the CLASSPATH of the JSP compiler. Once they are in the CLASSPATH, the JSPs are compiled and the tutorial runs properly. This is a known issue with the CLASSPATH handling of third party JSP tag extensions in iPlanet Application Server.
For example, on NT add d:\iplanet\ias6\ias\APPS\modules\CDShopCart\WEB-INF\lib to the front of Java CLASSPATH in the kregedit utility.
Note: You should check the CDShopCart\WEB-INF\lib\CDclasses.jar file after deploying or executing to make sure this file is not corrupted by the Compile All or Build All function. This is a known problem with Forte.
See also | |
---|---|
Using Advanced Features
Debugging a Web Module Debugging an EJB Module |