Announcement Announcement Module
No announcement yet.
Going nuts on a simple flow: "The requested resource() is not available" Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Going nuts on a simple flow: "The requested resource() is not available"

    Something, obviously, is terribly wrong in my setup because I'm getting the error message:

    HTTP Status 404
    The requested resource () is not available

    On a simple invocation of my flow.

    Here's what my webflow config looks like:

    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns=""
    <!-- WEBFLOW -->
        <bean id="incidentFlowHandler" class="org.springframework.webflow.mvc.servlet.FlowController">
            <property name="flowExecutor" ref="flowExecutor" />
            <property name="redirectHttp10Compatible" value="true" />
        <webflow:flow-registry id="flowRegistry" flow-builder-services="flowBuilderServices">
            <webflow:flow-location path="/WEB-INF/flows/incident-flow.xml" id="incident" />
             <!--<webflow:flow-location-pattern value="/**/*-flow.xml" />-->
        <!-- Plugs in a custom creator for Web Flow views -->
        <webflow:flow-builder-services id="flowBuilderServices" view-factory-creator="mvcViewFactoryCreator" development="true"/>
        <bean id="mvcViewFactoryCreator"
             <!--this is required for voiceXML usesage - since the default is _eventID and the underscore-->
                 <!--is not allowed in VoiceXML parameter names -->
            <property name="eventIdParameterName" value="eventID" />
            <property name="viewResolvers">
                    <ref bean="vxmlViewResolver" />
        <webflow:flow-executor id="flowExecutor" flow-registry="flowRegistry">
            <!-- webflow has some great features to help handle returning to previous states when
                 the user hits the back button... etc. but VoiceXML doesn't ever use the "back button"
                 so we disbale the execution snapshots and save the resources -->
            <!-- If snapshots are enabled, the entire object graph that makes up the model for the 
                flow must also be serializable - which currently is not the case for some of our objects -->
            <webflow:flow-execution-repository max-executions="5" max-execution-snapshots="0" />
    Here's my dispatcher-servlet config:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <beans xmlns=""
        <bean id="handlerMapping"
            <property name="mappings">
                    <!-- although they are mapped here, flows are defined in the webflow-config.xml file -->
                    <prop key="/incident.vxml">incidentFlowHandler</prop>
       <!-- Enables convention-based request URL mapping to @Controllers (ex: /person/* maps to PersonController) -->
        <bean class="">
            <property name="order" value="1"/>
        <bean class="org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter" />
        <bean class="org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter"/>
        <bean class="org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping"/>
        <bean id="vxmlViewResolver" class="org.springframework.web.servlet.view.InternalResourceViewResolver">
            <property name="requestContextAttribute" value="requestContext"/>
            <property name="viewClass" value="org.springframework.web.servlet.view.JstlView"/>
            <property name="prefix" value="/WEB-INF/views/ivr/" />
            <property name="suffix" value=".jsp" />
            <property name="order" value="1" />
    Here's the flow definition for the flow that is called:

    <?xml version="1.0" encoding="UTF-8"?>
    <flow xmlns=""
        <input name="incidentUID" required="true" />
            <evaluate expression="incidentService.findByIncidentUID(incidentUID)"
                      result-type="" />
        <view-state id="incidentOutbound" view="incidentOutbound" >
            <transition on="submit" to="incidentComplete"/>
        <end-state id="incidentComplete" view="incidentOutbound" />
    And finally, here's a snippet of the debug log when it is rendering the view:

    The view is in the right spot, and gets resolved - if I move or delete the incdentOutbound.jsp I get a different error - so something funky seems to be going on when Tomcat goes to grab the view and render it...

    But the error is "The requested resource () is not available." which makes me wonder why it is not even requesting a resource - normally that error has the name of the resource being requested...

    Anyone have any ideas on how I can fix this?

  • #2
    There was a simple solution

    I had my the path *.jsp being mapped to my dispatcher servlet - which then caused requests to /WEB-INF/ jsp pages to be send to the dispatcher servlet - which didn't have any idea what to do with the jsp urls.

    changing that fixed this first error. (I'm still fighting a few other things to get it all running properly)