Re: [jira] Commented: (JSR301-2) Coding Standards: This project should adopt coding standards similar to MyFaces for consistancy

I like the Exceptions section in the Geronimo Coding standards very much. We should have these rules in our conventions as well. Hope they are open source... ;-) There is just one issue I would not recommend due to personal experience: Abbreviations and Acronyms should *always* appear in

[jira] Commented: (TRINIDAD-144) AJAX client validation creates blank space underneath inputs in IE6

[ https://issues.apache.org/jira/browse/TRINIDAD-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531458 ] Darren McEntee commented on TRINIDAD-144: - Hi, Is there any update in this issue as we need to get it

[jira] Commented: (TOBAGO-497) Tree-Selection causes no submit

[ https://issues.apache.org/jira/browse/TOBAGO-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531492 ] Helmut Swaczinna commented on TOBAGO-497: - You can use a treeNodeCommand facet to specify the action to be

[jira] Commented: (TOBAGO-497) Tree-Selection causes no submit

[ https://issues.apache.org/jira/browse/TOBAGO-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531508 ] Bernd Bohmann commented on TOBAGO-497: -- If someone depends on this feature. Someone would not expect such

[jira] Commented: (TOMAHAWK-602) try to replace the anchor tag of an unselected entry to a div tag

[ https://issues.apache.org/jira/browse/TOMAHAWK-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531520 ] Björn Voß commented on TOMAHAWK-602: this will also solve a problem with the anchor tag if you use the a

[jira] Commented: (TOMAHAWK-128) Incorrect inputCalendar position when placed in DIV tag with position: absolute;

[ https://issues.apache.org/jira/browse/TOMAHAWK-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531538 ] Thiago D. Freitas commented on TOMAHAWK-128: How to install this patch on my tomahawk? Incorrect

[jira] Created: (MYFACES-1738) invokeOnComponent returns wrong reference for UIData children

invokeOnComponent returns wrong reference for UIData children - Key: MYFACES-1738 URL: https://issues.apache.org/jira/browse/MYFACES-1738 Project: MyFaces Core Issue Type: Bug

[jira] Commented: (TRINIDAD-713) Using name as the id for a component breaks form submission. name appears to be an undocumented reserved identifier.

[ https://issues.apache.org/jira/browse/TRINIDAD-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531594 ] Mike Hanafey commented on TRINIDAD-713: --- Could someone comment on this issue? Is name and invalid value for

[jira] Commented: (MYFACES-1738) invokeOnComponent returns wrong reference for UIData children

[ https://issues.apache.org/jira/browse/MYFACES-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531596 ] Leonardo Uribe commented on MYFACES-1738: - It's not a bug. UIData use the same components to render each

[TRINIDAD] Build error on latest nightly build

Hi all, I cannot build the current Trinidad trunk. The compilation error is pretty straightforward, but there's also a renderkit test error. Anyone can confirm this or is it just me? And if anyone else can confirm, how come Continuum didn't warn us? ~ Simon

Re: [TRINIDAD] Build error on latest nightly build

I just did an update and tried to build: Also getting a compile error in ChildPropertyTreeModel. If I locally rollback that file to the previous revision, then mvn clean install works fine, though. No test failures. Simon Lessard wrote: Hi all, I cannot build the current Trinidad trunk. The

Re: [TRINIDAD] Build error on latest nightly build

Thanks Stephen, So it's not on my side only this time. The compile error is 2 missing imports that was introduced with last commit, but the test error (on treeTable) seems older. I'll fix the compile issue since it's pretty simple. I cannot really search for the test failure atm however. ~ Simon

[jira] Created: (TRINIDAD-748) Client-side DateTimeRangeValidator does not handle differences in timezone

Client-side DateTimeRangeValidator does not handle differences in timezone -- Key: TRINIDAD-748 URL: https://issues.apache.org/jira/browse/TRINIDAD-748 Project: MyFaces Trinidad

Re: [TRINIDAD] Build error on latest nightly build

Unfortunately, this was my mistake. I merged my code in from a different file and apparently forgot the imports. Being late at night, I must have compiled the wrong source to verify correctness. On 10/1/07, Simon Lessard [EMAIL PROTECTED] wrote: Thanks Stephen, So it's not on my side only this

[jira] Created: (TRINIDAD-750) PPR does not R: Table rows are not refreshed

PPR does not R: Table rows are not refreshed Key: TRINIDAD-750 URL: https://issues.apache.org/jira/browse/TRINIDAD-750 Project: MyFaces Trinidad Issue Type: Bug Reporter: Stephen

[jira] Created: (TRINIDAD-749) Launching modal dialog when the launcher window body has position:absolute in IE makes launcher page look corrupt

Launching modal dialog when the launcher window body has position:absolute in IE makes launcher page look corrupt - Key: TRINIDAD-749 URL:

[jira] Commented: (TRINIDAD-750) PPR does not R: Table rows are not refreshed

[ https://issues.apache.org/jira/browse/TRINIDAD-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531642 ] Stephen Friedrich commented on TRINIDAD-750: No Jira macors enabled?! PPR does not R: Table rows are

[jira] Created: (TOMAHAWK-1124) ExtensionFilter throws NoClassDefFoundError when used with Myfaces 1.2.x and JBoss 4.2.1

ExtensionFilter throws NoClassDefFoundError when used with Myfaces 1.2.x and JBoss 4.2.1 Key: TOMAHAWK-1124 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1124

[jira] Commented: (TRINIDAD-750) PPR does not R: Table rows are not refreshed

[ https://issues.apache.org/jira/browse/TRINIDAD-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531654 ] Stephen Friedrich commented on TRINIDAD-750: After further research: It is not caused by PPR, but by

required icon after label: How to best implement skinning?

I have just changed the OutputLabelRenderer to optionally render the required icon _after_ the label. How should I implement skinning for that? (Currently I check a system property, that I set in my test code.) What is the practical difference between defining a new skinning property vs. a

Re: required icon after label: How to best implement skinning?

Hello Stephen, This is definitely a skin property case, not per component. There's no strict rule though. About the name, maybe -tr-required-icon-position? ~ Simon On 10/1/07, Stephen Friedrich [EMAIL PROTECTED] wrote: I have just changed the OutputLabelRenderer to optionally render the