[ http://issues.apache.org/jira/browse/MYFACES-434?page=comments#action_12362501 ]
Shinsuke SUGAYA commented on MYFACES-434: ----------------------------------------- For HeaderResource mechanism, please see HeaderResource interface(it's simple). init() is to initialize the instance, and addHeaderResources() is that portal server puts JavaScript and StyleSheet tags into <head>. To put tags into <head> is not defined in JSR 168. So, some portal servers might not have the mechanism to put tags to <head>. If so, you need to use Extensions Filter or the like. Basically this solution does not depend on Jetspeed. Since Jetspeed just have components in PortletContext, I added getter/setter method for PortletContext. If you need other parameters to implement it, please let me know. I'll add it to HeaderResource interface. > MyFaces's Portlet enhancement > ----------------------------- > > Key: MYFACES-434 > URL: http://issues.apache.org/jira/browse/MYFACES-434 > Project: MyFaces > Type: Improvement > Versions: 1.1.0 > Environment: LInux, J2SE 1.4.2 > Reporter: Shinsuke SUGAYA > Assignee: Stan Silvert > Attachments: filter051230.patch, filter051230.tar.gz, filterportlet.patch, > filterportlet.tar.gz, headerresource_for_j2.tar.gz, > newfile_for_portlet.tar.gz, patch_for_portlet.patch > > MyFacesGenericPortlet does not fully support the feature of tomahawk > component, such as inputHtml and fileUpload. So, I request the following > feature to run it on portlet: > - support tags in <head> (ex. inputHtml component) > - support upload (fileUpload component) -- 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
