You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Steve Olson (JIRA)" <ji...@apache.org> on 2006/12/18 02:24:57 UTC
[jira] Created: (SHALE-364) Tomahawk 1.1.3 component jscookmenu
does not render
Tomahawk 1.1.3 component jscookmenu does not render
---------------------------------------------------
Key: SHALE-364
URL: http://issues.apache.org/struts/browse/SHALE-364
Project: Shale
Issue Type: Bug
Components: Clay
Affects Versions: 1.0.3
Reporter: Steve Olson
Priority: Minor
t:jscookmenu and related t:navigationMenuItem components render to a default rendererType that results in a SubmitQuery button being rendered when using Clay. Also the Myfaces ExtensionsFilter does not include the appropriate javascript and related resources from the Tomahawk 1.1.3 jar for jscookmenu, as it should.
>From Gary VanMatre's reearch into this:
1 )The rendererType of the jscookMenu must be set to "org.apache.myfaces.JSCookMenu". This can be worked around by inheriting a new component and setting the missing attribute:
<component jsfid="t:myJscookMenu" extends="t:jscookMenu">
<attributes>
<set name="rendererType" value="org.apache.myfaces.JSCookMenu" />
</attributes>
</component>
2) The ClayViewHander is not explicitly setting the response's content type, and ExtensionsFilter requires this to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SHALE-364) Tomahawk 1.1.3 component jscookmenu
does not render
Posted by "Gary VanMatre (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/struts/browse/SHALE-364?page=all ]
Gary VanMatre resolved SHALE-364.
---------------------------------
Fix Version/s: 1.0.4-SNAPSHOT
Resolution: Fixed
Assignee: Gary VanMatre
There was a couple issue preventing the jscookmenu component from working in full clay views.
1) The jscookMenu component was missing a Clay xml configuration attribute that overrides the rendererType. The default was a command button renderer.
2) The ClayViewHandler was not explicitly setting the contentType of the response. The missing response content type was preventing the myfaces filter extension from adding javascript for the jscookMenu component.
Thanks for the help Steve. Please reopen this issue if you have other problems with the tomahawk jscookmenu component used with clay templates.
> Tomahawk 1.1.3 component jscookmenu does not render
> ---------------------------------------------------
>
> Key: SHALE-364
> URL: http://issues.apache.org/struts/browse/SHALE-364
> Project: Shale
> Issue Type: Bug
> Components: Clay
> Affects Versions: 1.0.3
> Reporter: Steve Olson
> Assigned To: Gary VanMatre
> Priority: Minor
> Fix For: 1.0.4-SNAPSHOT
>
>
> t:jscookmenu and related t:navigationMenuItem components render to a default rendererType that results in a SubmitQuery button being rendered when using Clay. Also the Myfaces ExtensionsFilter does not include the appropriate javascript and related resources from the Tomahawk 1.1.3 jar for jscookmenu, as it should.
> From Gary VanMatre's reearch into this:
> 1 )The rendererType of the jscookMenu must be set to "org.apache.myfaces.JSCookMenu". This can be worked around by inheriting a new component and setting the missing attribute:
> <component jsfid="t:myJscookMenu" extends="t:jscookMenu">
> <attributes>
> <set name="rendererType" value="org.apache.myfaces.JSCookMenu" />
> </attributes>
> </component>
> 2) The ClayViewHander is not explicitly setting the response's content type, and ExtensionsFilter requires this to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira