Hi Sam,
I think this is an kind of implementation issue, or maybe because of the
different understanding of the PageBean. I'm using Sun's reference
implementation, and it only permits me to pass the same bean to the same
request once, the second time when you try to repass the same bean, it will
throw out an "IllegalStateException", so let alone being visible.
Cheers.
Lihua Sun
-----Original Message-----
From: EXT "Weiner, Sam [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 21, 1999 10:00 PM
To: [EMAIL PROTECTED]
Subject: Re: WebSphere problems detecting new servlets
I haven't had any problems with Websphere (2.0.2) detecting changes in
servlets, even ones that are in the "Reloadable Servlet Classpath". I have
noticed that Websphere seems to use timestamps to detect updates in JSP
pages.
What I haven't been able to do is get a Bean to reload. I instantiate the
Bean in a Servlet, pass it to a JSP page, and display it (scope="request")
successfully, but subsequent changes made to the Bean aren't visible until
the server is restarted. Does anyone know what I'm doing wrong?
Thanks in advance,
Sam Weiner
----------
From: Rob Jago[SMTP:[EMAIL PROTECTED]]
Reply To: [EMAIL PROTECTED]
Sent: Tuesday, April 20, 1999 9:32 AM
To: [EMAIL PROTECTED]
Subject: Re: WebSphere problems detecting new servlets
make sure the time stamps on your server are the same as on your
workstation. WebSphere checks the timestamp of the code when
checking to
see if it should grab the latest and newest version.
also, make sure the servlet is in the servlets directory. in
websphere 1.0
you can specify different directories where to place things but the
only
real directory that is "reloadable" to websphere 1.0 is the servlets
directory. therefore , if you placed the servlet in a directory
other than
the servlets directory the only way of getting your servlet to
reload is via
recyclying webpshere. In websphere 2.0 this implementation has
changed
hope this helps
Rob Jago
Programmer Analyst
Ottawa
> -----Original Message-----
> From: Kirkdorffer, Daniel [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 16, 1999 1:55 PM
> To: [EMAIL PROTECTED]
> Subject: WebSphere problems detecting new servlets
>
> Has anyone experienced problems with WebSphere 1.0 where it
doesn't seem
> to
> detect that you've updated a servlet, and therefore fails to use
it?
>
> I'm banging my head against the wall trying to figure out why
sometimes it
> picks it up and why other times (more often than not now) it
doesn't pick
> up
> the changes and continues to run the older version. I shouldn't
have to
> restart the web server, but it appears that I do now.
>
> This problems seems to have started to happen in the past few
weeks for
> me.
> The servlet path is defined in the servlets.properties file. But
the
> servlets don't seem to be reloading as they should.
>
> Any ideas?
>
> Dan
> --
> Daniel Kirkdorffer
> Sr. Consultant, Syllogistics LLC
> Web: http://www.syllogistics.com/
> Email: [EMAIL PROTECTED]
>
>
==========================================================================
> =
> 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".
===========================================================================
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".
