RE: [WEB400] Error compiling JSPs using Toolbox for Java

[Colin Williams <colin.williams@xxxxxxxxxxxx>]

Try

<%@ page import="com.ibm.AS400.access.*" %>

cheers
Colin.W
 
Extension   5800
Direct dial   0870 429 5800


-----Original Message-----
From: Kelly Cookson [mailto:kc62301@xxxxxxxxx] 
Sent: 27 September 2004 15:10
To: web400@xxxxxxxxxxxx
Subject: [WEB400] Error compiling JSPs using Toolbox for Java


I'm trying to run some JSPs in Tomcat 5 that use IBM
Toolbox for Java classes. I have the jt400.jar file in
my C:\Tomcat5\shared\lib directory.  I have 
C:\Tomcat5\shared\lib\jt400.jar in both my user and my
system CLASSPATH variables. (And, by the way, I have
PHP scripts that use the jt400.jar classes and run
just fine in Tomcat, so I know the jt400.jar classes
are available for use by applications in Tomcat.)  

However, when I try to open the JSP pages in a
browser, I get error messages saying the jt400.jar
packages are not found.

Any ideas how to get my JSPs to see the jt400.jar
classes?

Detailed info below...

Thanks,
Kelly

Here are the three error statements:

Generated servlet error:
C:\Tomcat5\work\Catalina\localhost\amexj\org\apache\jsp\login_jsp.java:6:
package com.ibm.AS400 does not exist
import com.ibm.AS400.access;

An error occurred at line: 2 in the jsp file: /includes/login/loginmodel.jsp
Generated servlet error:
C:\Tomcat5\work\Catalina\localhost\amexj\org\apache\jsp\login_jsp.java:297:
cannot resolve symbol
symbol  : class AS400 
location: class org.apache.jsp.login_jsp
        AS400 iSeries = new AS400(inSystem, inUser,
inPassword);

An error occurred at line: 2 in the jsp file: /includes/login/loginmodel.jsp
Generated servlet error:
C:\Tomcat5\work\Catalina\localhost\amexj\org\apache\jsp\login_jsp.java:297:
cannot resolve symbol
symbol  : class AS400 
location: class org.apache.jsp.login_jsp
        AS400 iSeries = new AS400(inSystem, inUser,
inPassword);


Here's the complete code of the scriptlet that fails
to compile. I've tried with and without the page
import directive.

<%@ page import="com.ibm.AS400.access" %>
<%
 try {
  String inSystem = "arcticsystem"; 
  AS400 iSeries = new AS400(inSystem, inUser,
inPassword);
  try {
   Boolean uservalid = iSeries.authenticate(inUser, inPassword);  
   session.setAttribute("system", inSystem);
   session.setAttribute("user", inUser);
   session.setAttribute("password", inPassword);
   out.println("<meta http-equiv=\"refresh\"
content=\"0;URL=http://localhost:8080/amexj/mainmenu.jsp\";>");
  } catch (Exception e) {
   message="User name or password not valid. Please
try again.";
  %>
  <%@ include file="loginview.jsp" %>            
  <%
  }     
 } catch (Exception e) {
  message="Unable to connect to the iSeries server.
Please contact IT.";
 %>
 <%@ include file="loginview.jsp" %>
 <%              
 }
%>



                
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today! http://vote.yahoo.com
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a
message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.