[jira] Updated: (MYFACES-1429) Remove rest of the portlet API references from the portlet util.

[ https://issues.apache.org/jira/browse/MYFACES-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Lee updated MYFACES-1429: - Status: Patch Available (was: Open) Remove rest of the portlet API references from the

[jira] Resolved: (TRINIDAD-1461) Build framework for jsr-276 metadata

[ https://issues.apache.org/jira/browse/TRINIDAD-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-1461. -- Resolution: Fixed Fix Version/s: 1.2.10-plugins Assignee:

Re: Connect my committer account to jira

done. Ganesh, Alexander, Michael, you are all three now member of the jira group myfaces committers --Manfred On Fri, May 1, 2009 at 12:03, Matthias Wessendorf mat...@apache.org wrote: Hello Manfred, can you do the jira-update for all the three new committers ? :-) Thanks! Matthias On

[jira] Commented: (ORCHESTRA-40) A transaction token component inspired by the struts transaction processor

[ https://issues.apache.org/jira/browse/ORCHESTRA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705595#action_12705595 ] Manfred Geiler commented on ORCHESTRA-40: - MANAGED_BEAN_NAME =

Re: [jira] Resolved: (TRINIDAD-1461) Build framework for jsr-276 metadata

Thanks for helping me with this.     bill Matthias Weßendorf (JIRA) wrote: [ https://issues.apache.org/jira/browse/TRINIDAD-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-1461. --

[jira] Created: (TRINIDAD-1466) Support xinclude'd property metadata

Support xinclude'd property metadata Key: TRINIDAD-1466 URL: https://issues.apache.org/jira/browse/TRINIDAD-1466 Project: MyFaces Trinidad Issue Type: Improvement Components: Build

[jira] Created: (TOMAHAWK-1419) CLONE -t:inputCalendar not working in IE

CLONE -t:inputCalendar not working in IE -- Key: TOMAHAWK-1419 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1419 Project: MyFaces Tomahawk Issue Type: Task Components: Calendar

[jira] Commented: (TRINIDAD-1466) Support xinclude'd property metadata

[ https://issues.apache.org/jira/browse/TRINIDAD-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705734#action_12705734 ] Andy Schwartz commented on TRINIDAD-1466: - Note: the patch file was created off

[jira] Commented: (TRINIDAD-1466) Support xinclude'd property metadata

[ https://issues.apache.org/jira/browse/TRINIDAD-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705736#action_12705736 ] Andy Schwartz commented on TRINIDAD-1466: - Verified that the same patch applies

[jira] Updated: (TRINIDAD-1466) Support xinclude'd property metadata

[ https://issues.apache.org/jira/browse/TRINIDAD-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Schwartz updated TRINIDAD-1466: Status: Patch Available (was: Open) Support xinclude'd property metadata

Re: h:head and h:body in JSF 2.0

Ganesh wrote: Hi, 3 more comments from Apache MyFaces development on the JSR 314 spec: [1] In the spec 2.6.2.1 h:head and h:body are silently indroduced as the JSF 2.0 way of rendering html head and body. It says The h:head and h:body tags refer to the renderers HeadRenderer and BodyRenderer

Re: [jira] Commented: (TRINIDAD-1109) Support non-standard user agents

Could you provide a sample jsp for your workaround? My Faces - Dev mailing list wrote: [ https://issues.apache.org/jira/browse/TRINIDAD-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668380#action_12668380 ] Jon Bullock commented on

Re: h:head and h:body in JSF 2.0

Ganesh wrote: [2] The jsdoc on javax.faces.response defines a behaviour for update elements with the id javax.faces.ViewRoot. By testing with the RI I found out that this behaviour is triggered if an AJAX requests triggers a naviagtion rule that leads to a different page. It's a cool thing to