I have been evaluating WebSphere, ServletExec, and JRun this week, and I
came across the same behavior in JRun today. I consider it a bug. Other
than that, I've found JRun easier to work with than the other two.
<RANT>
Why have the different JSP implementations been so consistently unable to
implement the spec, and all in different ways? For example, how can JRun
say that it implements the 0.92 spec when "out" is an OutputStream instead
of a PrintWriter (spec says PrintWriter). I have similar complaints about
the other JSP runners that do 0.91. I realize there's no answer to my
question, but I felt like venting.
</RANT>
Jack Humphrey
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and reference
> [mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Yavorskiy
> Sent: Thursday, April 15, 1999 2:50 PM
> To: [EMAIL PROTECTED]
> Subject: valueBound/valueUnbound
>
>
> When java bean implements HttpSessionBindingListener interface it gets
> notified when it is added and/or remove from the session
> object. That works
> fine if you add/remove objects to/from session manually.
> However, if USEBEAN
> tag is used with the LIFE-SPAN=session it seems to bound and unbound on
> every page request (in spite of "session" lifespan). Is this a
> bug in JRun,
> the servlet engine we are using, or it is supposed to work like that?
>
> Has anyone seen similar behavior?
>
> Thanks,
> Alex
>
> ================================================================
> ===========
> To unsubscribe, send email to [EMAIL PROTECTED] and include
> in the body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
