Seems like this is a perfect situation to use the JSP and
tags. Or is that answer just too easy?
- Dave F.
"McCann, Charles (Atlanta)" wrote:
> Does JSP provide a mechanism for controlling what will and won't be
> displayed on a page?
>
> For example (from a JSP page):
> A bean value is che
I'm seeing a similar problem. In my case, I'm using the 0.92 reference implementation
and trying to set a boolean property with SETFROMREQUEST. It does not work. My
setter and getter methods are named correctly and there are no exceptions or other
errors. I could try adding a BeanInfo class
I've seen the same thing. I'm using an ugly work-around where I actually do the test
on the string "null". Of course, this only works on String objects and I have to
initialize to the string "null" in my beans instead of using the "null" keyword.
A bigger problem to us has been that JRun does
Chris, I couldn't agree more! We were absolutely thrilled with the way we could use
the simple tags from the 0.92 spec. It was perfect for our business model where we
provide JavaBeans and a standard set of JSP pages to our customers. They will want
customize the pages for their needs, and s
We're running IIS 4.0 on NT and using JRun 2.3 as our JSP/servlet engine. I have a
set of JSP's that I'm using in a "Model 1" configuration. I need to restrict access
to these JSP's, so my thinking was just to use the authentication control options in
the IIS web server.
Unfortunately, no ma
These sites, and some of the others mentioned, appear to be "BroadVision" sites rather
than JSP sites (see Mark Kolb's post). I notice that many of the URL's refer to
"BV_SessionID". That seems to be a dead giveaway. Remember - the ".jsp" extension
doesn't necessarily mean it is JavaServer P
I'm looking for more clever solutions.
My problem also occurs when I use RequestDispatcher.forward() to forward to a JSP page
(see original posting below). In my case, the JSP page contains relative links like
and they are not being found. The JSP is not in the
server's root directory, but
#x27;t know how well supported it is by the various browsers.
-- Scott
Dave Ferguson wrote:
> I'm looking for more clever solutions.
>
> My problem also occurs when I use RequestDispatcher.forward() to forward to a JSP
>page (see original posting below). In my case, the JSP page
I'm not sure if this is the problem, but I assume you know that iPlanet 4.0 only
supports the JSP 0.92 spec. We are using iPlanet 4.0 with ServletExec 2.2 for JSP 1.0
support. There is supposed to be a release of iPlanet 4.1 soon which supports JSP 1.1
and Servlet 2.2.
Dave F.
> Shashank D
NES 4 (iPlanet) only supports JSP 0.92 spec. There is a new version (4.1) available
that supports JSP 1.1 and Servlet 2.2. The URL is
http://www.iplanet.com/downloads/download/index.html. I have not tested it, so don't
know how well it works.
Dave F.
Santhosh Kolathur wrote:
> Hi
>
> I'm
We used JRun 2.3 a while back during development. We didn't get anything as bad as a
javaw.exe crash, but did find too many bugs for our liking. We tried ServletExec 2.2
and have been very pleased. The browser-based administration is easier to use and we
found the tech support more responsiv
Anil,
Thanks for your efforts in moderating this list. I've been on it since Feb. 1999 and
believe that the quality has deteriorated a lot since then. I also agree with the
guys who complained about the bouncing mail. Every message you post to this list
results in about 10 "undeliverable" me
Since all request are coming from the same browser instance (even if different
windows), there is only one session as far as the servlet knows. There's no way
around that. Of course, using two different browsers would keep the sessions distinct
(i.e., user opens IE, then opens Netscape).
The
Roger Kjensrud wrote:
> Hello,
>
> I'm new to the JSP and JAVA world, and I'm trying to gain an =
> understanding of how different clients are handled, and potential =
> dangers of having several simultaneous requests.
>
> I get the concept of JSPs compiled into a servlet, and that they can =
> h
14 matches
Mail list logo