Request dispatcher null

Question

          The forward code we have is like
          public void forward(String url, HttpServletRequest request,
          HttpServletResponse response)
          throws ServletException, IOException
          RequestDispatcher dispatcher = getServletConfig().getServletContext().getRequestDispatcher(url);
          dispatcher.forward(request, response);
          My question is:
          As per the documents
          The pathname must begin with a "/" and is interpreted as relative to the current
          context root.
          if my URL is "http://www.abcz.com/<somepage>
          request dispatcher is null? and on one server (say A) that is a problem but other
          server(say B) when given the full URL behaves ok.
          on server A I am getting a null pointer exception , which on tracing happens to
          be the request dispatcher is null.(If http://www.abcz.com/<somepage> is URL) but
          no null pointer exception if url is "/<somepage>"
          On B its behaving fine when given the "http://www.abcz.com/<somepage> " as URL
          to the method.
          Both server A and B are running wl6. Is the difference in service pack cause of
          the problem?
          Internally does wl6 parses the URL to find a relative URL?
          Any help will be greatly appreciated.
          Thanks
          Rumpa
          

Answer 1

And the reason for that is, RequestDispatcher is per application
          scope. And RequestDispatcher comes from the ServletContext which is
          the current application scope. So it has to be relative url. If you
          need to forward to an absolute url, you can use sendRedirect instead.
          Bhaskar
          "Matt Krevs" <[email protected]> wrote in message news:<[email protected]>...
          > as far as i know, you should always specify relative urls when using request
          > dispatchers
          >
          > eg
          >
          > if the entire url is
          > http://myserver/theurl
          > you would code as follows
          >
          > RequestDispatcher dispatcher =
          > getServletConfig().getServletContext().getRequestDispatcher("/theurl");
          > dispatcher.forward(request, response);
          >
          > You definitely should not use complete URLs when calling
          > getRequestDispatcher()
          >
          > what happens on the server that returns a null dispatcher if you manually
          > type the address into the browser? Does weblogic find the resource? If not
          > then you have something specified differently in your server that doesn
          > work.
          >
          >
          > "RUMPA GIRI" <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > The forward code we have is like
          > > /**********************************************/
          > >
          > > public void forward(String url, HttpServletRequest request,
          > > HttpServletResponse response)
          > > throws ServletException, IOException
          > > {
          > > RequestDispatcher dispatcher =
          > getServletConfig().getServletContext().getRequestDispatcher(url);
          > > dispatcher.forward(request, response);
          > > }
          > > /***********************************************/
          > >
          > > My question is:
          > > As per the documents
          > > The pathname must begin with a "/" and is interpreted as relative to the
          > current
          > > context root.
          > > if my URL is "http://www.abcz.com/<somepage>
          > > request dispatcher is null? and on one server (say A) that is a problem
          > but other
          > > server(say B) when given the full URL behaves ok.
          > > on server A I am getting a null pointer exception , which on tracing
          > happens to
          > > be the request dispatcher is null.(If http://www.abcz.com/<somepage> is
          > URL) but
          > > no null pointer exception if url is "/<somepage>"
          > > On B its behaving fine when given the "http://www.abcz.com/<somepage> " as
          > URL
          > > to the method.
          > > Both server A and B are running wl6. Is the difference in service pack
          > cause of
          > > the problem?
          > >
          > > Internally does wl6 parses the URL to find a relative URL?
          > >
          > > Any help will be greatly appreciated.
          > > Thanks
          > > Rumpa
          > >
          > >