Wrap PHPCR session completely to enable operation log

[dantleech]

It would be useful to be able to see what operations have been scheduled, for example before calling session:save.

One way to accomplish this would be to wrap the Phpcr session and wrap the implementations NodeInterface classes and add logging capabilities to them.

We could then add a command such as:

shell:session:log --nodes
+-------------------------------+
| Path      | Method     | Args |
+-------------------------------+
+ /path    | remove     |     |

etc.

[dbu]

but unsaved changes only remain until the session terminates.
does jackalope not provide some inofficial public methods to get to the operations log and see what is scheduled? though if you go through phpcr-odm, the phpcr operations only happen during the flush, and session::save is called automatically.

sounds more like a "dry-run" use case to me. (a feature that does not exist either).

for RoutingAuto, when would you use this? to debug the configuration?

[dantleech]

heh. this should have been in PHPCR-Shell :P but this feature is just a feature so that you can sanity check before calling save in the shell

[wouterj]

@dantleech what do you think about removing the issue tracker in the component repo (this one) and only enabling it in the bundle repo? That would make it easier to track the issues

[dbu]

@wouterj i would not recommend to disable the issues here. if the intention is to have people use this component without the bundle, its weird to ask them to go to the bundle. tracking things that span both component and bundle will be hard anyways, as we don't do a subtree split.

maybe the current issues need sorting out what belongs to component and what to bundle.