-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Observation #241
base: 2.x
Are you sure you want to change the base?
[WIP] Observation #241
Conversation
@@ -127,10 +127,12 @@ public function __construct(FactoryInterface $factory, Repository $repository, $ | |||
{ | |||
$this->factory = $factory; | |||
$this->repository = $repository; | |||
$this->objectManager = $this->factory->get('ObjectManager', array($transport, $this)); | |||
$observationManager = $this->factory->get('Observation\ObservationManager', array($factory, $this, $transport)); | |||
$this->objectManager = $this->factory->get('ObjectManager', array($transport, $this, $observationManager)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Observation manager is always created when the session is intantiated.
what do you mean by non-journaling? that we only see the events of the current session? i agree it should go into jackalope/jackalope. just make sure its done in a way that jackalope-jackrabbit can do everything differently. |
yeah. so repositories can support "non journaling", journaling or both. Non-journaling would be the equivalent of the SF event system I think. http://www.day.com/specs/jcr/2.0/12_Observation.html#12.1%20Event%20Model
|
can we reuse the symfony event component for this? |
We could wrap it I guess. |
I started working on Observation this morning. Basically the goal of this PR is to support non-journaling event observation.
I guess this can all be done at the jackalope level?