Where does WebLogic search the compiled JSP files?

Question

Hi,
          I have done several tests with WebLogic and JSP files.
          I have observed that when the JSP is requested the first time it is
          compiled and saved in c:\weblogic\myserver\classfiles\jsp_servlet
          If I request the same JSP again, it won't be compiled again. I
          suppoussed it was because the compiled JSP (*.class) was created. Then I
          deleted the compiled JSP and when I call the JSP again it run perfectly
          without a new compilation.
          Where are really those JSPs?
          Thanks in advance,
          Chemi.
          

Answer 1

          Chemi wrote:
          >
          > Thanks Mathieu,
          >
          > just one thing more. Can I disable this feature just to measure the advantage
          > of WebLogic against other AppSrv which haven't it?
          >
          No clue. But as somebody else has said, touching the jsp files WILL
          force recompilation if you gor your JSP engine setting correct (check
          seconds set to zero).
          My guess is that all AppSrv would have this feature, because it comes
          for free with usual classloaders, i.e. it would be MORE trouble to not
          have this feature than to have it.
          Mathieu
          > Thanks in advance,
          >
          > Chemi.
          >
          > Mathieu Gervais wrote:
          >
          > > Chemi wrote:
          > > >
          > > > Hi,
          > > >
          > > > I have done several tests with WebLogic and JSP files.
          > > >
          > > > I have observed that when the JSP is requested the first time it is
          > > > compiled and saved in c:\weblogic\myserver\classfiles\jsp_servlet
          > > >
          > > > If I request the same JSP again, it won't be compiled again. I
          > > > suppoussed it was because the compiled JSP (*.class) was created. Then I
          > > > deleted the compiled JSP and when I call the JSP again it run perfectly
          > > > without a new compilation.
          > >
          > > it's because it is loaded in memory. It doesn't need the .class file
          > > anymore. Depending on your jsp engine settings, changing the JSP file
          > > will force a new recompilation, but changing the .class doesn't affect
          > > anything, since the class is loaded by the weblogic classsloader in
          > > memory, and accessed from here at future requests.
          > >
          > > Mathieu
          > >
          > > >
          > > > Where are really those JSPs?
          > > >
          > > > Thanks in advance,
          > > >
          > > > Chemi.