使用Doctrine 2将实体保存到REST API而不是DB

您可以使用https://github.com/doctrine/rest以构建一个REST客户端，该客户端与目标服务器进行对话。这里的关键部分是从实体（本地）到RESTneneneba API（目标）的映射。

简而言之：Doctrine2（本地DB）->Rest客户端（实体到Rest映射）->Request（目标服务器）

Doctrine/Rest还提供了另一种方法：Doctrine-Rest服务器，通过Rest（对服务器的请求）公开您的本地实体。但这不是你想要的。

DoctrineRestDriver正是在做您想要做的事情。https://github.com/CircleOfNice/DoctrineRestDriver

配置原则：

doctrine: dbal: driver_class: "Circle\DoctrineRestDriver\Driver" host: "http://www.your-url.com/api" port: 80 user: "Circle" password: "CantRenember"

构建实体：

/**
 * This annotation marks the class as managed entity:
 *
 * @ORMEntity
 *
 * You can either only use a resource name or the whole url of
 * the resource to define your target. In the first case the target 
 * url will consist of the host, configured in your options and the 
 * given name. In the second one your argument is used as it is.
 * Important: The resource name must begin with its protocol.
 *
 * @ORMTable("products|http://www.yourSite.com/api/products")
 */
class Product {
    /**
     * @ORMColumn(type="integer")
     * @ORMId
     * @ORMGeneratedValue(strategy="AUTO")
     */
    private $id;
    /**
     * @ORMColumn(type="string", length=100)
     */
    private $name;
    public function getId() {
        return $this->id;
    }
    public function setName($name) {
        $this->name = $name;
        return $this;
    }
    public function getName() {
        return $this->name;
    }
}

让我们假设我们已经使用了值http://www.yourSite.com/api/products用于产品实体的@Table注释。

控制器：

<?php
namespace CircleBundleController;
use SymfonyBundleFrameworkBundleControllerController;
use SymfonyHttpFoundationResponse;
class UserController extends Controller {
    /**
     * Sends the following request to the API:
     * POST http://www.yourSite.com/api/products HTTP/1.1
     * {"name": "Circle"}
     *
     * Let's assume the API responded with:
     * HTTP/1.1 200 OK
     * {"id": 1, "name": "Circle"}
     *
     * Response body is "1"
     */
    public function createAction() {
        $em     = $this->getDoctrine()->getManager();
        $entity = new CircleBundleEntityProduct();
        $entity->setName('Circle');
        $em->persist($entity);
        $em->flush();
        return new Response($entity->getId());
    }
    /**
     * Sends the following request to the API by default:
     * GET http://www.yourSite.com/api/products/1 HTTP/1.1
     *
     * which might respond with:
     * HTTP/1.1 200 OK
     * {"id": 1, "name": "Circle"}
     *
     * Response body is "Circle"
     */
    public function readAction($id = 1) {
        $em     = $this->getDoctrine()->getManager();
        $entity = $em->find('CircleBundleEntityProduct', $id);
        return new Response($entity->getName());
    }
    /**
     * Sends the following request to the API:
     * GET http://www.yourSite.com/api/products HTTP/1.1
     *
     * Example response:
     * HTTP/1.1 200 OK
     * [{"id": 1, "name": "Circle"}]
     *
     * Response body is "Circle"
     */
    public function readAllAction() {
        $em       = $this->getDoctrine()->getManager();
        $entities = $em->getRepository('CircleBundleEntityProduct')->findAll();
        return new Response($entities->first()->getName());
    }
    /**
     * After sending a GET request (readAction) it sends the following
     * request to the API by default:
     * PUT http://www.yourSite.com/api/products/1 HTTP/1.1
     * {"name": "myName"}
     *
     * Let's assume the API responded the GET request with:
     * HTTP/1.1 200 OK
     * {"id": 1, "name": "Circle"}
     *
     * and the PUT request with:
     * HTTP/1.1 200 OK
     * {"id": 1, "name": "myName"}
     *
     * Then the response body is "myName"
     */
    public function updateAction($id = 1) {
        $em     = $this->getDoctrine()->getManager();
        $entity = $em->find('CircleBundleEntityProduct', $id);
        $entity->setName('myName');
        $em->flush();
        return new Response($entity->getName());
    }
    /**
     * After sending a GET request (readAction) it sends the following
     * request to the API by default:
     * DELETE http://www.yourSite.com/api/products/1 HTTP/1.1
     *
     * If the response is:
     * HTTP/1.1 204 No Content
     *
     * the response body is ""
     */
    public function deleteAction($id = 1) {
        $em     = $this->getDoctrine()->getManager();
        $entity = $em->find('CircleBundleEntityProduct', $id);
        $em->remove($entity);
        $em->flush();
        return new Response();
    }
}

您甚至可以使用DQL或本机查询。

由于没有现成的解决方案，我决定编写自己的解决方案。我称之为RAPL。它深受Doctrine的ORM的启发（事实上，它使用了Doctrine Common提供的许多接口）。

使用RAPL，我可以简单地编写一个小的YAML文件来配置实体和web服务之间的映射，从而允许我使用自定义EntityManager持久化/检索实体。

我认为你的做法不对
我现在还没有准备好深入研究文档，但我将条令堆栈理解为：

ORM->DQL（条令查询语言）->dbal->一些数据库sql

并指出您在DBAL中作为自定义数据库驱动程序的实现。

我认为创建一个通用的REST驱动程序非常有趣的功能，它将很容易与第三方服务集成。

我不确定，但您可以尝试使用实体的生命周期回调事件来通过REST执行持久化逻辑。