RequstDispatcher problem in Seperate Deployment

Hi Phani,

My project is configured similarly, and in my servlets, I am able to do:

RequestDispatcher dispatch = request.getRequestDispatcher("/myforms/myPage.jsp");

dispatch.forward(request,response);

where my orbeon filter is set to the url-mapping of the “myforms” directory.  

What does your forwarding code look like?  Are you able to contact your servlet if you just do a GET request to it?  It is a bit strange to me that your servlet’s <url-mapping> entry is the same as the directory in which you are telling orbeon to find the forms to render. 

Thanks,

Stephanie

Hi all,
       I deployed my application "project" as a separately to orbeon. Filter is configured with
    <filter>
        <filter-name>orbeon-xforms-filter</filter-name>
        <filter-class>org.orbeon.oxf.servlet.OrbeonXFormsFilter</filter-class>
        <init-param>
            <param-name>oxf.xforms.renderer.context</param-name>
            <param-value>/orbeon-development</param-value>
        </init-param>
        </filter>
and filter mapping
    <filter-mapping>
        <filter-name>orbeon-xforms-filter</filter-name>
        <url-pattern>/xforms-jsp/*</url-pattern>
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>FORWARD</dispatcher>
    </filter-mapping>

    <!-- This is necessary so that XForms engine resources can be served appropriately -->

    <filter-mapping>
        <filter-name>orbeon-xforms-filter</filter-name>
        <url-pattern>/orbeon-development/*</url-pattern>
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>FORWARD</dispatcher>
    </filter-mapping>

I have a servlet-mapping
    <servlet-mapping>
        <servlet-name>FrontControllerServlet</servlet-name>
        <url-pattern>/xforms-jsp/*</url-pattern>
    </servlet-mapping>

From this servlet I am trying to dispatch request to index.xhtml.
for cases "/project/xforms-jsp/index.xhtml", "/xforms-jsp/index.xhtml", "/index.xhtml" It is not forwarding to the actual page. What might be the problem.
--
Regards
Phani. S

Hi Phani,

RequestDispatcher is just saying “go to this page” - it doesn’t really know anything about where the client came from.  One idea you could try is setting an attribute in the request that goes through the right path to your page that you could check in myPage.jsp and if it’s not there, redirect the client to the start page so they go through the right way.  Does that make sense?

Good luck,

Stephanie

Stephanie,
           I slightly change my configuration in deployment descriptor.

    <!-- Any web resource under /web-port is processed by the XForms engine -->   
<filter-mapping>
        <filter-name>orbeon-xforms-filter</filter-name>
        <url-pattern>/web-port/*</url-pattern>
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>FORWARD</dispatcher>i
    </filter-mapping>

    <servlet-mapping>
        <servlet-name>FrontControllerServlet</servlet-name>
        <url-pattern>/portal/*</url-pattern>
    </servlet-mapping>

From my FrontControllerServlet I use

RequestDispatcher dispatch = request.getRequestDispatcher("/web-port/myPage.jsp");

dispatch.forward(request,response);

It is working fine. But it is not stopping the client using the urls directly such as http://localhost/sample/web-port/mypage.jsp.

How do I stop clients directly use these urls. They must come through sample/portal/ etc...

--
Regards
Phani. S