[jira] Commented: (MYFACES-2935) SystemEvent Acid Test

2010-10-04 Thread Kennard Consulting (JIRA)
[ https://issues.apache.org/jira/browse/MYFACES-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917484#action_12917484 ] Kennard Consulting commented on MYFACES-2935: - Leonardo, Wow. Just wow. I

[RESULT] [VOTE] Release Tobago 1.0.30

2010-10-04 Thread Bernd Bohmann
The vote has passed with the following results: +1 werpu (binding) weber (binding) lofwyr (binding) bommel (binding) I will proceed with the next steps. Regards Bernd On Mon, Oct 4, 2010 at 2:32 PM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Here is my +1 Regards Bernd On Sun, Oct

[jira] Resolved: (EXTCDI-70) enhanced qualifier for add-ons

2010-10-04 Thread Gerhard Petracek (JIRA)
[ https://issues.apache.org/jira/browse/EXTCDI-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-70. Resolution: Fixed Fix Version/s: 1.0.0-SNAPSHOT enhanced qualifier for add-ons

Re: [VOTE] Release Tobago 1.0.30

2010-10-04 Thread Bernd Bohmann
Here is my +1 Regards Bernd On Sun, Oct 3, 2010 at 7:48 AM, Werner Punz werner.p...@gmail.com wrote: +1 Werner Bernd Bohmann bernd.bohm...@atanion.com wrote: Hello, I would like to release Tobago 1.0.30. For a detail list please consult the release notes:

[jira] Created: (EXTCDI-70) enhanced qualifier for add-ons

2010-10-04 Thread Gerhard Petracek (JIRA)
enhanced qualifier for add-ons -- Key: EXTCDI-70 URL: https://issues.apache.org/jira/browse/EXTCDI-70 Project: MyFaces CODI Issue Type: Improvement Components: Core Reporter: Gerhard

[jira] Resolved: (TRINIDAD-1932) Changes to UIXIterator break full visiting

2010-10-04 Thread Andrew Robinson (JIRA)
[ https://issues.apache.org/jira/browse/TRINIDAD-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Robinson resolved TRINIDAD-1932. --- Resolution: Fixed Fix Version/s: 1.2.12-core Changes to UIXIterator

Re: [jira] Created: (TRINIDAD-1930) Ability to easily create a meta tag

2010-10-04 Thread Blake Sullivan
I'm not sure that I'm a fan of this approach. Actually, I'm not a fan at all. 1) Our first choice should be for any agent-specific meta attributes to be generated by the document renderer 2) Any standard attributes that happen to be rendered as meta attributes should be exposed as document

Re: [jira] Created: (TRINIDAD-1930) Ability to easily create a meta tag

2010-10-04 Thread Matt Cooper
Hi Blake, How would you recommend exposing the configuration of the viewport metadata since it is agent-specific to iOS, Android, and Windows Mobile 7 agents? Thanks, Matt On Mon, Oct 4, 2010 at 10:16 AM, Blake Sullivan blake.sulli...@oracle.comwrote: I'm not sure that I'm a fan of this

[jira] Resolved: (MYFACES-2935) SystemEvent Acid Test

2010-10-04 Thread Leonardo Uribe (JIRA)
[ https://issues.apache.org/jira/browse/MYFACES-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2935. - Resolution: Fixed Fix Version/s: 2.0.3-SNAPSHOT Assignee: Leonardo

Re: [jira] Created: (TRINIDAD-1930) Ability to easily create a meta tag

2010-10-04 Thread Blake Sullivan
Trying again, since I got an error from the mail server. -- Blake On 10/4/10 11:25 AM, Blake Sullivan wrote: The document renderer should be delegating to the Agent implementation. This is essentially what happened in UIX, which is where the idea of the metacontainer facet came from (in

Re: [jira] Created: (TRINIDAD-1930) Ability to easily create a meta tag

2010-10-04 Thread Matt Cooper
I'd like to learn more about configuring Agents in UIX, is there any good documentation that you would recommend? (My quick searches for information about UIX or Trinidad Agent configuration has come up empty.) Thanks, Matt On Mon, Oct 4, 2010 at 12:43 PM, Blake Sullivan

[jira] Created: (MYFACES-2937) Change getApplicationObject function name to buildApplicationObject and move it to shared ClassUtils

2010-10-04 Thread Leonardo Uribe (JIRA)
Change getApplicationObject function name to buildApplicationObject and move it to shared ClassUtils Key: MYFACES-2937 URL:

[jira] Resolved: (MYFACES-2937) Change getApplicationObject function name to buildApplicationObject and move it to shared ClassUtils

2010-10-04 Thread Leonardo Uribe (JIRA)
[ https://issues.apache.org/jira/browse/MYFACES-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2937. - Resolution: Fixed Fix Version/s: 2.0.3-SNAPSHOT It was also added a class

[jira] Created: (MFCOMMONS-15) Move and document some very useful classes from shared to myfaces commons utils

2010-10-04 Thread Leonardo Uribe (JIRA)
Move and document some very useful classes from shared to myfaces commons utils --- Key: MFCOMMONS-15 URL: https://issues.apache.org/jira/browse/MFCOMMONS-15 Project: MyFaces

[jira] Created: (TRINIDAD-1933) Handling Windows Mobile 6.5 browser

2010-10-04 Thread Mamallan Uthaman (JIRA)
Handling Windows Mobile 6.5 browser --- Key: TRINIDAD-1933 URL: https://issues.apache.org/jira/browse/TRINIDAD-1933 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects

Re: [jira] Created: (TRINIDAD-1930) Ability to easily create a meta tag

2010-10-04 Thread Blake Sullivan
They worked mostly like the Agents in Trinidad do, since that's where the Trinidad Agents come from. I think that in this case, we actually had per-agent DocumentRenderer subclasses to handle agents that needed to output specific content. However, at least for XHTML content, I think we

[jira] Commented: (TRINIDAD-1922) In Facelets, Partial Refreshing tr:inputText Not Working

2010-10-04 Thread Pavitra Subramaniam (JIRA)
[ https://issues.apache.org/jira/browse/TRINIDAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917818#action_12917818 ] Pavitra Subramaniam commented on TRINIDAD-1922: --- With the above testcase I

Re: [jira] Created: (TRINIDAD-1930) Ability to easily create a meta tag

2010-10-04 Thread Blake Sullivan
On 10/4/10 2:07 PM, Matt Cooper wrote: That makes sense for the hard-coded/constant configuration pieces. However, the missing piece is the support for page-specific or even app-specific agent settings. I don't want to add new behavior to an agent with the risk of breaking applications or