6 Replies Latest reply on May 11, 2002 3:34 AM by 3004

    JATO Vs Struts

    3004

      Hi,

      We have to recommend a framework to a client for their next project and having
      done a few JATO projects we'd like to use JATO, but they've heard alot about
      Struts. I've done a little reading up about struts but I dont see why Struts
      would be any better than JATO or JATO better than Struts for that matter.
      Having not developed any commercial using the Struts framework makes this a
      little harder for us to answer, can anyone point out a few advantages of using
      JATO over Struts or prehaps Struts over JATO.

      Thanks,

      Shawn.


      [Non-text portions of this message have been removed]


        • 1. Re: [SunONE-JATO] JATO Vs Struts
          3004


          We are also in the same process of choosing between JATO and Struts. One thing
          that I read at many a places is that the struts framework suits/supported more
          for a WebSphere Application Server (we use WAS). But one temptation to go with
          JATO is because of the COnversion tool to migrate from NetDynamics to J2EE
          (Jato Framework). But even here the conversion is so messy ie it does not
          convert any of the custom code even if it is within the standard methods.

          YEAH...so we are also in a state of confusion..

          Bobby

          Hi,

          We have to recommend a framework to a client for their next project and having
          done a few JATO projects we'd like to use JATO, but they've heard alot about
          Struts. I've done a little reading up about struts but I dont see why Struts
          would be any better than JATO or JATO better than Struts for that matter.
          Having not developed any commercial using the Struts framework makes this a
          little harder for us to answer, can anyone point out a few advantages of using
          JATO over Struts or prehaps Struts over JATO.

          Thanks,

          Shawn.


          [Non-text portions of this message have been removed]






          ---------------------------------

          • 2. Re: [SunONE-JATO] JATO Vs Struts
            3004

            Bobby,
            Some of the custom code can be auto mapped to JATO/J2EE using the RegExp
            API Mapping Tool.

            I do know that without the tool, migrating an ND project to J2EE takes
            much longer, even if you are targeting a rich framework.

            Sorry I don't have any formal Struts vs JATO analysis for you. The
            outcome tends to favor the author's "favorite" framework. A Struts
            person would say Struts is better and vice versa.

            What is needed is an unbiased third party to evaluate each on its merits
            and come up with a pros/cons list.

            I feel confident that JATO will come out the winner :)
            c


            Bobby Nair wrote:
            We are also in the same process of choosing between JATO and Struts. One thing
            that I read at many a places is that the struts framework suits/supported more
            for a WebSphere Application Server (we use WAS). But one temptation to go with
            JATO is because of the COnversion tool to migrate from NetDynamics to J2EE
            (Jato Framework). But even here the conversion is so messy ie it does not
            convert any of the custom code even if it is within the standard methods.
            >
            YEAH...so we are also in a state of confusion..

            Bobby

            Hi,

            We have to recommend a framework to a client for their next project and having
            done a few JATO projects we'd like to use JATO, but they've heard alot about
            Struts. I've done a little reading up about struts but I dont see why Struts
            would be any better than JATO or JATO better than Struts for that matter.
            Having not developed any commercial using the Struts framework makes this a
            little harder for us to answer, can anyone point out a few advantages of using
            JATO over Struts or prehaps Struts over JATO.
            >
            Thanks,

            Shawn.


            [Non-text portions of this message have been removed]






            ---------------------------------

            To download the latest version of JATO, please visit:
            http://www.sun.com/software/download/developer/5102.html

            For more information about JATO, please visit:
            http://developer.iplanet.com/tech/appserver/framework/index.jsp



            • 3. Re: [SunONE-JATO] JATO Vs Struts
              3004

              Hi Bobby,

              We have just completed our second migration from ND to iPlanet using the
              iPlanet Migration Tool and JATO. The migration tool does leave most of the
              custom code commented, but all that's required in most cases is to uncomment
              the code and implement JATO equivalent method calls. In some cases we have
              had to re-develop the ND code where there is no JATO equivalent but working
              with the JATO framework always allows you to overcome these little hurdles.

              We're pretty happy with the time taken to complete the migrations we've done
              and the amount of time it takes to get a person with no JATO knowledge to
              become a productive team member. So if you're looking to migrate from ND,
              JATO is definitely the way to go.

              Shawn.

              ----- Original Message -----
              From: "Bobby Nair" <bobby_nair@y...>
              Sent: Thursday, May 09, 2002 1:05 AM
              Subject: Re: [SunONE-JATO] JATO Vs Struts


              >
              We are also in the same process of choosing between JATO and Struts. One
              thing that I read at many a places is that the struts framework
              suits/supported more for a WebSphere Application Server (we use WAS). But
              one temptation to go with JATO is because of the COnversion tool to migrate
              from NetDynamics to J2EE (Jato Framework). But even here the conversion is
              so messy ie it does not convert any of the custom code even if it is within
              the standard methods.
              >
              YEAH...so we are also in a state of confusion..

              Bobby

              Hi,

              We have to recommend a framework to a client for their next project and
              having done a few JATO projects we'd like to use JATO, but they've heard
              alot about Struts. I've done a little reading up about struts but I dont see
              why Struts would be any better than JATO or JATO better than Struts for that
              matter. Having not developed any commercial using the Struts framework makes
              this a little harder for us to answer, can anyone point out a few
              advantages of using JATO over Struts or prehaps Struts over JATO.
              >
              Thanks,

              Shawn.


              [Non-text portions of this message have been removed]






              ---------------------------------

              To download the latest version of JATO, please visit:
              http://www.sun.com/software/download/developer/5102.html

              For more information about JATO, please visit:
              http://developer.iplanet.com/tech/appserver/framework/index.jsp



              • 4. Re: [SunONE-JATO] JATO Vs Struts
                3004


                As for JATO vs Struts
                They are both capable frameworks albeit different in significant ways.
                We tend to encourage the customer to perform their own due diligence by
                reading the JATO whitepaper and analyzing the JATO Sample application.
                The JATO white paper outlines the JATO design principles and the value
                proposition that JATO provides to enterprise developers. In general,
                JATO is a larger more feature rich framework and provides more ready
                made structure that application developers can leverage immediately.

                RE - the iMT and Migration of ND applications

                Several points thta the migrtion candidate should consider.

                1. There is an extraordinary amount of migratoin work being done
                automatically by the iMT independent of the "source code conversion" per
                se.

                * Automatic conversion of ND templates and proprietry Spider tags to
                JATO JSPs.
                * Automatic conversion of nearly ALL declaratively specified values
                in nearly every object within the ND project. (i.e. property
                values, which are not present in the ND project's source code, but
                only present in ND studio property sheets) The discovery and
                conversion of these settings ALONE should make the use of the iMT a
                no brainer.
                * Automatic MAPPING of ND events to JATO events. Since your original
                ND code is structured within the ND event flow, you will not be
                able to easily migrate that code without an analogous event model.
                JATO provides the analogous event model and the iMT automatically
                maps your original ND event code into the corresponding JATO event
                handlers. This is a highly non-trivial task and essential to
                reducing risk during migration.

                2. As previously pointed out, the code conversion is partially automated
                and the fact that the original code is "commented out" should not be
                taken to mean that its full migration is difficult.


                * Partial automated conversion of application source code does take
                place via the iMT's Regular Expression Tool
                * In many cases, the only manual adjustment required is to uncomment
                the "commented" code.
                * In ALL cases, any post iMT manual conversion effort will be only a
                fraction of the effort that would be required by a complete non-iMT
                assisted rewrite.

                3. JATO provides the events and programming idioms that ND develolpers
                and applications are familiar with.

                * In nearly all cases, JATO provides a corresponding event and/or
                programming idiom. Rewriting your application independent of JATO
                will be extremely DESIGN intensive as it will require you to either
                redesign your entire application to rely on a framework other than
                JATO, or no framework at all. That would be an extremely risky,
                design and labor intensive, and ultimately error prone endeavor.

                In short, I would only recommend a complete manual rewrite over the iMT
                if one wishes to greatly extend the migration timeframe, introduce alot
                more risk, spend alot more money and reduce the quality of the migrated
                application. Otherwise, I would use the iMT.


                Shawn Marshall wrote:
                Hi Bobby,

                We have just completed our second migration from ND to iPlanet using
                the
                iPlanet Migration Tool and JATO. The migration tool does leave most of
                the
                custom code commented, but all that's required in most cases is to
                uncomment
                the code and implement JATO equivalent method calls. In some cases we
                have
                had to re-develop the ND code where there is no JATO equivalent but
                working
                with the JATO framework always allows you to overcome these little
                hurdles.

                We're pretty happy with the time taken to complete the migrations
                we've done
                and the amount of time it takes to get a person with no JATO knowledge
                to
                become a productive team member. So if you're looking to migrate from
                ND,
                JATO is definitely the way to go.

                Shawn.

                ----- Original Message -----
                From: "Bobby Nair" <bobby_nair@y...>
                Sent: Thursday, May 09, 2002 1:05 AM
                Subject: Re: [SunONE-JATO] JATO Vs Struts

                We are also in the same process of choosing between JATO and Struts.
                One
                thing that I read at many a places is that the struts framework
                suits/supported more for a WebSphere Application Server (we use WAS).
                But
                one temptation to go with JATO is because of the COnversion tool to
                migrate
                from NetDynamics to J2EE (Jato Framework). But even here the
                conversion is
                so messy ie it does not convert any of the custom code even if it is
                within
                the standard methods.
                YEAH...so we are also in a state of confusion..

                Bobby

                Hi,

                We have to recommend a framework to a client for their next project
                and
                having done a few JATO projects we'd like to use JATO, but they've
                heard
                alot about Struts. I've done a little reading up about struts but I
                dont see
                why Struts would be any better than JATO or JATO better than Struts
                for that
                matter. Having not developed any commercial using the Struts framework
                makes
                this a little harder for us to answer, can anyone point out a few
                advantages of using JATO over Struts or prehaps Struts over JATO.
                Thanks,

                Shawn.


                [Non-text portions of this message have been removed]






                ---------------------------------

                To download the latest version of JATO, please visit:
                http://www.sun.com/software/download/developer/5102.html

                For more information about JATO, please visit:
                http://developer.iplanet.com/tech/appserver/framework/index.jsp



                >
                To download the latest version of JATO, please visit:
                http://www.sun.com/software/download/developer/5102.html

                For more information about JATO, please visit:
                http://developer.iplanet.com/tech/appserver/framework/index.jsp

                [Non-text portions of this message have been removed]


                • 5. Re: [SunONE-JATO] ND to JATO Conversion
                  3004


                  Hi,

                  I am new to JATO..so sorry if I am missing something...

                  I tried to convert a prototype of our application. A simple 2 page ND app. One
                  .spg displays a list of Departments from a database. Once a Department is
                  choosen and if you press 'Submit', A new page appears with the list of
                  employees in that Dept.

                  We then migrated this application into JATO using the mgration tool. Packaged
                  the WAR files. Then opened the WebSPhere Studio. Here we created a New Web
                  Project and then imported the WAR file into this project. Now after compiling
                  the project files when I run the First JSP page (ie the Department Selection
                  Page) which does not need any parameters and stuff..and is logically supposed
                  to be the start page the following Error appears..

                  After reading this Exception we tried to invoke it thru a servlet by doing a
                  response.sendRedirect but the same error continues to appear..
                  Error page exceptionThe server cannot use the error page specified for your
                  application to handle the Original Exception printed below. Please see the
                  Error Page Exception below for a description of the problem with the specified
                  error page.


                  Original Exception:
                  Error Message: The request context is null - this page must be accessed through
                  a servlet
                  Error Code: 500
                  Target Servlet: null
                  Error Stack:
                  javax.servlet.jsp.JspException: The request context is null - this page must be
                  accessed through a servlet
                  at
                  com.iplanet.jato.taglib.UseViewBeanTag.doStartTag(UseViewBeanTag.java:110)
                  at
                  May_00030_00037Test.ConversionSample.EmployeeList.pgDeptSelect_jsp_4._jspService\
                  (pgDeptSelect.jsp :4)
                  at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:139)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                  at
                  org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:2\
                  86)
                  at
                  org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:415)
                  at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:544)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                  at
                  com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.jav\
                  a:827)
                  at
                  com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleSer\
                  vlet.java:159)
                  at
                  com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.ja\
                  va:286)
                  at
                  com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServ\
                  let.java:106)
                  at
                  com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
                  at
                  com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager\
                  .java:1012)
                  at
                  com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.j\
                  ava:913)
                  at
                  com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAp\
                  pRequestDispatcher.java:499)
                  at
                  com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDisp\
                  atcher.java:278)
                  at
                  com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispa\
                  tcher.java:105)
                  at
                  com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:67)
                  at
                  com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java\
                  :123)
                  at
                  com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvoca\
                  tion.java:67)
                  at
                  com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestP\
                  rocessor.java:122)
                  at
                  com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.jav\
                  a:315)
                  at
                  com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:6\
                  0)
                  at
                  com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313)
                  at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242)
                  at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)




                  Error Page Exception:
                  Error Message: JSPG0113E: JSP file "C:\Program Files\IBM\Application Developer
                  Trial Edition\workspace\May07Test\webApplication\error.jsp (The system cannot
                  find the file specified)" not found
                  Error Code: 404
                  Target Servlet: JSP 1.1 Processor
                  Error Stack:
                  com.ibm.servlet.engine.webapp.WebAppErrorReport: JSPG0113E: JSP file
                  "C:\Program Files\IBM\Application Developer Trial
                  Edition\workspace\May07Test\webApplication\error.jsp (The system cannot find
                  the file specified)" not found
                  at
                  com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispatche\
                  rResponse.java:97)
                  at
                  org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:2\
                  96)
                  at
                  org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:415)
                  at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:544)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                  at
                  com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.jav\
                  a:827)
                  at
                  com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleSer\
                  vlet.java:159)
                  at
                  com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.ja\
                  va:286)
                  at
                  com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServ\
                  let.java:106)
                  at
                  com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
                  at
                  com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager\
                  .java:1012)
                  at
                  com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.j\
                  ava:913)
                  at
                  com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAp\
                  pRequestDispatcher.java:499)
                  at
                  com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDisp\
                  atcher.java:278)
                  at
                  com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.include(WebAppRequestDispa\
                  tcher.java:111)
                  at com.ibm.servlet.engine.webapp.WebApp.sendError(WebApp.java:620)
                  at com.ibm.servlet.engine.webapp.WebApp.sendError(WebApp.java:546)
                  at
                  com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:92)
                  at
                  com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java\
                  :123)
                  at
                  com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvoca\
                  tion.java:67)
                  at
                  com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestP\
                  rocessor.java:122)
                  at
                  com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.jav\
                  a:315)
                  at
                  com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:6\
                  0)
                  at
                  com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313)
                  at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242)
                  at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)





                  ---------------------------------

                  • 6. Re: [SunONE-JATO] ND to JATO Conversion
                    3004


                    Hi,

                    I am new to JATO..so sorry if I am missing something...

                    I tried to convert a prototype of our application. A simple 2 page ND app. One
                    .spg displays a list of Departments from a database. Once a Department is
                    choosen and if you press 'Submit', A new page appears with the list of
                    employees in that Dept.

                    We then migrated this application into JATO using the mgration tool. Packaged
                    the WAR files. Then opened the WebSPhere Studio. Here we created a New Web
                    Project and then imported the WAR file into this project. Now after compiling
                    the project files when I run the First JSP page (ie the Department Selection
                    Page) which does not need any parameters and stuff..and is logically supposed
                    to be the start page the following Error appears..

                    After reading this Exception we tried to invoke it thru a servlet by doing a
                    response.sendRedirect but the same error continues to appear..
                    Error page exceptionThe server cannot use the error page specified for your
                    application to handle the Original Exception printed below. Please see the
                    Error Page Exception below for a description of the problem with the specified
                    error page.


                    Original Exception:
                    Error Message: The request context is null - this page must be accessed through
                    a servlet
                    Error Code: 500
                    Target Servlet: null
                    Error Stack:
                    javax.servlet.jsp.JspException: The request context is null - this page must be
                    accessed through a servlet
                    at
                    com.iplanet.jato.taglib.UseViewBeanTag.doStartTag(UseViewBeanTag.java:110)
                    at
                    May_00030_00037Test.ConversionSample.EmployeeList.pgDeptSelect_jsp_4._jspService\
                    (pgDeptSelect.jsp :4)
                    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:139)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                    at
                    org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:2\
                    86)
                    at
                    org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:415)
                    at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:544)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                    at
                    com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.jav\
                    a:827)
                    at
                    com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleSer\
                    vlet.java:159)
                    at
                    com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.ja\
                    va:286)
                    at
                    com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServ\
                    let.java:106)
                    at
                    com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
                    at
                    com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager\
                    .java:1012)
                    at
                    com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.j\
                    ava:913)
                    at
                    com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAp\
                    pRequestDispatcher.java:499)
                    at
                    com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDisp\
                    atcher.java:278)
                    at
                    com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispa\
                    tcher.java:105)
                    at
                    com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:67)
                    at
                    com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java\
                    :123)
                    at
                    com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvoca\
                    tion.java:67)
                    at
                    com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestP\
                    rocessor.java:122)
                    at
                    com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.jav\
                    a:315)
                    at
                    com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:6\
                    0)
                    at
                    com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313)
                    at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242)
                    at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)




                    Error Page Exception:
                    Error Message: JSPG0113E: JSP file "C:\Program Files\IBM\Application Developer
                    Trial Edition\workspace\May07Test\webApplication\error.jsp (The system cannot
                    find the file specified)" not found
                    Error Code: 404
                    Target Servlet: JSP 1.1 Processor
                    Error Stack:
                    com.ibm.servlet.engine.webapp.WebAppErrorReport: JSPG0113E: JSP file
                    "C:\Program Files\IBM\Application Developer Trial
                    Edition\workspace\May07Test\webApplication\error.jsp (The system cannot find
                    the file specified)" not found
                    at
                    com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispatche\
                    rResponse.java:97)
                    at
                    org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:2\
                    96)
                    at
                    org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:415)
                    at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:544)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                    at
                    com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.jav\
                    a:827)
                    at
                    com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleSer\
                    vlet.java:159)
                    at
                    com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.ja\
                    va:286)
                    at
                    com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServ\
                    let.java:106)
                    at
                    com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
                    at
                    com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager\
                    .java:1012)
                    at
                    com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.j\
                    ava:913)
                    at
                    com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAp\
                    pRequestDispatcher.java:499)
                    at
                    com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDisp\
                    atcher.java:278)
                    at
                    com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.include(WebAppRequestDispa\
                    tcher.java:111)
                    at com.ibm.servlet.engine.webapp.WebApp.sendError(WebApp.java:620)
                    at com.ibm.servlet.engine.webapp.WebApp.sendError(WebApp.java:546)
                    at
                    com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:92)
                    at
                    com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java\
                    :123)
                    at
                    com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvoca\
                    tion.java:67)
                    at
                    com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestP\
                    rocessor.java:122)
                    at
                    com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.jav\
                    a:315)
                    at
                    com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:6\
                    0)
                    at
                    com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313)
                    at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242)
                    at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)





                    ---------------------------------