[ http://jira.magnolia.info/browse/MAGNOLIA-1394?page=comments#action_13754
]
Karl Krukow commented on MAGNOLIA-1394:
---------------------------------------
Two comments:
- I can reproduce this problem without any packages.
- I get a similar but "reverse" problem: dialogs and paragraphs persist even if
their ids/names are changed.
To reproduce bug: ( I am running Magnolia EE v. 3.0.2 on windows xp)
- create a template, say MyHelloWorld, and a corresponding jsp-script which
references a paragraph: myPageParagraph
(/Example:
<%@ taglib uri="cms-taglib" prefix="cms" %>
<html>
<head><title><cms:out nodeDataName="title" /></title></head>
<body>
<cms:mainBar
paragraph="myPageParagraph"
label="Label Page Properties"
adminButtonVisible="true"/>
Hello Magnolia World!
</body>
</html>
/Example)
- Create a dialog: under myProject/myHelloWorldPageProperties
(in my example this is just a copy of the sitedesigner "pageProperties")
- Create a paragraph: under myProject/myPageParagraph including properties:
* name=myPageParagraph
* dialogPath=myProject/myHelloWorldPageProperties
Now in my setup, if I create a web-page using this template and I click the
Properties button, I get the same problem:
info.magnolia.cms.beans.config.ConfigurationException: no dialog registered for
name: myPageParagraph
However, there is more: If I restart, it works, BUT supposing that I now change
the dialogPath from myProject/myHelloWorldPageProperties to
myProject/InvalidReference (or any other that is not defined) it still works:
If I refresh the browser and click the button I get the dialog. So it seems
that the changes are not "flushed".
There is a workaround: if I 'Activate' the paragraph and the dialog, I
(correctly) get the ConfigurationException.
Regards,
- Karl
> Adding new dialogs needs a Servlet Engine restart
> -------------------------------------------------
>
> Key: MAGNOLIA-1394
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1394
> Project: Magnolia
> Issue Type: Bug
> Components: templating
> Affects Versions: 3.0.1
> Environment: Mac OS X, Tomcat 5, Firefox 2
> Reporter: Giancarlo Berner
> Assigned To: Philipp Bracher
> Attachments: dialog_error.jpg
>
>
> - Install two different Magnolia Instances
> It is a little annoying if you have to restart Tomcat whenever you add NEW
> dialogs.
> - Create a package with the Packager tool on one instance
> - The package must contain dialogs which are not in the other instance
> - Install package with new dialogs on other instance
> - Click New bar on other instance and select new paragraph with new dialog
> - ERROR: no dialog registered for name: {new dialog name}
> - Click Tools/Deploy and re-deploy
> - Click New bar on other instance and select new paragraph with new dialog
> - ERROR: same error again
> - Restart Tomcat
> - Click New bar on other instance and select new paragraph with new dialog
> - Everything is fine
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
