Can someone tell me which filters in server/filters/ need /dms and /dms-static bypases added in order for DMS to work? I added them to "rendering" filter and DMS still does not work.
Thanks Amir -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Friday, May 04, 2007 4:51 AM To: [email protected] Subject: Re: [magnolia-dev] custom servlet: HTTP Status 404 - The requested resource () is not available. 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? Are there any rules when patching bootstrap files (system view)? jcr:uuid or activation come to mind... O. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
