Advice to "thick as a brick" in Java-files tuning, please

Question

I have just now installed on the NT ojsp, jswdk, jsdk, Apache
and tried OJSP "White papers"'s example with <%@ page
import="mybeans.NameBean" %>. I have compiled "NameBean.java"
to "NameBean.class" and put it into the same directory where a
jsp-coded page saved. But I got:
Request URI: /Usebean.jsp
Exception:
oracle.jsp.parse.JspParseException: Line #2, Error: Unable to
find class for bean 'pageBean' defined by tag with class:
mybeans.NameBean
Could somebody advice me where I can find descriptions of
Javabeans, classes and import USING and TUNING on the filesystem?
And where should I put NameBean.class to run "Usebean.jsp"?
null

Answer 1

GF (guest) wrote:
: Oracle Java Technical Team wrote:
: : GF (guest) wrote:
: : : I have just now installed on the NT ojsp, jswdk, jsdk,
: Apache
: : : and tried OJSP "White papers"'s example with <%@ page
: : : import="mybeans.NameBean" %>. I have
: compiled "NameBean.java"
: : : to "NameBean.class" and put it into the same directory
: where a
: : : jsp-coded page saved. But I got:
: : : Request URI: /Usebean.jsp
: : : Exception:
: : : oracle.jsp.parse.JspParseException: Line #2, Error: Unable
: to
: : : find class for bean 'pageBean' defined by tag with class:
: : : mybeans.NameBean
: : : Could somebody advice me where I can find descriptions of
: : : Javabeans, classes and import USING and TUNING on the
: : filesystem?
: : : And where should I put NameBean.class to run "Usebean.jsp"?
: : Your download also contains documentation; "Oracle JSP
: Developers
: : Guide". Read the first couple of chapters including the one
: : concerning JSP applications.
: : The short answer to you question is you put the bean in the
: : WEB-INF/classes directory of your application. If you have
no
: : application then the servers document root is considered the
: : application (root).
: : An alternative is to put the class where ever you want and
: : configure either OJSP or the underlying servers classpath to
: : include this location.
: ===========================================================
: Thanks a lot for the previous one.
: There is other point of question.
: I successfully tested "white paper"'s JDBCQuery.jsp but didn't
: the SQLJQuery.sqljsp.
: Could you help again? Where is the reason of Exception?
: So,
: It seems that I have all required records and over in
: the "jserv.properties" file:
: "wrapper.classpath=C:\Program Files\Apache Group\Apache
: JServ\ApacheJServ.jar
: wrapper.classpath=d:\Jsdk2.0\lib\jsdk.jar
: wrapper.classpath=d:\jswdk-1.0.1\lib\servlet.jar
: wrapper.classpath=d:\ojsp\lib\ojsp.jar
: wrapper.classpath=d:\ojsp\lib\xmlparserv2.jar
: wrapper.classpath=d:\jswdk-1.0.1\lib\jspengine.jar
: wrapper.classpath=d:\jswdk-1.0.1\lib\xml.jar
: wrapper.classpath=d:\orant\jdbc\lib\classes111.zip
: wrapper.classpath=d:\ojsp\lib\translator.zip"
: But running of http://nt-tst/SQLJQuery.sqljsp gives on the
: Browser's page:
: "JSP Error
: Request URI: /SQLJQuery.sqljsp
: Exception:
: oracle.jsp.provider.JspCompileException:
: Errors compiling: c:\jsps\\SQLJQuery.java
: Line # Error "
: and in "jserv.log":
: [26/11/1999 14:52:02:280 GMT+03:00] JspServlet: unable to
: dispatch to requested page:Exception:
: oracle.jsp.provider.JspCompileException: <H3>Errors compiling:
: c:\jsps\\SQLJQuery.java</H3>...
: I checked SQLJQuery.sqlj file in the Jdeveloper 2.0
environment.
: There were red painted items:
: "import oracle.jsp.runtime.*;
: import javax.servlet.jsp.*;
: import oracle.sqlj.runtime.Oracle;
: oracle.jsp.runtime.HttpJsp
: hireDate
: JspFactory
: PageContext
: JspWriter".
The error is being reported during page compile. Unfortunately,
the compile problem isn't being reported. It is possible that
the code is confused and the page compiled correctly -- check to
see if SQLJQuery.class exists.
Another thing to check is what files were generate? Does
SQLJQuery.java exist? If not an error occurred when the SQLJ
translator was run. If SQLJQuery.java exists but SQLJQuery.class
doesn't then the error occurred during Java compilation. My
advice in either case is to manually translate/compile thelast
generated file to determine the actual compile/translation error.
I.e. either SQLJQuery.sqlj via the SQLJ translator
or SQLJQuery.java via the Java compiler
null