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] Closed: (JS2-316) JSF Component javascript not being rendered
Date Thu, 14 Sep 2006 03:36:22 GMT
     [ http://issues.apache.org/jira/browse/JS2-316?page=all ]

Shinsuke SUGAYA closed JS2-316.

    Resolution: Won't Fix

I put my comment to MYFACES-434. 
If you use MyFaces Bridge 0.8 I provided, you can use Tomahawk's portlet on J2. So, J2 does
not need to take care of this issue. If you have any problems and comments, let me know.

> JSF Component javascript not being rendered
> -------------------------------------------
>                 Key: JS2-316
>                 URL: http://issues.apache.org/jira/browse/JS2-316
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Demo Portlets
>    Affects Versions: 2.0-M3
>         Environment: Windows XP, Jakarta Tomcat 5.5.9, Jetspeed 2.0 M3, JDK 1.5.0_04,
MyFaces 1.09
>            Reporter: Ronald Holshausen
>         Assigned To: Shinsuke SUGAYA
>             Fix For: 2.1
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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

View raw message