On 04.05.2007, at 10:51, Oliver Lietz wrote:
Am Freitag, 4. Mai 2007 schrieb Philipp Bracher:
Am Freitag, 27. April 2007 schrieb Philipp Bracher:
DMS
- it is likely that you did not deploy a new dms (1.2-SNAPSHOT) to
your maven repository since we moved the HierarchyManager.
- I deployed a new snapshot so this issue should be gone for you
too
No. Magnolia and DMS module are both build from trunk (r9306). The
issue still
exists on a freshly bootstrapped instance.
I did not yet fix that. You have to define a bypass for the /dms/*
path yourself. Sorry for that.
No problem. After I found out what is going on in AggregatorFilter
adding the
bypasses for the servlets was an easy task. Should I add a patch to
Jira
(http://jira.magnolia.info/browse/MGNLDMS-97) or can you just add
them to
your config/bootstrap file?
Since you are a commiter you can commit those kind of fixes yourself ;-)
Thanks!
Are there any rules when patching bootstrap files (system view)?
jcr:uuid or
activation come to mind...
No rules so far, uuid is only relevant in some rare cases.
Philipp Bracher
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
