[MGNLDMS-30] DMS: Can't Create new Document when using ROOT webapp Created: 14/Nov/06  Updated: 03/Jul/14  Resolved: 07/Dec/06

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Type: Bug Priority: Blocker
Reporter: Sean McMains Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Redhat/Mac OS X, Tomcat


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When the Magnolia WAR is delpoyed normally, creating documents in DMS works fine.

When one changes the webapp name to ROOT, however, clicking the New Document button results in an error:

ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/].[AdminTreeServlet] StandardWrapperValve.java(invoke:260) 14.11.2006 09:58:43 Servlet.service() for servlet AdminTreeServlet threw exception
info.magnolia.module.admininterface.InvalidTreeHandlerException: No tree handler for [.magnolia/dialogs/dmsEdit] found
at info.magnolia.module.admininterface.TreeHandlerManager.getTreeHandler(TreeHandlerManager.java:57)
at info.magnolia.module.admininterface.AdminTreeMVCServlet.getHandler(AdminTreeMVCServlet.java:46)
at info.magnolia.cms.servlets.MVCServlet.doPost(MVCServlet.java:96)
at info.magnolia.cms.servlets.MVCServlet.doGet(MVCServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
....

This appears to be caused by an incorrect URL for the New Document dialog.



 Comments   
Comment by Sean McMains [ 16/Nov/06 ]

I've verified that this problem still occurs with the release version of 3.0. This is, unfortunately, a blocker for making the DMS available to our users.

Comment by Philipp Bracher [ 17/Nov/06 ]

not sure if this is fixed (related to version dialog problems we have) need to check it

Comment by Sean McMains [ 29/Nov/06 ]

Hi Philipp,

I checked out the latest 3.0.1 snapshot and built it this morning. The problem still exists.

Sean

Comment by Sameer Charles [ 04/Dec/06 ]

I can confirm that its still the same behaviour if running as root context

Comment by Matthew Schmidt [ 04/Dec/06 ]

We're seeing a similar issue related to activating documents in the DMS. When we make new folders (pre-existing ones are fine) and then try to activate those folders or files in those folders we get the following error:

ERROR info.magnolia.cms.core.version.BaseVersionManager BaseVersionManager.java(addVersion:129) 04.12.2006 14:29:43 failed to copy versionable node to version store, reverting all changes made in this session
ERROR info.magnolia.module.admininterface.commands.VersionCommand VersionCommand.java(execute:62) 04.12.2006 14:29:43 can't version
javax.jcr.ItemNotFoundException: failed to build path of fc7f8677-c8be-4178-8789-edaaa082843b: cafebabe-cafe-babe-cafe-babecafebabe has no child entry for fc7f8677-c8be-4178-8789-edaaa082843b

Comment by Magnolia International [ 04/Dec/06 ]

It should be noted that Matthew's admin instance is not in the root context of his appserver, but his public instance is
in the root context. (same server)

Comment by Sameer Charles [ 04/Dec/06 ]

Its a different problem, this issue is related to dialog handler.
Can you please create a seperate issue on JIRA for versioning on DMS

Comment by Philipp Bracher [ 07/Dec/06 ]

fixed the general mgnlOpenWindow method to handle this

Generated at Mon Feb 12 00:47:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.