Reloading JavaBeans in a JSP without re-starting the server

Answer 1

          The JSP will get recompiled but the bean is already sucked in by the server. Even if you break the session by doing reqest.getSession.invalidate() at the end of your JSP - it still persists. Even try removing your bean class and you will still see that the page is working. That proves it doesn't use .class anymore. However when you touch your .jsp at this time and try to re-display it in the browser you will get compilation error because .class cannot be imported. When you put a new class and repeat it, it compiles against that new class but still executes with the old one. Until you restart the WebLogic server...
          "Carl Ansley" <[email protected]> wrote:
          >
          >I've found that you need to "touch" the JSP that references the javabean,
          >i.e. to force the server to recompile. Plus you'll need to create a new
          >session if the bean has session scope.
          >
          >"Eli Tucker" <[email protected]> wrote in message
          >news:8hom7d$puk$[email protected]..
          >> Hello.
          >>
          >> I have a JSP page that uses a simple JavaBean (not an EJB). If I modify
          >the
          >> bean, the server appears to use the old version of it. The only way I've
          >> found to force the server to use the latest version is to re-start the
          >> server.
          >>
          >> Is there a way to use the latest class without re-starting the server?
          >I'm
          >> using WebLogic Server 5.1.0 on an NT system.
          >>
          >> Thanks,
          >> Eli
          >
          >
          >