Feature #28228: FLOW3 should be usable without Doctrine - TYPO3.Flow - TYPO3 Forge

TYPO3 Flow Base Distribution TYPO3.Eel TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Welcome Packages Applications

Feature #28228

FLOW3 should be usable without Doctrine

Added by Christopher Hlubek about 4 years ago. Updated about 4 years ago.

Status:

Resolved

Start date:

2011-07-15

Priority:

Must have

Due date:

Assigned To:

Christopher Hlubek

% Done:

100%

Category:

Target version:

PHP Version:

Complexity:

Has patch:

Description

FLOW3 should work without the Doctrine package. We should try to move the code that relies on Doctrine to a separate package to make FLOW3 more modular.

If I don't active the Doctrine package in the current version I'll get an exception during compilation:

PHP Fatal error:  Class 'Doctrine\ORM\Query\TreeWalkerAdapter' not found in .../Packages/Framework/TYPO3.FLOW3/Classes/Persistence/Doctrine/CountWalker.php on line 24

As a general goal we should try to push FLOW3 more into a component based architecture (though we provide the user with a full-stack framework with the base distribution).

Associated revisions

Revision 7f648f8a
Added by Christopher Hlubek about 4 years ago

[BUGFIX] It should be possible to disable Doctrine integration

This change introduces a setting to control the integration of Doctrine
in the bootstrap of FLOW3. For non-Doctrine persistence backends no
Doctrine code should be invoked, otherwise warnings about missing
driver or driverClass options will occur. And there is no need to
do proxy code compilation for Doctrine if it's not used.

Change-Id: I0ae80d2106c758d12242805ed20becb696e75da8
Resolves: #28228

History

#1 Updated by Christopher Hlubek about 4 years ago

One note: It would be okay to bundle the Doctrine\Common package as it just provides general tools and datastructures. Though I still feel uncomfortable with the naming implications since it looks like we have this strong dependency on Doctrine.