beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Feit (JIRA)" <>
Subject [jira] Created: (BEEHIVE-1012) Assertion error when throwing an Error out of onCreate() in a shared flow
Date Fri, 18 Nov 2005 17:37:42 GMT
Assertion error when throwing an Error out of onCreate() in a shared flow

         Key: BEEHIVE-1012
     Project: Beehive
        Type: Bug
  Components: NetUI  
    Versions: V1    
    Reporter: Rich Feit
 Assigned to: Rich Feit 
     Fix For: 1.1

    - In a new shared flow controller, add the following in onCreate():

    protected void onCreate()
        throw new Error("intentional");

    - Create a page flow that references the shared flow.

    - Hit the page flow.

EXPECTED: a stacktrace for the thrown Error.
java.lang.AssertionError: no cached ModuleConfig for foo.SharedFlow

        at org.apache.beehive.netui.pageflow.FlowController.getModuleConfig(

        at org.apache.beehive.netui.pageflow.internal.DefaultExceptionsHandler.handleException(

        at org.apache.beehive.netui.pageflow.FlowController.handleException(

        at org.apache.beehive.netui.pageflow.FlowController.create(

        at org.apache.beehive.netui.pageflow.FlowControllerFactory.createSharedFlow(

        at org.apache.beehive.netui.pageflow.FlowControllerFactory.createSharedFlow(

        at org.apache.beehive.netui.pageflow.FlowControllerFactory.addSharedFlow(

        at org.apache.beehive.netui.pageflow.FlowControllerFactory.getSharedFlowsForPath(

        at org.apache.beehive.netui.pageflow.FlowControllerFactory.getSharedFlowsForRequest(

        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(

        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(

        at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(

        at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(

        at org.apache.struts.action.ActionServlet.doGet(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message