You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Ian Priest (JIRA)" <ji...@apache.org> on 2007/06/26 23:54:27 UTC
[jira] Created: (SHALE-451) outputFormat ignores "escape" attribute
outputFormat ignores "escape" attribute
---------------------------------------
Key: SHALE-451
URL: https://issues.apache.org/struts/browse/SHALE-451
Project: Shale
Issue Type: Bug
Components: Clay
Affects Versions: 1.0.3
Reporter: Ian Priest
The "escape" attribute is missing from the definition of outputFormat in the clay-config.xml file in shale-clay-1.0.3.jar, causing the attribute to be ignored when used in the html.
My HTML is as follows...
<h:outputFormat escape="false" value="#{messages['myaccount$callhistory.moneycostcol.header']}">
<f:param value="#{@managed-bean-name.currencySymbol}" />
</h:outputFormat>
but I found that escape was defaulting to true. The definition for the tag in META-INF/clay-config.xml is:
<component jsfid="outputFormat" componentType="javax.faces.HtmlOutputFormat" extends="baseOutput">
<description>Render a readonly text value substituting inline string parameters. </description>
</component>
<component jsfid="h:outputFormat" extends="outputFormat"/>
I edited the META-INF/clay-config.xml file in shale-clay-1.0.3.jar to be as follows:
<component jsfid="outputFormat" componentType="javax.faces.HtmlOutputFormat" extends="baseOutput">
<description>Render a readonly text value substituting inline string parameters. </description>
<attributes>
<set name="escape" bindingType="VB">
<description></description>
</set>
</attributes>
</component>
<component jsfid="h:outputFormat" extends="outputFormat"/>
and now my esacpe attribute works correctly. Someone needs to make the change described above for the next release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHALE-451) outputFormat ignores "escape"
attribute
Posted by "Gary VanMatre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary VanMatre resolved SHALE-451.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0-SNAPSHOT
1.0.5-SNAPSHOT
Fix in the 20070728 nightly build.
> outputFormat ignores "escape" attribute
> ---------------------------------------
>
> Key: SHALE-451
> URL: https://issues.apache.org/struts/browse/SHALE-451
> Project: Shale
> Issue Type: Bug
> Components: Clay
> Affects Versions: 1.0.3
> Reporter: Ian Priest
> Assignee: Gary VanMatre
> Fix For: 1.0.5-SNAPSHOT, 1.1.0-SNAPSHOT
>
>
> The "escape" attribute is missing from the definition of outputFormat in the clay-config.xml file in shale-clay-1.0.3.jar, causing the attribute to be ignored when used in the html.
> My HTML is as follows...
> <h:outputFormat escape="false" value="#{messages['myaccount$callhistory.moneycostcol.header']}">
> <f:param value="#{@managed-bean-name.currencySymbol}" />
> </h:outputFormat>
> but I found that escape was defaulting to true. The definition for the tag in META-INF/clay-config.xml is:
> <component jsfid="outputFormat" componentType="javax.faces.HtmlOutputFormat" extends="baseOutput">
> <description>Render a readonly text value substituting inline string parameters. </description>
> </component>
> <component jsfid="h:outputFormat" extends="outputFormat"/>
> I edited the META-INF/clay-config.xml file in shale-clay-1.0.3.jar to be as follows:
> <component jsfid="outputFormat" componentType="javax.faces.HtmlOutputFormat" extends="baseOutput">
> <description>Render a readonly text value substituting inline string parameters. </description>
> <attributes>
> <set name="escape" bindingType="VB">
> <description></description>
> </set>
> </attributes>
> </component>
> <component jsfid="h:outputFormat" extends="outputFormat"/>
> and now my esacpe attribute works correctly. Someone needs to make the change described above for the next release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SHALE-451) outputFormat ignores "escape"
attribute
Posted by "Gary VanMatre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary VanMatre reassigned SHALE-451:
-----------------------------------
Assignee: Gary VanMatre
> outputFormat ignores "escape" attribute
> ---------------------------------------
>
> Key: SHALE-451
> URL: https://issues.apache.org/struts/browse/SHALE-451
> Project: Shale
> Issue Type: Bug
> Components: Clay
> Affects Versions: 1.0.3
> Reporter: Ian Priest
> Assignee: Gary VanMatre
>
> The "escape" attribute is missing from the definition of outputFormat in the clay-config.xml file in shale-clay-1.0.3.jar, causing the attribute to be ignored when used in the html.
> My HTML is as follows...
> <h:outputFormat escape="false" value="#{messages['myaccount$callhistory.moneycostcol.header']}">
> <f:param value="#{@managed-bean-name.currencySymbol}" />
> </h:outputFormat>
> but I found that escape was defaulting to true. The definition for the tag in META-INF/clay-config.xml is:
> <component jsfid="outputFormat" componentType="javax.faces.HtmlOutputFormat" extends="baseOutput">
> <description>Render a readonly text value substituting inline string parameters. </description>
> </component>
> <component jsfid="h:outputFormat" extends="outputFormat"/>
> I edited the META-INF/clay-config.xml file in shale-clay-1.0.3.jar to be as follows:
> <component jsfid="outputFormat" componentType="javax.faces.HtmlOutputFormat" extends="baseOutput">
> <description>Render a readonly text value substituting inline string parameters. </description>
> <attributes>
> <set name="escape" bindingType="VB">
> <description></description>
> </set>
> </attributes>
> </component>
> <component jsfid="h:outputFormat" extends="outputFormat"/>
> and now my esacpe attribute works correctly. Someone needs to make the change described above for the next release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.