[FLOW3-general] Question regarding doctrine integration
Chris Zepernick
chris at swift-lizard.com
Wed Aug 24 14:05:12 CEST 2011
Jepp,
at the moment this is the only way I see either,
question is "Was there a reason that those features are missing" ?
This features ate pretty neat,...
cheers
chris
Am 24.08.11 13:52, schrieb Ferdinand Kuhl:
> Hi Chris,
>
> just let FLOW3 inject the Docrtine-Entity-Manager for you and you have full
> access to the original doctrine-implementation.
> But I have no Idea if this has any sideeffects.
>
> /**
> * @inject
> * @var \Doctrine\Common\Persistence\ObjectManager
> */
> protected $entityManager;
>
> Hope this helps,
> Ferdinand
>
> Chris Zepernick wrote:
>
>> Hi List,
>>
>> guys I got a question, perhaps I have just not found it yet, but as far
>> as I can see some methods of the common doctrine entitymanager are
>> missing at the moment (flush, close, clear, beginTransaction,
>> transactional, commit, rollback,...) is there a way to retreive the
>> entitymanger instance within the repository somehow that I currently do
>> not see, or a whole other approach ?
>>
>> Why do I need this? Well I have to evaluate FLOW3 vs. Symfony2 for a
>> middleware we are planing at the moment, and as far as I can see the
>> methods mentioned would be very much needed for what we are trying to do
>> (authentication [several different ldaps], publishing [migrating complex
>> data to simple production data], pushing data to search server,...).
>>
>> From todays point of view I personally would like to take FLOW3 for
>> that, because of some nice advantages (AOP, annotation injection,...)
>> over Symfony2, although Symfony2 is faster at the moment, for the same
>> basic tasks we tested so far.
>>
>> But now we are going to test more complex tasks, and for those I need
>> those perhaps missing methods, so some help would be nice ;-)
>>
>>
>> thanks
>>
>> chris
>
More information about the FLOW3-general
mailing list