portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shinsuke SUGAYA (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Updated: (JS2-316) JSF Component javascript not being rendered
Date Thu, 28 Jul 2005 12:11:22 GMT
     [ http://issues.apache.org/jira/browse/JS2-316?page=all ]

Shinsuke SUGAYA updated JS2-316:

    Component: Demo Portlets
                   (was: MyFaces Portlet Bridge)

I'll add extended MyFacesGenericPortlet to handle HeaderResource component. Since this is
J2 specific portlet, it should not be added to portals-bridge. So, moved to Demo Portlets.

> JSF Component javascript not being rendered
> -------------------------------------------
>          Key: JS2-316
>          URL: http://issues.apache.org/jira/browse/JS2-316
>      Project: Jetspeed 2
>         Type: Bug
>   Components: Demo Portlets
>     Versions: 2.0-M3
>  Environment: Windows XP, Jakarta Tomcat 5.5.9, Jetspeed 2.0 M3, JDK 1.5.0_04, MyFaces
>     Reporter: Ronald Holshausen
>     Assignee: Shinsuke SUGAYA

> The x:swapImage component is not generating the link to it's javascript file. I had a
look at the myfaces render class for it (HtmlSwapImageRenderer), and it includes the following
> Line 57: AddResource.addJavaScriptToHeader(HtmlSwapImage.class, "swapimage.js", facesContext);

> I assume that the JSF framework will then add a link to this javascript file in the header.
But it is not being included in the portal page.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message