首页 \ 问答 \ Zend Framework - 在不同的模块中重定向到IndexController(Zend Framework - Redirecting to IndexController in different module)

Zend Framework - 在不同的模块中重定向到IndexController(Zend Framework - Redirecting to IndexController in different module)

 所有，  
 我在Zend的mvc Framework中设置了以下项目。 在访问应用程序时，我希望用户重定向到“移动”模块，而不是转到“默认”模块中的IndexController。 我怎么做？  
-billingsystem
-application
    -configs
        application.ini
    -layouts
        -scripts
            layout.phtml
    -modules
        -default
            -controllers
                IndexController.php
            -models
            -views
            Bootstrap.php
        -mobile
            -controllers
                IndexController.php
            -models
            -views
            Bootstrap.php
Bootstrap.php
-documentation
-include
-library
-logs
-public
    -design
        -css
        -images
        -js
    index.php
    .htaccess
 
 我的index.php有以下代码：  
require_once 'Zend/Application.php';
require_once 'Zend/Loader.php';


$application = new Zend_Application(
  APPLICATION_ENV,
  APPLICATION_PATH . '/configs/application.ini'
);

$application->bootstrap()->run();

All, 
I have the following project setup in Zend's mvc Framework. Upon accessing the application, I want the user to redirect to "mobile" module instead of going to IndexController in "default" module. How do I do that? 
-billingsystem
-application
    -configs
        application.ini
    -layouts
        -scripts
            layout.phtml
    -modules
        -default
            -controllers
                IndexController.php
            -models
            -views
            Bootstrap.php
        -mobile
            -controllers
                IndexController.php
            -models
            -views
            Bootstrap.php
Bootstrap.php
-documentation
-include
-library
-logs
-public
    -design
        -css
        -images
        -js
    index.php
    .htaccess
 
My index.php has the following code: 
require_once 'Zend/Application.php';
require_once 'Zend/Loader.php';


$application = new Zend_Application(
  APPLICATION_ENV,
  APPLICATION_PATH . '/configs/application.ini'
);

$application->bootstrap()->run();

原文：https://stackoverflow.com/questions/5969034

更新时间：2023-09-30 07:09

最满意答案

 问题2非常简单 - 你实际上并没有启动一个新线程，而只是调用run() ，它在原始线程中同步运行。 您应该调用start() ，此时异常将不会传回。  
 至于处理ScheduledExecutorService异常 - 如果您调用Future.get() ，它将在原始任务抛出异常时抛出ExecutionException ，从而暴露原始异常：  
 
  尝试检索由抛出异常中止的任务的结果时抛出异常。 这个异常可以使用Throwable.getCause()方法进行检查。  
 
 如果您需要在未阻止未来完成的情况下响应异常，则可以将您的“真实” Runnable包装到另一个已委托给原始run()方法的Runnable中，但需要使用适当的try / catch块。 

Question 2 is really easy - you're not actually starting a new thread, you're just calling run(), which runs synchronously in the original thread. You should be calling start(), at which point the exception won't be propagated back. 
As for handling exceptions in a ScheduledExecutorService - if you call Future.get(), it will throw ExecutionException if the original task threw an exception, exposing the original exception as the cause: 
 
 Exception thrown when attempting to retrieve the result of a task that aborted by throwing an exception. This exception can be inspected using the Throwable.getCause() method. 
 
If you need to respond to exceptions without blocking for the future to complete, you could wrap your "real" Runnable in another one which just delegated to the original's run() method, but with an appropriate try/catch block.

Zend Framework - 在不同的模块中重定向到IndexController(Zend Framework - Redirecting to IndexController in different module)

最满意答案

相关问答

确定Executors.newSingleThreadExecutor（）创建的线程数。执行？(Determining the number of threads created by Executors.newSingleThreadExecutor().execute?)[2022-07-19]

执行程序没有运行所有的线程。(Executors are not running all the threads.)[2023-06-12]

执行者何时真正创建新线程(when does executor really create new thread)[2023-02-18]

执行者服务中断处理(executor Service interupt handling)[2022-02-26]

执行者与线程(Executors vs threads)[2022-03-27]

如何管理执行者(How to manage executors)[2022-04-23]

作业使用的执行者的Spark数量(Spark number of executors that job uses)[2023-12-29]

AMQP入站通道适配器并发 - 消费者属性与任务执行者之间的关系(Relationship between AMQP inbound channel adapter concurrent-consumers attribute and task executors)[2023-07-21]

执行程序或线程使程序无法关闭(Executors or threads keep program from shutting down)[2023-07-02]

风暴中的执行者(Executors in Storm)[2022-04-15]

相关文章

最新问答