[DOCU-728] Create feature page 'Using observation' Created: 20/Apr/16 Updated: 30/Sep/19 Resolved: 30/Sep/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | outdated | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
With 5.4.6 we deprecate info.magnolia.cms.util.ObservationUtil - instead people should use info.magnolia.observation.WorkspaceEventListenerRegistration. There is a small section in DOCS which mentions the deprecated ObservationUtil - see Configurationmanagement # Observation, i also add a note there, but it is the wrong place to add examples. Besides that there is the Observation module page, but since 5.4.6 release does not include the observation module, both things, the module and the utility classes (in main) are orthogonal. We could create a page about observation mentioning both the module and the utility classes with a code example. Is it correct to say?
|
| Comments |
| Comment by Christoph Meier [ 20/Apr/16 ] |
|
Here is a rough recipe how to use the new class (provided by jsimak):
|
| Comment by Julie Legendre [ 30/Sep/19 ] |
|
In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed. |