I'm in charge of two Magnolia instances (one for testing and the other for the 
actual application, both 4.5.2 CE) and this one component including its dialog 
and jsp templating file is installed at both of them synchronously. At my 
testing instance it was working as expected, I only had problems at the other 
instance, which made it that strange after all.
Thanks to you, Danilo, I renamed the dialog's control's name from "abstract" to 
"preamble" and now it is working on both instances, [b]thank you[/b]!

Anyway, I wonder why it was working for one instance only. I also took a look 
in the by Tomcat Catalina generated Java source code 
(/opt/magnolia-4.5.2/apache-tomcat-6.0.32/work/Catalina/localhost/magnoliaAuthor/org/apache/jsp/templates/components/ServicesParagraph_jsp.java)
 and couldn't figure out why this reserved keyword is any problem:

[code]_jspx_th_c_005fwhen_005f1.setTest(((java.lang.Boolean)
org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate("${not empty 
content.abstract}",
java.lang.Boolean.class, (PageContext)_jspx_page_context, null, 
false)).booleanValue());[/code]

"abstract" is part of a paramter, so basically it's a String and shouldn't 
cause any trouble.
I don't know.

But thank you anyway!

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=1f80a00e-c6cf-4bb9-a8fa-bdd17aa55c7b


----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to