同时使用PHP League中的Route和Container不能创建响应

如何解决同时使用PHP League中的Route和Container不能创建响应

我正在重写一个PHP应用程序,该应用程序在过去十年中得到了发展,并选择了League \ Route,League \ Container和Aura \ Sql来建立坚实的基础。 我在将路由器中的所有组件连接在一起时遇到了麻烦-其他组件似乎可以正常工作:

索引:

    $container = new League\Container\Container;
    $container->defaultToShared(); // Added along the line - not sure whether this is needed
    $container->delegate( new League\Container\ReflectionContainer ); // Enable auto wiring
    
    $container
        ->add('dbpro',Aura\Sql\ExtendedPdo::class)
        ->addArgument('pgsql:dbname=app client_encoding=UTF8')
        ->addArgument('app')
        ->addArgument(NULL)
        ->addArgument($db_attributes);
    
    $container->add('modl_party',App\Model\Party::class)
      ->addArgument('dbpro');
    $container->add('ctrl_party',App\Controllers\Party::class)
      ->addArgument('modl_party');
    $container
        ->addServiceProvider('App\ServiceProvider\LaminasDiactorosServiceProvider');
    
    $strategy = (new League\Route\Strategy\ApplicationStrategy)->setContainer($container);
    $router   = (new League\Route\Router)->setStrategy($strategy);
    
    $router->group('/API/v1',function (\League\Route\RouteGroup $route)
    {
      $route->map('GET','/party/{id}','App\Controllers\Party::get');
      $route->map('GET','/parties/{dos_nr}','App\Controllers\Parties::get');
    });
    
    try {
        $response = $router->dispatch(
            $container->get('Laminas\Diactoros\ServerRequest'),$container->get('Laminas\Diactoros\Response')
        );
    } catch (League\Route\Http\Exception\NotFoundException $e) {
        $response = $container->get('Laminas\Diactoros\Response');
        $response->getBody()->write($e->getMessage());
        $response = $response->withStatus($e->getStatusCode());
    }
    
    $container->get('Laminas\Diactoros\Response\SapiEmitter')->emit($response);

控制器:

    namespace App\Controllers;
    
    use Psr\Http\Message\ResponseInterface;
    use Psr\Http\Message\ServerRequestInterface;
    use Laminas\Diactoros\Response;
    
    class Party {
    
      protected $party;
    
      public function __construct( \App\Model\Party $party )
      {
        $this->party = $party;
      }
    
      public function get(ServerRequestInterface $request,array $args) : ResponseInterface
      {
        $party  = $this->party->get( $args['id'] );
        $body     = json_encode( $party );
        $response = new Response;
        $response->getBody()->write($body);
        return $response
          ->withAddedHeader('content-type','application/json')
          ->withStatus(200);
      }
    
    }

型号:

    namespace App\Model;
    
    use \Aura\Sql\ExtendedPdo;
    
    class Party {
    
      protected $pdo;
      protected $table;
      public $id;
    
      public function __construct( \Aura\Sql\ExtendedPdo $pdo ) {
        $this->pdo = $pdo;
        $this->table = 'parties';
      }
    
      public function get( $id )
      {
        $sql    = "SELECT ...";
        $binds  = array( 'id' => $id );
        $obj = $this->pdo->fetchObject( $sql,$binds,'App\Model\Party',[$this->pdo] );
        return $obj;
      }
    }

结果:

$ curl <URI>/API/v1/party/15285
<b>Fatal error</b>:  Uncaught League\Container\Exception\NotFoundException: Unable to resolve a value for parameter (dsn) in the function/method (__construct) in [...]/vendor/league/container/src/Argument/ArgumentResolverTrait.php:79
Stack trace:
#0 [internal function]: League\Container\ReflectionContainer-&gt;League\Container\Argument\{closure}(Object(ReflectionParameter))
#1 [...]/vendor/league/container/src/Argument/ArgumentResolverTrait.php(84): array_map(Object(Closure),Array)
#2 [...]/vendor/league/container/src/ReflectionContainer.php(52): League\Container\ReflectionContainer-&gt;reflectArguments(Object(ReflectionMethod),Array)
#3 [...]/vendor/league/container/src/Container.php(183): League\Container\ReflectionContainer-&gt;get('Aura\\Sql\\Extend...')
#4 [...]/vendor/league/container/src/Argument/ArgumentResolverTrait.php(45): League\Container\Container-&gt;get('Aura\\Sql\\Extend...')
#5 [...]/vendor/league/container/src/Argument/ArgumentResolverTrait.php(86): League\Contai in <b>[...]/vendor/league/container/src/Argument/ArgumentResolverTrait.php</b> on line <b>79</b>

其他信息:

  • 我可以从容器中成功获取ExtendedPdo实例
  • 我可以从容器和':: get(15285)'中成功获取App \ Model \ Party实例
  • 我可以从容器和':: get(15285)'中成功获取App \ Controllers \ Party实例
  • 我也使用文档中提供的示例尝试了JsonStrategy,但是得到了相同的结果
  • 我未包含LaminasDiactorosServiceProvider.php代码,但这与文档中的示例相同(除了将“ Zend”替换为“ Laminas”之外)

->我认为错误一定是路由器“构建”响应方式的某个地方?

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-