分離業務邏輯從PHP學說2

Question

我使用symfony的2.3和PHP學說2.

該方案具有以下型號：

• 實體訂單 - 一個典型的客戶訂單
• 實體BadOrderEntry（場：id，訂單 - 與訂單的單向一對一關係，createdAt）
• 工廠BadOrderEntryFactory用於創建實體BadOrderEntry
• 存儲庫BadOrderEntryReposi保守黨對實體的搜索方法BadOrderEntry
• 經理BadOrderEntryManager用於保存/編輯/刪除實體的方法BadOrderEntry

• 和主類BadOrderList - 壞的訂單列表中，這個類的代碼：

  private $factory; 
  private $repository; 
  private $manager; 
  
  public function __construct(
      BadOrderEntryFactory $f, 
      BadOrderEntryRepository $r, 
      BadOrderEntryManager $m 
  ) { 
      $this->factory = $f; 
      $this->repository = $r; 
      $this->manager = $m; 
  } 
  
  public function has(Order $order) 
  { 
      return $this->repository->existsByOrder($order); 
  } 
  
  public function add(Order $order) 
  { 
      if (! $this->has($order)) { 
       $entry = $this->factory->create($order); 
       $this->manager->save($entry); 
      } 
  } 
  
  public function remove(Order $order) 
  { 
      $entry = $this->repository->findOneByOrder($order); 
      if ($entry !== null) { 
       $this->manager->delete($entry); 
      } 
  } 
  

我很喜歡這門課的設計。我想了很多。 一切都很美妙。但！有一個問題：必須在事務中執行方法添加和刪除操作。在PHP Docrine 2

事務代碼看起來是這樣的：

<?php 
$em->getConnection()->beginTransaction(); 
try { 
    //... do some work 
    $em->getConnection()->commit(); 
} catch (Exception $e) { 
    $em->getConnection()->rollback(); 
    throw $e; 
} 

但我怎麼能叫內BadOrderList這個代碼？

我花了很多時間和取決於數據庫（和相應的PHP Doctrine 2），並再次創建它？ 現在依賴關係被隱藏在類BadOrderEntryRepository和BadOrderEntryManager中。

如何在類BadOrderList中隱藏對事務機制的依賴？

Answer 1

我們的討論後，我有一個回答你的問題。 問題真的不是「如何在類BadOrderList中隱藏對事務機制的依賴？」，但是如何從持久層分離模型？（該特例中的學說2）。

我想說明我的建議有一些代碼

class BadOrderEntry 
// Bad - is too bad word to describe an order here. Why is it bad? Is it Declined? Cancelled? 
{ 
    private $order; 
    // some code 
} 
class BadOrderEntryFactory 
{ 
    // If there is not to much processing to build BadOrderEntry better use factory method like BadOrderEntry::fromOrder($order); 
} 
class BadOrderEntryRepository 
{ 
    // here is some read model 
} 
class BadOrderEntryManager 
// ITS a part of our model and shouldn't be coupled to ORM 
{ 
    public function save(BadEntry $be) 
    { 
    // some model events, model actions 
    $this->doSave($be); // here we should hide our storage manipulation 
    } 

    protected function doSave($be) // it can be abstract, but may contain some basic storage actions 
    { 
    } 

    // similar code for delete/remove and other model code 
} 
class ORMBadOrderEntryManager extends BadOrderEntryManager 
// IT'S NOT the part of your model. There is no business logic. There is only persistent logic and transaction manipulation 
{ 
    protected $entityManager; 

    // some constructor to inject doctrine entitymanager 

    protected doSave($be) 
    { 
    $em = $this->entityManager; 
    $em->getConnection()->beginTransaction(); // suspend auto-commit 
    try { 
     $em->persist($be); 
     $em->flush(); 
     $em->getConnection()->commit(); 
    } catch (Exception $e) { 
     $em->getConnection()->rollback(); 
     throw $e; 
    } 
    } 
} 
// You can also implement ODMBadOrderEntryManager, MemcacheBadOrderEntryManager etc. 

所以，如果我們談論的目錄結構，所有的模型可以被移出束和任何地方使用。你的包結構將是這樣的：

BadEntryBundle 
| 
+ Entity 
| | 
| --- BadOrderEntryEntity.php 
| 
+ ORM 
| | 
| --- ORMBadOrderEntryManager.php 

然後你只注入ORMBadOrderEntryManager您BadOrderEntryList

Answer 2

您可以將您的類作爲服務進行轉換，然後在您的類內部注入服務容器後調用它。 您可以在這裏瞭解dependency injection找到更多的信息：

$injectedContainerOfService->get("id_of_your_service")