Hi Scott,
I am replacing JRUN with Resin for a preliminary test to see if it works for
us. We use IIS as the web server, and I would opt for Resin, but we need SSL
support.
I read the instructions, but infact installed it slightly different and it
seems to work as well. Just thought I would throw this install to you incase
you didn't know. What I did is copy the iis_srun.dll to the inetpub/scripts
folder, just like the install does. Then, in IIS Control, I went to my
"default web site" properties, selected HOME directory, Configuration and
there I have the *.jsp setting. I edited it to point to the iis_srun.dll. I
then ran the SRUN.exe and low and behold, it worked. Seems easy enough. I
have seen a number of people complaining that it was so difficult to set up.
So I ask you..is there something I am missing here?
Now, the one problem I see, when I try to log in, for some reason I get a
white page. I will play with this a bit more, but with JRUN it directly
logged me in and forwarded to the right page. Is there something I need to
do to allow the JDBC.ZIP type IV driver we use for Oracle to work correctly?
Oddly enough, our enrollment page, which also uses the database worked..so I
am thinking this may not have anything to do with the database use, but
maybe the way I forward to a page. I call on a LoginServlet (right now
until I move our site to Model 2) that checks the database then does a
redirect to the page. That for some reason isn't working. Ok..just checked
again. When I try to log in, the special HttpSession object I create to
determine if one is logged in or not DOES exist, because when I log in, I
get a white page, but if I directly type in the inside page to access, it
shows up. Now, if I click around, then it gives me a white page again. Ok..I
have determined that its the login process. I call a
/common/login.jsp?command_code=1&login=loginname&password=passwordname. It
appears that this is the culprit. It goes to the JSP page, which is nothing
more than this:
<jsp:include page="/servlet/com.bm.ui.servlets.LoginServlet" />
I can most likely fix this problem by using the Model 2 approach, where all
*.do mappings go to my controller servlet (probably seen myself, Craig,
Daniel and a few others discussing this alot in the past month or so in the
JSP-INTEREST group). But I am curious as to why this might not work.
Two other things. A "complaint" so to speak..I would be interested in
knowing how to load-balance for two web servers, but I am not quite sure I
understand your docs on this task.
Secondly, the use of the dbpool stuff in the resin.conf. How can I directly
use this so that my Database.java class I wrote that maintains the
connection pools is a thing of the past?
Thanks Scott. Appreciate anything you can reply to.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
