handling end states

[Sam Brannen]

Hi Wang,

What Michael Clark pointed out about configuring a ContextLoaderPlugIn is correct. Doing so will solve your NullPointerException issue; however, this will not help you with your initial problem.

The bad news for you is that my earlier assumption was correct: you can not directly use the SpringWebFlowExceptionResolver in conjunction with Struts.

The reason is that SpringWebFlowExceptionResolver is a HandlerExceptionResolver which is called by Spring's DispatcherServlet in its processHandlerException() method. Since you are using Struts, a Struts ActionServlet is responsible for handling your request. Thus any exceptions thrown will never be handled by a HandlerExceptionResolver and must therefore be handled by the Struts framework (for example, by implementing a custom Struts ExceptionHandler as I mentioned earlier).

Another possible option would be to override the execute(ActionMapping, ActionForm, HttpServletRequest, HttpServletResponse) method of SWF's FlowAction and add a try-catch block around the calls into the SWF framework code. You could then decide how to handle the exception yourself, perhaps in a manner similar to the SpringWebFlowExceptionResolver implementation.

Hope this helps!

And if you develop a custom exception handling solution for use with Struts+SWF, please post it back here in the forum or on Jira, as I'm sure the rest of the community would appreciate it.

cheers,

Sam

[Sam Brannen]

For those of you (still) following this thread and using my SpringWebFlowExceptionResolver, I have uploaded a new release with support for SWF 1.0.x. See the new thread here:

http://forum.springframework.org/sho...d.php?p=111246

cheers,

Sam

[Sam Brannen]

Hi sre786,

I realize that this is a rather belated reply; however, I hope you still find it helpful...

Thanks for providing the code.

You're very welcome!

I copied the code and tried to get it working but I have a problem. May be I am missing something here... If I have multiple flows ... i can't set a defaultFlowId for my FlowExecutor and _flowId parameter is not passed around in the URL once the flow kicks-off.... how do I extract what flow to start from available info ?(which seems to be just the expired _flowExecutionKey)?

These are some good points you raise.

• Due to the current limitations of SWF, there is no way to determine the flowId from the conversation and/or flow execution keys for an expired flow. Thus if you cannot configure a defaultFlowId, it does not make sense to use the SpringWebFlowExceptionResolver.
• A viable option is to use multiple FlowControllers, one configured for each flow with a specific path and corresponding defaultFlowId. Each of these FlowControllers could reference the same flowExecutor. Thus, you would essentially have one central repository (i.e., flowRegistry), but you would have multiple, unique entry points into the various flows. This would allow SpringWebFlowExceptionResolver to restart the correct flow based merely on the path and configured defaultFlowId per FlowController.

Does that make sense?

Sam

p.s. in case you are still using the code from 2006, you might want to check out the latest release: http://forum.springframework.org/showthread.php?t=36960

[Sudheesh]

Hi Sam,

I am using your "Custom SimpleMappingExceptionResolver"..

But when am getting "org.springframework.webflow.execution.repository. NoSuchFlowExecutionException"

The debugger is not reaching this class.


I have configured the beans as u mentioned ..



How Spring is registering " SpringWebFlowExceptionResolver"?

[Sudheesh]

I have configured globalExceptionResolver.

I am using Spring webflow + Spring MVC.

Exceptions are not reaching globalExceptionResolver..



How do I need to configure globalExceptionResolver?

Do i need to refer it from some other bean???

[Sam Brannen]

Hi Sudheesh,

How Spring is registering " SpringWebFlowExceptionResolver"?

Spring's DispatcherServlet will automatically detect any HandlerExceptionResolvers registered in the ApplicationContext of your web application. Thus, its mere presence should ensure that it is registered. Note, however, that the resolvers will be sorted according to their configured ordering (i.e., via the Ordered interface, which SimpleMappingExceptionResolver implements). In addition, you must configure the FlowDefinitionRegistry for a SpringWebFlowExceptionResolver as I mentioned in the JIRA here:

http://jira.springframework.org/browse/SWF-158

As of version 1.9, SpringWebFlowExceptionResolver requires that you manually configure
a FlowDefinitionRegistry as follows:

<bean id="springWebFlowExceptionResolver" class="org.springframework.webflow.executor.support.SpringWebFlowExceptionResolver">
    <property name="flowDefinitionRegistry" ref="flowRegistry" />
</bean>

Regards,

Sam

[Sudheesh]

Thanks Sam,

This post has helped me a lot


I think following thread is also some what related.

http://forum.springframework.org/showthread.php?t=54711


Thanks once again,
Sudheesh

[eros]

this exception handling strategy is implemented with Spring?
Or other way to implement this?