Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.2 final
-
Fix Version/s: 1.2.1
-
Component/s: View technologies
-
Labels:None
-
Environment:Windows XP and Mac OS 10.6.2, Grails 1.2
-
Patch Submitted:Yes
Description
In the views for my applications, I take advantage of the <meta /> property setting furnished by Sitemesh.
I used to be able to do
<meta name="propertyName" value="${valueArg}"></meta>
in which <valueArg> could be of any type (e.g., a String or Timestamp).
Now, not only is an exception thrown when attempting to create a meta property of any type other than String (or GStringImpl, I suppose) (GrailsExceptionResolver), attempting to read a previously undefined property also triggers the exception (presumably because the in-view method pageProperty() creates a default, empty property when none existed prior).
"Previously undefined" means that I'm trying to use a meta property in a layout when that property was not initialized in a view partial.
Issue Links
| This issue is duplicated by: | ||||
| GRAILS-5723 | Sitemesh code is not updated to be aware of GSP optimization - using tag output for meta values passed to SiteMesh results in error |
|
|
|
Aaron,
Could you please attach a small simple project that demonstrates the behavior you are seeing?