[jira] [Commented] (TRINIDAD-2172) pseudo classes missing from CSSGenerationUtils
[ https://issues.apache.org/jira/browse/TRINIDAD-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402000#comment-13402000 ] Anand V Nath commented on TRINIDAD-2172: Nested pseudo classes were not handled in the initial fix. Patch uploaded for handling this (jira-2172-not-pseudo-fix.patch) Please reopen this bug and commit the patch. pseudo classes missing from CSSGenerationUtils -- Key: TRINIDAD-2172 URL: https://issues.apache.org/jira/browse/TRINIDAD-2172 Project: MyFaces Trinidad Issue Type: Improvement Components: Skinning Affects Versions: 2.0.0-core Reporter: Jeremy C. Hull Assignee: Scott O'Bryan Fix For: 2.0.1-core Attachments: bug-13253267-3.patch, jira-2172-not-pseudo-fix.patch Only the following built-in pseudo classes are handled _BUILT_IN_PSEUDO_CLASSES.add(:first-child); _BUILT_IN_PSEUDO_CLASSES.add(:link); _BUILT_IN_PSEUDO_CLASSES.add(:visited); _BUILT_IN_PSEUDO_CLASSES.add(:hover); _BUILT_IN_PSEUDO_CLASSES.add(:active); _BUILT_IN_PSEUDO_CLASSES.add(:focus); There are a few CSS2.1 and a bunch of CSS3 pseudo classes that should be handled. first-letter, first-line, only-child, last-child, nth-child, nth-child-of-type, etc... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2282) In validateLength, a default hintRange message is displayed instead of hintMaximum even when minimum value is not set
Anshu Jain created TRINIDAD-2282:
Summary: In validateLength, a default hintRange message is
displayed instead of hintMaximum even when minimum value is not set
Key: TRINIDAD-2282
URL: https://issues.apache.org/jira/browse/TRINIDAD-2282
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 2.0.0-beta-2
Environment: JDeveloper 11.1.2.0.0
Reporter: Anshu Jain
af:validateLength is used for a input text box. The maximum value is set and
minimum value is not set. Which means by default minimum is 0.
The hintMaximum is set to {0} is maximum allowed and hintRange is set to {0}
is minimum, {1} is maximum
When the user clicks on the the given text box, hintMaximum should be displayed.
Instead a default message: Enter between 0 and 3 characters. is displayed.
hintMaximum should be displayed in this scenario.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (TRINIDAD-2172) pseudo classes missing from CSSGenerationUtils
Hello, Please review and commit the patch attached in the jira issue (jira-2172-not-pseudo-fix.patch). Thanks Anand On 6/27/2012 12:27 PM, Anand V Nath (JIRA) wrote: [ https://issues.apache.org/jira/browse/TRINIDAD-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402000#comment-13402000 ] Anand V Nath commented on TRINIDAD-2172: Nested pseudo classes were not handled in the initial fix. Patch uploaded for handling this (jira-2172-not-pseudo-fix.patch) Please reopen this bug and commit the patch. pseudo classes missing from CSSGenerationUtils -- Key: TRINIDAD-2172 URL: https://issues.apache.org/jira/browse/TRINIDAD-2172 Project: MyFaces Trinidad Issue Type: Improvement Components: Skinning Affects Versions: 2.0.0-core Reporter: Jeremy C. Hull Assignee: Scott O'Bryan Fix For: 2.0.1-core Attachments: bug-13253267-3.patch, jira-2172-not-pseudo-fix.patch Only the following built-in pseudo classes are handled _BUILT_IN_PSEUDO_CLASSES.add(:first-child); _BUILT_IN_PSEUDO_CLASSES.add(:link); _BUILT_IN_PSEUDO_CLASSES.add(:visited); _BUILT_IN_PSEUDO_CLASSES.add(:hover); _BUILT_IN_PSEUDO_CLASSES.add(:active); _BUILT_IN_PSEUDO_CLASSES.add(:focus); There are a few CSS2.1 and a bunch of CSS3 pseudo classes that should be handled. first-letter, first-line, only-child, last-child, nth-child, nth-child-of-type, etc... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TRINIDAD-2277) input date popup does not open when using IE 9
[
https://issues.apache.org/jira/browse/TRINIDAD-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated TRINIDAD-2277:
-
Status: Patch Available (was: Open)
input date popup does not open when using IE 9
--
Key: TRINIDAD-2277
URL: https://issues.apache.org/jira/browse/TRINIDAD-2277
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Reporter: Leonardo Uribe
Attachments: TRINIDAD-2277-1.patch
Checking the showcase:
http://example.irian.at/trinidad-components-showcase/component-demo/inputDate-Detailed
also with the latest build I can see this error using IE 9 (9.0.8112.16421)
SCRIPT5007: Für die Eigenschaft body kann kein Wert abgerufen werden: Das
Objekt ist Null oder undefiniert
DebugCommon1_2_15.js, Zeile 15623 Zeichen 7
Related js:
if (!dialog._fixedSize)
{
if (_agent.isIE)
{
dialog._resizeIFrame(
dialog._iframe.Document.body.scrollWidth+40,
dialog._iframe.Document.body.scrollHeight+40);
}
else
The popup does not open. Using firefox or chrome it works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TRINIDAD-2277) input date popup does not open when using IE 9
[
https://issues.apache.org/jira/browse/TRINIDAD-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402071#comment-13402071
]
Leonardo Uribe commented on TRINIDAD-2277:
--
Yes it is legitimate. I'm able to reproduce it and debug it. I found a simple
solution to this one. Just set fixed dimensions in DateField.js _ldp function,
when IE9 is used.
Obviously that's not a complete patch, because anyway a more general culprit
should be done in PopupDialog.js
But I notice that the reason why in IE9 the popup fills the whole screen is
because dialog._iframe.document.body.scrollWidth and
dialog._iframe.Document.body.scrollHeight returns too big values (maybe related
to the window size). So, the question is if we can use something else to set
the default dimensions for a popup in IE9.
Anyway, the fix suggested sounds reasonable.
input date popup does not open when using IE 9
--
Key: TRINIDAD-2277
URL: https://issues.apache.org/jira/browse/TRINIDAD-2277
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Reporter: Leonardo Uribe
Checking the showcase:
http://example.irian.at/trinidad-components-showcase/component-demo/inputDate-Detailed
also with the latest build I can see this error using IE 9 (9.0.8112.16421)
SCRIPT5007: Für die Eigenschaft body kann kein Wert abgerufen werden: Das
Objekt ist Null oder undefiniert
DebugCommon1_2_15.js, Zeile 15623 Zeichen 7
Related js:
if (!dialog._fixedSize)
{
if (_agent.isIE)
{
dialog._resizeIFrame(
dialog._iframe.Document.body.scrollWidth+40,
dialog._iframe.Document.body.scrollHeight+40);
}
else
The popup does not open. Using firefox or chrome it works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TOBAGO-1165) Layout Manager: preferred value must not be more significant than current value
Udo Schnurpfeil created TOBAGO-1165: --- Summary: Layout Manager: preferred value must not be more significant than current value Key: TOBAGO-1165 URL: https://issues.apache.org/jira/browse/TOBAGO-1165 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.5.6, 1.5.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil When laying out using the auto attribute and there is a current width or height set, this value should be used to compute the free space, and not the preferred value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1165) Layout Manager: preferred value must not be more significant than current value
[ https://issues.apache.org/jira/browse/TOBAGO-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402099#comment-13402099 ] Udo Schnurpfeil commented on TOBAGO-1165: - This is the reason why there is so much space in tabGroup-auto-auto.xhtml Layout Manager: preferred value must not be more significant than current value --- Key: TOBAGO-1165 URL: https://issues.apache.org/jira/browse/TOBAGO-1165 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil When laying out using the auto attribute and there is a current width or height set, this value should be used to compute the free space, and not the preferred value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1162) Missing accesskey support in tc:selectBooleanCheckbox
[ https://issues.apache.org/jira/browse/TOBAGO-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402102#comment-13402102 ] Hudson commented on TOBAGO-1162: Integrated in tobago-1.5.x #51 (See [https://builds.apache.org/job/tobago-1.5.x/51/]) Merged from trunk (TOBAGO-1162) Missing accessKey support in tc:selectBooleanCheckbox [from revision 1353071] (Revision 1353208) Result = FAILURE bommel : http://svn.apache.org/viewvc/?view=revrev=1353208 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/SelectBooleanCheckboxRenderer.java Missing accesskey support in tc:selectBooleanCheckbox - Key: TOBAGO-1162 URL: https://issues.apache.org/jira/browse/TOBAGO-1162 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1154) Show a warning, if there is no JavaScript activated.
[ https://issues.apache.org/jira/browse/TOBAGO-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402100#comment-13402100 ] Hudson commented on TOBAGO-1154: Integrated in tobago-1.5.x #51 (See [https://builds.apache.org/job/tobago-1.5.x/51/]) TOBAGO-1154: Show a warning, if there is no JavaScript activated. spelling (Revision 1351958) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1351958 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/resources/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/property/tobago_de.properties.xml * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/resources/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/property/tobago_es.properties.xml Show a warning, if there is no JavaScript activated. Key: TOBAGO-1154 URL: https://issues.apache.org/jira/browse/TOBAGO-1154 Project: MyFaces Tobago Issue Type: Improvement Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.6.0-beta-2, 1.5.7, 1.0.40, 1.6.0 Tobago doesn't work without JavaScript. The browser should warn the user, if no JavaScript is available. Using the NOSCRIPT tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1160) AJAX reload blocks reloaded area
[ https://issues.apache.org/jira/browse/TOBAGO-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402101#comment-13402101 ] Hudson commented on TOBAGO-1160: Integrated in tobago-1.5.x #51 (See [https://builds.apache.org/job/tobago-1.5.x/51/]) TOBAGO-1160: AJAX reload blocks reloaded area - fix: using iframe only in ie6 (not ie7, ie8, ...) - fix: removing iframe - fix: do not create 2nd iframe Merged from trunk [from revision 1352820] (Revision 1352886) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352886 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js AJAX reload blocks reloaded area Key: TOBAGO-1160 URL: https://issues.apache.org/jira/browse/TOBAGO-1160 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Environment: Internet Explorer only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Critical Fix For: 1.6.0-beta-2, 1.5.7 e.g.: use reload facet with update=false in the demo sheet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1138) Avoid using String.replace inside ResponseWriter
[ https://issues.apache.org/jira/browse/TOBAGO-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402103#comment-13402103 ] Hudson commented on TOBAGO-1138: Integrated in tobago-1.5.x #51 (See [https://builds.apache.org/job/tobago-1.5.x/51/]) Merged from trunk (TOBAGO-1138) Avoid using String.replace inside ResponseWriter [from revision 1354247] (Revision 1354248) Result = FAILURE bommel : http://svn.apache.org/viewvc/?view=revrev=1354248 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/util/JavascriptWriterUtils.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/test/java/org/apache/myfaces/tobago/util/JavascriptWriterUtilsTest.java Avoid using String.replace inside ResponseWriter Key: TOBAGO-1138 URL: https://issues.apache.org/jira/browse/TOBAGO-1138 Project: MyFaces Tobago Issue Type: Improvement Components: Core, Themes Affects Versions: 1.5.6 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Fix For: 1.6.0-beta-1, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1161) Double AJAX request shows an error in the area
[ https://issues.apache.org/jira/browse/TOBAGO-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402104#comment-13402104 ] Hudson commented on TOBAGO-1161: Integrated in tobago-1.5.x #51 (See [https://builds.apache.org/job/tobago-1.5.x/51/]) TOBAGO-1161: Double AJAX request shows an error in the area Merged from trunk [from revision 1352824] (Revision 1352887) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352887 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js Double AJAX request shows an error in the area -- Key: TOBAGO-1161 URL: https://issues.apache.org/jira/browse/TOBAGO-1161 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1165) Layout Manager: preferred value must not be more significant than current value
[ https://issues.apache.org/jira/browse/TOBAGO-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402112#comment-13402112 ] Hudson commented on TOBAGO-1165: Integrated in tobago-trunk #805 (See [https://builds.apache.org/job/tobago-trunk/805/]) TOBAGO-1165: Layout Manager: preferred value must not be more significant than current value (Revision 1354395) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354395 Files : * /myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/layout/IntervalList.java * /myfaces/tobago/trunk/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto-auto.xhtml * /myfaces/tobago/trunk/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto.xhtml * /myfaces/tobago/trunk/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-relative.xhtml Layout Manager: preferred value must not be more significant than current value --- Key: TOBAGO-1165 URL: https://issues.apache.org/jira/browse/TOBAGO-1165 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil When laying out using the auto attribute and there is a current width or height set, this value should be used to compute the free space, and not the preferred value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1164) Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height
[ https://issues.apache.org/jira/browse/TOBAGO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402135#comment-13402135 ] Udo Schnurpfeil commented on TOBAGO-1164: - When having a sheet in the tab, you got an error message in the log file: no height in parent container, setting to 100 Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height -- Key: TOBAGO-1164 URL: https://issues.apache.org/jira/browse/TOBAGO-1164 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Ralph Jacobs Assignee: Udo Schnurpfeil In this example tc:sheet will be displayed with a height of 63 pixels although it should be rendered according to its rows setting. The surrounding tc:tab gets the correct height. tc:panel id=layout-panel f:facet name=layout tc:gridLayout rows=auto / /f:facet tc:tabGroup tc:tab tc:sheetcolumns=*;* ... /tc:sheet /tc:tab /tc:tabGroup /tc:panel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1160) AJAX reload blocks reloaded area
[ https://issues.apache.org/jira/browse/TOBAGO-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402138#comment-13402138 ] Hudson commented on TOBAGO-1160: Integrated in tobago-1.5.x #52 (See [https://builds.apache.org/job/tobago-1.5.x/52/]) TOBAGO-1160: AJAX reload blocks reloaded area - fix: using iframe only in ie6 (not ie7, ie8, ...) - fix: removing iframe - fix: do not create 2nd iframe Merged from trunk [from revision 1352820] (Revision 1352886) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352886 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js AJAX reload blocks reloaded area Key: TOBAGO-1160 URL: https://issues.apache.org/jira/browse/TOBAGO-1160 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Environment: Internet Explorer only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Critical Fix For: 1.6.0-beta-2, 1.5.7 e.g.: use reload facet with update=false in the demo sheet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1165) Layout Manager: preferred value must not be more significant than current value
[ https://issues.apache.org/jira/browse/TOBAGO-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402137#comment-13402137 ] Hudson commented on TOBAGO-1165: Integrated in tobago-1.5.x #52 (See [https://builds.apache.org/job/tobago-1.5.x/52/]) TOBAGO-1165: Layout Manager: preferred value must not be more significant than current value Merged from trunk [from revision 1354395] (Revision 1354396) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354396 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/layout/IntervalList.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto-auto.xhtml * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto.xhtml * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-relative.xhtml Layout Manager: preferred value must not be more significant than current value --- Key: TOBAGO-1165 URL: https://issues.apache.org/jira/browse/TOBAGO-1165 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil When laying out using the auto attribute and there is a current width or height set, this value should be used to compute the free space, and not the preferred value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1161) Double AJAX request shows an error in the area
[ https://issues.apache.org/jira/browse/TOBAGO-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402141#comment-13402141 ] Hudson commented on TOBAGO-1161: Integrated in tobago-1.5.x #52 (See [https://builds.apache.org/job/tobago-1.5.x/52/]) TOBAGO-1161: Double AJAX request shows an error in the area Merged from trunk [from revision 1352824] (Revision 1352887) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352887 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js Double AJAX request shows an error in the area -- Key: TOBAGO-1161 URL: https://issues.apache.org/jira/browse/TOBAGO-1161 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1162) Missing accesskey support in tc:selectBooleanCheckbox
[ https://issues.apache.org/jira/browse/TOBAGO-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402139#comment-13402139 ] Hudson commented on TOBAGO-1162: Integrated in tobago-1.5.x #52 (See [https://builds.apache.org/job/tobago-1.5.x/52/]) Merged from trunk (TOBAGO-1162) Missing accessKey support in tc:selectBooleanCheckbox [from revision 1353071] (Revision 1353208) Result = SUCCESS bommel : http://svn.apache.org/viewvc/?view=revrev=1353208 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/SelectBooleanCheckboxRenderer.java Missing accesskey support in tc:selectBooleanCheckbox - Key: TOBAGO-1162 URL: https://issues.apache.org/jira/browse/TOBAGO-1162 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1138) Avoid using String.replace inside ResponseWriter
[ https://issues.apache.org/jira/browse/TOBAGO-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402140#comment-13402140 ] Hudson commented on TOBAGO-1138: Integrated in tobago-1.5.x #52 (See [https://builds.apache.org/job/tobago-1.5.x/52/]) Merged from trunk (TOBAGO-1138) Avoid using String.replace inside ResponseWriter [from revision 1354247] (Revision 1354248) Result = SUCCESS bommel : http://svn.apache.org/viewvc/?view=revrev=1354248 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/util/JavascriptWriterUtils.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/test/java/org/apache/myfaces/tobago/util/JavascriptWriterUtilsTest.java Avoid using String.replace inside ResponseWriter Key: TOBAGO-1138 URL: https://issues.apache.org/jira/browse/TOBAGO-1138 Project: MyFaces Tobago Issue Type: Improvement Components: Core, Themes Affects Versions: 1.5.6 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Fix For: 1.6.0-beta-1, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1164) Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height
[ https://issues.apache.org/jira/browse/TOBAGO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402142#comment-13402142 ] Udo Schnurpfeil commented on TOBAGO-1164: - The bug is for both dimesions: for width and height. The reason is, that the AbstractUITabGroupLayout doesn't call the mainProcessing recursively, in the case of auto-layout. Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height -- Key: TOBAGO-1164 URL: https://issues.apache.org/jira/browse/TOBAGO-1164 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Ralph Jacobs Assignee: Udo Schnurpfeil In this example tc:sheet will be displayed with a height of 63 pixels although it should be rendered according to its rows setting. The surrounding tc:tab gets the correct height. tc:panel id=layout-panel f:facet name=layout tc:gridLayout rows=auto / /f:facet tc:tabGroup tc:tab tc:sheetcolumns=*;* ... /tc:sheet /tc:tab /tc:tabGroup /tc:panel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOBAGO-1165) Layout Manager: preferred value must not be more significant than current value
[ https://issues.apache.org/jira/browse/TOBAGO-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1165. - Resolution: Fixed Fix Version/s: 1.6.0-beta-3 1.5.7 Layout Manager: preferred value must not be more significant than current value --- Key: TOBAGO-1165 URL: https://issues.apache.org/jira/browse/TOBAGO-1165 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 When laying out using the auto attribute and there is a current width or height set, this value should be used to compute the free space, and not the preferred value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOBAGO-1164) Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height
[ https://issues.apache.org/jira/browse/TOBAGO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Jacobs resolved TOBAGO-1164. -- Resolution: Fixed Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height -- Key: TOBAGO-1164 URL: https://issues.apache.org/jira/browse/TOBAGO-1164 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Ralph Jacobs Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 In this example tc:sheet will be displayed with a height of 63 pixels although it should be rendered according to its rows setting. The surrounding tc:tab gets the correct height. tc:panel id=layout-panel f:facet name=layout tc:gridLayout rows=auto / /f:facet tc:tabGroup tc:tab tc:sheetcolumns=*;* ... /tc:sheet /tc:tab /tc:tabGroup /tc:panel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1164) Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height
[ https://issues.apache.org/jira/browse/TOBAGO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402172#comment-13402172 ] Hudson commented on TOBAGO-1164: Integrated in tobago-1.5.x #53 (See [https://builds.apache.org/job/tobago-1.5.x/53/]) TOBAGO-1164: Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height Merged from trunk [from revision 1354437] (Revision 1354440) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354440 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUITabGroupLayout.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/tabGroup/tabGroup-layout-1164.xhtml Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height -- Key: TOBAGO-1164 URL: https://issues.apache.org/jira/browse/TOBAGO-1164 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Ralph Jacobs Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 In this example tc:sheet will be displayed with a height of 63 pixels although it should be rendered according to its rows setting. The surrounding tc:tab gets the correct height. tc:panel id=layout-panel f:facet name=layout tc:gridLayout rows=auto / /f:facet tc:tabGroup tc:tab tc:sheetcolumns=*;* ... /tc:sheet /tc:tab /tc:tabGroup /tc:panel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1164) Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height
[ https://issues.apache.org/jira/browse/TOBAGO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402176#comment-13402176 ] Hudson commented on TOBAGO-1164: Integrated in tobago-trunk #806 (See [https://builds.apache.org/job/tobago-trunk/806/]) TOBAGO-1164: Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height (Revision 1354437) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354437 Files : * /myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUITabGroupLayout.java * /myfaces/tobago/trunk/tobago-example/tobago-example-test/src/main/webapp/tc/tabGroup/tabGroup-layout-1164.xhtml Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height -- Key: TOBAGO-1164 URL: https://issues.apache.org/jira/browse/TOBAGO-1164 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.0-beta-2, 1.5.6 Reporter: Ralph Jacobs Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 In this example tc:sheet will be displayed with a height of 63 pixels although it should be rendered according to its rows setting. The surrounding tc:tab gets the correct height. tc:panel id=layout-panel f:facet name=layout tc:gridLayout rows=auto / /f:facet tc:tabGroup tc:tab tc:sheetcolumns=*;* ... /tc:sheet /tc:tab /tc:tabGroup /tc:panel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MYFACES-3576) [perf] use get() over eval() for UIViewRoot.getViewId()
Leonardo Uribe created MYFACES-3576:
---
Summary: [perf] use get() over eval() for UIViewRoot.getViewId()
Key: MYFACES-3576
URL: https://issues.apache.org/jira/browse/MYFACES-3576
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-314
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
Priority: Trivial
Checking some code I saw this line:
public String getViewId()
{
return (String) getStateHelper().eval(PropertyKeys.viewId);
}
A viewId can never be a ValueExpression! The viewId is a value that identifies
the view in a unique way and it is set according to the rules of the spec. It
is possible to change the line and use get() instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MYFACES-3576) [perf] use get() over eval() for UIViewRoot.getViewId()
[
https://issues.apache.org/jira/browse/MYFACES-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3576.
-
Resolution: Fixed
Fix Version/s: 2.1.9
2.0.15
[perf] use get() over eval() for UIViewRoot.getViewId()
---
Key: MYFACES-3576
URL: https://issues.apache.org/jira/browse/MYFACES-3576
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-314
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
Priority: Trivial
Fix For: 2.0.15, 2.1.9
Checking some code I saw this line:
public String getViewId()
{
return (String) getStateHelper().eval(PropertyKeys.viewId);
}
A viewId can never be a ValueExpression! The viewId is a value that
identifies the view in a unique way and it is set according to the rules of
the spec. It is possible to change the line and use get() instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1107) Using a TreeState object instead of expanded and marked in the tree node tag
[ https://issues.apache.org/jira/browse/TOBAGO-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402205#comment-13402205 ] Hudson commented on TOBAGO-1107: Integrated in tobago-trunk #807 (See [https://builds.apache.org/job/tobago-trunk/807/]) TOBAGO-1107: Using a TreeState object instead of expanded and marked in the tree node tag - do not update expanded state, if the field wasn't sent. (Revision 1354456) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354456 Files : * /myfaces/tobago/trunk/tobago-theme/tobago-theme-standard/src/main/java/org/apache/myfaces/tobago/renderkit/util/RenderUtils.java Using a TreeState object instead of expanded and marked in the tree node tag - Key: TOBAGO-1107 URL: https://issues.apache.org/jira/browse/TOBAGO-1107 Project: MyFaces Tobago Issue Type: Task Components: Core Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.6.0-beta-1, 1.6.0 The expanded and marked state was saved in the tree model directly since Tobago 1.5.0. But it turns out, that has some disadvantages: - to handle the state, you may have to write extra code to save the state - usually this code is only for presenation (expanded), so you mix data and presentation So introducing the TreeState. The TreeState shoud be independet from tree model implementations. It saves the path a node, instead of the node themself. This is different to the TreeState of Tobago 1.0.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402208#comment-13402208 ] Dmitry Kukushkin commented on MYFACES-3575: --- Still no good, using 2.1.8. My problem is that in public Facelet getFacelet(String uri) relative location is unconditionally cached, while in my case _resolver.resolveUrl(path) can return different URLs for the same path, depending on the application's internal state. The caching of the outcome of _resolver.resolveUrl(path) breaks this. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kukushkin reopened MYFACES-3575: --- Still no good, using 2.1.8. My problem is that in public Facelet getFacelet(String uri) relative location is unconditionally cached, while in my case _resolver.resolveUrl(path) can return different URLs for the same path, depending on the application's internal state. The caching of the outcome of _resolver.resolveUrl(path) breaks this. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402228#comment-13402228 ] Leonardo Uribe commented on MYFACES-3575: - Now I get it what you want. I don't think it could be possible, because this quickly leads to inconsistencies. Maybe what you are looking for is PrettyFaces, which allows to rewrite the url based on different conditions. No need to do anything here. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402236#comment-13402236 ] Dmitry Kukushkin commented on MYFACES-3575: --- Is it not just making this _relativeLocations expiring, as it is done for _compositeComponentMetadataFacelets in the DefaultFaceletFactory class? This IMO will be more consistent instead. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TOBAGO-1166) tx:menuCheckbox may produce a duplicated id in JSPs
Udo Schnurpfeil created TOBAGO-1166: --- Summary: tx:menuCheckbox may produce a duplicated id in JSPs Key: TOBAGO-1166 URL: https://issues.apache.org/jira/browse/TOBAGO-1166 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Environment: JSP only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402254#comment-13402254 ] Leonardo Uribe commented on MYFACES-3575: - _relativeLocations do not expire. Look again the code, and you'll see the code for compositeComponentMetadataFacelets is just a copy of the default one. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402263#comment-13402263 ] Dmitry Kukushkin commented on MYFACES-3575: --- This is what I meant, why not to make _relativeLocations cache also expiring, like it is done for _compositeComponentMetadataFacelets? Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3575) Disable relative location caching in DefaultFaceletFactory
[ https://issues.apache.org/jira/browse/MYFACES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402289#comment-13402289 ] Leonardo Uribe commented on MYFACES-3575: - They are two different things. I finally can see the problem, it could be good to have a logic here, but it should be solved at spec level. Disable relative location caching in DefaultFaceletFactory -- Key: MYFACES-3575 URL: https://issues.apache.org/jira/browse/MYFACES-3575 Project: MyFaces Core Issue Type: Improvement Components: Extension Feature Affects Versions: 2.0.14, 2.1.8 Environment: Linux Reporter: Dmitry Kukushkin Assignee: Leonardo Uribe Priority: Minor In some circumstances the caching of the relative location in the public Facelet getFacelet(String uri) in DefaultFaceletFactory is not desirable: e.g. return the mobile and full content version for the same URI, if the user changes the content type on the fly. Now this caching always causes the same content to be returned. Should it be possible to switch it off like it is done for other caches in this class with needsToBeRefreshed check and NO_CACHE_DELAY configuration parameter? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1166) tx:menuCheckbox may produce a duplicated id in JSPs
[ https://issues.apache.org/jira/browse/TOBAGO-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402292#comment-13402292 ] Hudson commented on TOBAGO-1166: Integrated in tobago-trunk #810 (See [https://builds.apache.org/job/tobago-trunk/810/]) TOBAGO-1166: tx:menuCheckbox may produce a duplicated id in JSPs (Revision 1354539) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354539 Files : * /myfaces/tobago/trunk/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java tx:menuCheckbox may produce a duplicated id in JSPs - Key: TOBAGO-1166 URL: https://issues.apache.org/jira/browse/TOBAGO-1166 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Environment: JSP only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TOBAGO-1167) tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId
Udo Schnurpfeil created TOBAGO-1167: --- Summary: tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId Key: TOBAGO-1167 URL: https://issues.apache.org/jira/browse/TOBAGO-1167 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.6.0-beta-2, 1.5.6 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1166) tx:menuCheckbox may produce a duplicated id in JSPs
[ https://issues.apache.org/jira/browse/TOBAGO-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402390#comment-13402390 ] Hudson commented on TOBAGO-1166: Integrated in tobago-1.5.x #55 (See [https://builds.apache.org/job/tobago-1.5.x/55/]) TOBAGO-1166: tx:menuCheckbox may produce a duplicated id in JSPs Merged from trunk [from revision 1354539] (Revision 1354546) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354546 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2 * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java tx:menuCheckbox may produce a duplicated id in JSPs - Key: TOBAGO-1166 URL: https://issues.apache.org/jira/browse/TOBAGO-1166 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Environment: JSP only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TRINIDAD-2283) Unexpected value change with 2 digit defaulting in dateTimeConverter
Yee-Wah Lee created TRINIDAD-2283: - Summary: Unexpected value change with 2 digit defaulting in dateTimeConverter Key: TRINIDAD-2283 URL: https://issues.apache.org/jira/browse/TRINIDAD-2283 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 2.0.1-core Reporter: Yee-Wah Lee Priority: Minor 1. Create an inputText with a convertDateTime uses two-digit year patterns, e.g. convertdateTime pattern=dd/MM/yy 2. Set the inputText value to a date that falls outside the default two-digit-year-start in trinidad-config.xml. The default value is 1950, so two-digit-years would usually resolve within [1950, 2050]. For example, set the date to 1/1/1377. 3. Run the jspx, see that the value is 1/1/77. 4. Modify it to 1/1/78 and submit. Observe that the value changes to 1/1/1978. This is unexpected for the user who did not enter the century change (and also cannot see the effects). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1167) tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId
[ https://issues.apache.org/jira/browse/TOBAGO-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402563#comment-13402563 ] Hudson commented on TOBAGO-1167: Integrated in tobago-trunk #811 (See [https://builds.apache.org/job/tobago-trunk/811/]) TOBAGO-1167: tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId (Revision 1354708) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354708 Files : * /myfaces/tobago/trunk/tobago-extension/tobago-facelets/src/main/java/org/apache/myfaces/tobago/facelets/extension/TobagoMenuExtensionHandler.java * /myfaces/tobago/trunk/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java * /myfaces/tobago/trunk/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuRadioExtensionTag.java tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId -- Key: TOBAGO-1167 URL: https://issues.apache.org/jira/browse/TOBAGO-1167 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOBAGO-1167) tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId
[ https://issues.apache.org/jira/browse/TOBAGO-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1167. - Resolution: Fixed Fix Version/s: 1.6.0-beta-3 1.5.7 tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId -- Key: TOBAGO-1167 URL: https://issues.apache.org/jira/browse/TOBAGO-1167 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TOBAGO-1166) tx:menuCheckbox may produce a duplicated id in JSPs
[ https://issues.apache.org/jira/browse/TOBAGO-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Schnurpfeil resolved TOBAGO-1166. - Resolution: Fixed Fix Version/s: 1.6.0-beta-3 1.5.7 tx:menuCheckbox may produce a duplicated id in JSPs - Key: TOBAGO-1166 URL: https://issues.apache.org/jira/browse/TOBAGO-1166 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Environment: JSP only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1167) tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId
[ https://issues.apache.org/jira/browse/TOBAGO-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402602#comment-13402602 ] Hudson commented on TOBAGO-1167: Integrated in tobago-trunk #812 (See [https://builds.apache.org/job/tobago-trunk/812/]) TOBAGO-1167: tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId - jsf 1.1 variant (Revision 1354749) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354749 Files : * /myfaces/tobago/trunk/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.1/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java * /myfaces/tobago/trunk/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.1/org/apache/myfaces/tobago/internal/taglib/extension/MenuRadioExtensionTag.java tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId -- Key: TOBAGO-1167 URL: https://issues.apache.org/jira/browse/TOBAGO-1167 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1167) tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId
[ https://issues.apache.org/jira/browse/TOBAGO-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402608#comment-13402608 ] Hudson commented on TOBAGO-1167: Integrated in tobago-1.5.x #56 (See [https://builds.apache.org/job/tobago-1.5.x/56/]) TOBAGO-1167: tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId Merged from trunk [from revision 1354708] (Revision 1354710) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354710 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-facelets/src/main/java/org/apache/myfaces/tobago/facelets/extension/TobagoMenuExtensionHandler.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2 * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuRadioExtensionTag.java tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId -- Key: TOBAGO-1167 URL: https://issues.apache.org/jira/browse/TOBAGO-1167 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1164) Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height
[ https://issues.apache.org/jira/browse/TOBAGO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402610#comment-13402610 ] Hudson commented on TOBAGO-1164: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) TOBAGO-1164: Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height Merged from trunk [from revision 1354437] (Revision 1354440) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354440 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUITabGroupLayout.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/tabGroup/tabGroup-layout-1164.xhtml Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height -- Key: TOBAGO-1164 URL: https://issues.apache.org/jira/browse/TOBAGO-1164 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Ralph Jacobs Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 In this example tc:sheet will be displayed with a height of 63 pixels although it should be rendered according to its rows setting. The surrounding tc:tab gets the correct height. tc:panel id=layout-panel f:facet name=layout tc:gridLayout rows=auto / /f:facet tc:tabGroup tc:tab tc:sheetcolumns=*;* ... /tc:sheet /tc:tab /tc:tabGroup /tc:panel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1167) tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId
[ https://issues.apache.org/jira/browse/TOBAGO-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402609#comment-13402609 ] Hudson commented on TOBAGO-1167: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) TOBAGO-1167: tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId Merged from trunk [from revision 1354708] (Revision 1354710) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354710 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-facelets/src/main/java/org/apache/myfaces/tobago/facelets/extension/TobagoMenuExtensionHandler.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2 * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuRadioExtensionTag.java tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId -- Key: TOBAGO-1167 URL: https://issues.apache.org/jira/browse/TOBAGO-1167 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1138) Avoid using String.replace inside ResponseWriter
[ https://issues.apache.org/jira/browse/TOBAGO-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402616#comment-13402616 ] Hudson commented on TOBAGO-1138: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) Merged from trunk (TOBAGO-1138) Avoid using String.replace inside ResponseWriter [from revision 1354247] (Revision 1354248) Result = FAILURE bommel : http://svn.apache.org/viewvc/?view=revrev=1354248 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/util/JavascriptWriterUtils.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/test/java/org/apache/myfaces/tobago/util/JavascriptWriterUtilsTest.java Avoid using String.replace inside ResponseWriter Key: TOBAGO-1138 URL: https://issues.apache.org/jira/browse/TOBAGO-1138 Project: MyFaces Tobago Issue Type: Improvement Components: Core, Themes Affects Versions: 1.5.6 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Fix For: 1.6.0-beta-1, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1154) Show a warning, if there is no JavaScript activated.
[ https://issues.apache.org/jira/browse/TOBAGO-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402611#comment-13402611 ] Hudson commented on TOBAGO-1154: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) TOBAGO-1154: Show a warning, if there is no JavaScript activated. spelling (Revision 1351958) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1351958 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/resources/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/property/tobago_de.properties.xml * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/resources/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/property/tobago_es.properties.xml Show a warning, if there is no JavaScript activated. Key: TOBAGO-1154 URL: https://issues.apache.org/jira/browse/TOBAGO-1154 Project: MyFaces Tobago Issue Type: Improvement Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.6.0-beta-2, 1.5.7, 1.0.40, 1.6.0 Tobago doesn't work without JavaScript. The browser should warn the user, if no JavaScript is available. Using the NOSCRIPT tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1166) tx:menuCheckbox may produce a duplicated id in JSPs
[ https://issues.apache.org/jira/browse/TOBAGO-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402612#comment-13402612 ] Hudson commented on TOBAGO-1166: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) TOBAGO-1166: tx:menuCheckbox may produce a duplicated id in JSPs Merged from trunk [from revision 1354539] (Revision 1354546) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354546 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2 * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java tx:menuCheckbox may produce a duplicated id in JSPs - Key: TOBAGO-1166 URL: https://issues.apache.org/jira/browse/TOBAGO-1166 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Environment: JSP only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1165) Layout Manager: preferred value must not be more significant than current value
[ https://issues.apache.org/jira/browse/TOBAGO-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402613#comment-13402613 ] Hudson commented on TOBAGO-1165: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) TOBAGO-1165: Layout Manager: preferred value must not be more significant than current value Merged from trunk [from revision 1354395] (Revision 1354396) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354396 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/layout/IntervalList.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto-auto.xhtml * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto.xhtml * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-relative.xhtml Layout Manager: preferred value must not be more significant than current value --- Key: TOBAGO-1165 URL: https://issues.apache.org/jira/browse/TOBAGO-1165 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 When laying out using the auto attribute and there is a current width or height set, this value should be used to compute the free space, and not the preferred value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1160) AJAX reload blocks reloaded area
[ https://issues.apache.org/jira/browse/TOBAGO-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402614#comment-13402614 ] Hudson commented on TOBAGO-1160: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) TOBAGO-1160: AJAX reload blocks reloaded area - fix: using iframe only in ie6 (not ie7, ie8, ...) - fix: removing iframe - fix: do not create 2nd iframe Merged from trunk [from revision 1352820] (Revision 1352886) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352886 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js AJAX reload blocks reloaded area Key: TOBAGO-1160 URL: https://issues.apache.org/jira/browse/TOBAGO-1160 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Environment: Internet Explorer only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Critical Fix For: 1.6.0-beta-2, 1.5.7 e.g.: use reload facet with update=false in the demo sheet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1162) Missing accesskey support in tc:selectBooleanCheckbox
[ https://issues.apache.org/jira/browse/TOBAGO-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402615#comment-13402615 ] Hudson commented on TOBAGO-1162: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) Merged from trunk (TOBAGO-1162) Missing accessKey support in tc:selectBooleanCheckbox [from revision 1353071] (Revision 1353208) Result = FAILURE bommel : http://svn.apache.org/viewvc/?view=revrev=1353208 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/SelectBooleanCheckboxRenderer.java Missing accesskey support in tc:selectBooleanCheckbox - Key: TOBAGO-1162 URL: https://issues.apache.org/jira/browse/TOBAGO-1162 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1161) Double AJAX request shows an error in the area
[ https://issues.apache.org/jira/browse/TOBAGO-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402617#comment-13402617 ] Hudson commented on TOBAGO-1161: Integrated in tobago-1.5.x #57 (See [https://builds.apache.org/job/tobago-1.5.x/57/]) TOBAGO-1161: Double AJAX request shows an error in the area Merged from trunk [from revision 1352824] (Revision 1352887) Result = FAILURE lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352887 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js Double AJAX request shows an error in the area -- Key: TOBAGO-1161 URL: https://issues.apache.org/jira/browse/TOBAGO-1161 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TRINIDAD-2273) Allow scheme for application to control UIViewRoot caching logic
[ https://issues.apache.org/jira/browse/TRINIDAD-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Sullivan resolved TRINIDAD-2273. -- Resolution: Fixed Fix Version/s: 2.0.0-core Allow scheme for application to control UIViewRoot caching logic Key: TRINIDAD-2273 URL: https://issues.apache.org/jira/browse/TRINIDAD-2273 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.12-core, 2.0.1-core Environment: all Reporter: Blake Sullivan Assignee: Blake Sullivan Fix For: 2.0.0-core Attachments: trin_2273_2_1.patch Original Estimate: 48h Remaining Estimate: 48h When UIViewRoot caching is enabled, the cached UIViewRoots can consume considerable memory across all of the users. The proposal is to extend the allowed values of the Servlet Initialization parameter: param-nameorg.apache.myfaces.trinidad.CACHE_VIEW_ROOT/param-name to support, in addition to the current true, and false values, the values of: strong UIViewRoot caching is enabled and always uses strong references to the cached UIViewRoot soft UIViewRoot caching is enabled and always uses soft references to the cached UIViewRoot, allowing the cached UIViewRoots to be purged if under memory pressure classname The fully qualified classname of an implementation of org.apache.myfaces.trinidad.util.ref.PseudoReferenceFactory returning any desired PseudoReference implementation. In addition, the value of true now uses the value of a PseudoReferenceFactory implementation registered under the service name org.apache.myfaces.trinidad.CACHE_VIEW_ROOT if one is registered, otherwise, it uses a strong reference, to duplicate the current functionality -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (TRINIDAD-2273) Allow scheme for application to control UIViewRoot caching logic
[ https://issues.apache.org/jira/browse/TRINIDAD-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Sullivan reopened TRINIDAD-2273: -- Allow scheme for application to control UIViewRoot caching logic Key: TRINIDAD-2273 URL: https://issues.apache.org/jira/browse/TRINIDAD-2273 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.12-core, 2.0.1-core Environment: all Reporter: Blake Sullivan Assignee: Blake Sullivan Fix For: 2.0.0-core Attachments: trin_2273_2_1.patch Original Estimate: 48h Remaining Estimate: 48h When UIViewRoot caching is enabled, the cached UIViewRoots can consume considerable memory across all of the users. The proposal is to extend the allowed values of the Servlet Initialization parameter: param-nameorg.apache.myfaces.trinidad.CACHE_VIEW_ROOT/param-name to support, in addition to the current true, and false values, the values of: strong UIViewRoot caching is enabled and always uses strong references to the cached UIViewRoot soft UIViewRoot caching is enabled and always uses soft references to the cached UIViewRoot, allowing the cached UIViewRoots to be purged if under memory pressure classname The fully qualified classname of an implementation of org.apache.myfaces.trinidad.util.ref.PseudoReferenceFactory returning any desired PseudoReference implementation. In addition, the value of true now uses the value of a PseudoReferenceFactory implementation registered under the service name org.apache.myfaces.trinidad.CACHE_VIEW_ROOT if one is registered, otherwise, it uses a strong reference, to duplicate the current functionality -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TRINIDAD-2273) Allow scheme for application to control UIViewRoot caching logic
[ https://issues.apache.org/jira/browse/TRINIDAD-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402671#comment-13402671 ] Blake Sullivan commented on TRINIDAD-2273: -- Reopened because this caused a regression when view root caching was disabled Allow scheme for application to control UIViewRoot caching logic Key: TRINIDAD-2273 URL: https://issues.apache.org/jira/browse/TRINIDAD-2273 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.12-core, 2.0.1-core Environment: all Reporter: Blake Sullivan Assignee: Blake Sullivan Fix For: 2.0.0-core Attachments: trin_2273_2_1.patch Original Estimate: 48h Remaining Estimate: 48h When UIViewRoot caching is enabled, the cached UIViewRoots can consume considerable memory across all of the users. The proposal is to extend the allowed values of the Servlet Initialization parameter: param-nameorg.apache.myfaces.trinidad.CACHE_VIEW_ROOT/param-name to support, in addition to the current true, and false values, the values of: strong UIViewRoot caching is enabled and always uses strong references to the cached UIViewRoot soft UIViewRoot caching is enabled and always uses soft references to the cached UIViewRoot, allowing the cached UIViewRoots to be purged if under memory pressure classname The fully qualified classname of an implementation of org.apache.myfaces.trinidad.util.ref.PseudoReferenceFactory returning any desired PseudoReference implementation. In addition, the value of true now uses the value of a PseudoReferenceFactory implementation registered under the service name org.apache.myfaces.trinidad.CACHE_VIEW_ROOT if one is registered, otherwise, it uses a strong reference, to duplicate the current functionality -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1167) tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId
[ https://issues.apache.org/jira/browse/TOBAGO-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402697#comment-13402697 ] Hudson commented on TOBAGO-1167: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) TOBAGO-1167: tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId - jsf 1.1 variant (Revision 1354748) TOBAGO-1167: tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId Merged from trunk [from revision 1354708] (Revision 1354710) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354748 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.1/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.1/org/apache/myfaces/tobago/internal/taglib/extension/MenuRadioExtensionTag.java lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354710 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-facelets/src/main/java/org/apache/myfaces/tobago/facelets/extension/TobagoMenuExtensionHandler.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2 * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuRadioExtensionTag.java tx:menuCheckbox and tx:menuRadio should have the attributes id and fieldId -- Key: TOBAGO-1167 URL: https://issues.apache.org/jira/browse/TOBAGO-1167 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1164) Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height
[ https://issues.apache.org/jira/browse/TOBAGO-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402698#comment-13402698 ] Hudson commented on TOBAGO-1164: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) TOBAGO-1164: Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height Merged from trunk [from revision 1354437] (Revision 1354440) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354440 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUITabGroupLayout.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/tabGroup/tabGroup-layout-1164.xhtml Using auto layout with tc:tabGroup: The components inside of the tab are displayed with wrong height -- Key: TOBAGO-1164 URL: https://issues.apache.org/jira/browse/TOBAGO-1164 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Ralph Jacobs Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 In this example tc:sheet will be displayed with a height of 63 pixels although it should be rendered according to its rows setting. The surrounding tc:tab gets the correct height. tc:panel id=layout-panel f:facet name=layout tc:gridLayout rows=auto / /f:facet tc:tabGroup tc:tab tc:sheetcolumns=*;* ... /tc:sheet /tc:tab /tc:tabGroup /tc:panel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1166) tx:menuCheckbox may produce a duplicated id in JSPs
[ https://issues.apache.org/jira/browse/TOBAGO-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402699#comment-13402699 ] Hudson commented on TOBAGO-1166: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) TOBAGO-1166: tx:menuCheckbox may produce a duplicated id in JSPs Merged from trunk [from revision 1354539] (Revision 1354546) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354546 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2 * /myfaces/tobago/branches/tobago-1.5.x/tobago-extension/tobago-taglib-extension/src/main/java-jsf-1.2/org/apache/myfaces/tobago/internal/taglib/extension/MenuCheckboxExtensionTag.java tx:menuCheckbox may produce a duplicated id in JSPs - Key: TOBAGO-1166 URL: https://issues.apache.org/jira/browse/TOBAGO-1166 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.5.6, 1.6.0-beta-2 Environment: JSP only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1165) Layout Manager: preferred value must not be more significant than current value
[ https://issues.apache.org/jira/browse/TOBAGO-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402700#comment-13402700 ] Hudson commented on TOBAGO-1165: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) TOBAGO-1165: Layout Manager: preferred value must not be more significant than current value Merged from trunk [from revision 1354395] (Revision 1354396) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1354396 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/layout/IntervalList.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto-auto.xhtml * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-auto.xhtml * /myfaces/tobago/branches/tobago-1.5.x/tobago-example/tobago-example-test/src/main/webapp/tc/gridLayout/tabGroup-relative.xhtml Layout Manager: preferred value must not be more significant than current value --- Key: TOBAGO-1165 URL: https://issues.apache.org/jira/browse/TOBAGO-1165 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.5.6, 1.6.0-beta-2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Fix For: 1.5.7, 1.6.0-beta-3 When laying out using the auto attribute and there is a current width or height set, this value should be used to compute the free space, and not the preferred value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1160) AJAX reload blocks reloaded area
[ https://issues.apache.org/jira/browse/TOBAGO-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402701#comment-13402701 ] Hudson commented on TOBAGO-1160: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) TOBAGO-1160: AJAX reload blocks reloaded area - fix: using iframe only in ie6 (not ie7, ie8, ...) - fix: removing iframe - fix: do not create 2nd iframe Merged from trunk [from revision 1352820] (Revision 1352886) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352886 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js AJAX reload blocks reloaded area Key: TOBAGO-1160 URL: https://issues.apache.org/jira/browse/TOBAGO-1160 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Environment: Internet Explorer only Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Critical Fix For: 1.6.0-beta-2, 1.5.7 e.g.: use reload facet with update=false in the demo sheet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1162) Missing accesskey support in tc:selectBooleanCheckbox
[ https://issues.apache.org/jira/browse/TOBAGO-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402702#comment-13402702 ] Hudson commented on TOBAGO-1162: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) Merged from trunk (TOBAGO-1162) Missing accessKey support in tc:selectBooleanCheckbox [from revision 1353071] (Revision 1353208) Result = SUCCESS bommel : http://svn.apache.org/viewvc/?view=revrev=1353208 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/SelectBooleanCheckboxRenderer.java Missing accesskey support in tc:selectBooleanCheckbox - Key: TOBAGO-1162 URL: https://issues.apache.org/jira/browse/TOBAGO-1162 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1138) Avoid using String.replace inside ResponseWriter
[ https://issues.apache.org/jira/browse/TOBAGO-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402703#comment-13402703 ] Hudson commented on TOBAGO-1138: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) Merged from trunk (TOBAGO-1138) Avoid using String.replace inside ResponseWriter [from revision 1354247] (Revision 1354248) Result = SUCCESS bommel : http://svn.apache.org/viewvc/?view=revrev=1354248 Files : * /myfaces/tobago/branches/tobago-1.5.x * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/util/JavascriptWriterUtils.java * /myfaces/tobago/branches/tobago-1.5.x/tobago-core/src/test/java/org/apache/myfaces/tobago/util/JavascriptWriterUtilsTest.java Avoid using String.replace inside ResponseWriter Key: TOBAGO-1138 URL: https://issues.apache.org/jira/browse/TOBAGO-1138 Project: MyFaces Tobago Issue Type: Improvement Components: Core, Themes Affects Versions: 1.5.6 Reporter: Bernd Bohmann Assignee: Bernd Bohmann Fix For: 1.6.0-beta-1, 1.5.7, 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TOBAGO-1161) Double AJAX request shows an error in the area
[ https://issues.apache.org/jira/browse/TOBAGO-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402704#comment-13402704 ] Hudson commented on TOBAGO-1161: Integrated in tobago-1.5.x #58 (See [https://builds.apache.org/job/tobago-1.5.x/58/]) TOBAGO-1161: Double AJAX request shows an error in the area Merged from trunk [from revision 1352824] (Revision 1352887) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=revrev=1352887 Files : * /myfaces/tobago/branches/tobago-1.5.x/tobago-theme/tobago-theme-standard/src/main/resources/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js Double AJAX request shows an error in the area -- Key: TOBAGO-1161 URL: https://issues.apache.org/jira/browse/TOBAGO-1161 Project: MyFaces Tobago Issue Type: Bug Components: Themes Affects Versions: 1.5.6, 1.6.0-beta-1 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Minor Fix For: 1.6.0-beta-2, 1.5.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TRINIDAD-2273) Allow scheme for application to control UIViewRoot caching logic
[ https://issues.apache.org/jira/browse/TRINIDAD-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Sullivan resolved TRINIDAD-2273. -- Resolution: Fixed Allow scheme for application to control UIViewRoot caching logic Key: TRINIDAD-2273 URL: https://issues.apache.org/jira/browse/TRINIDAD-2273 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.12-core, 2.0.1-core Environment: all Reporter: Blake Sullivan Assignee: Blake Sullivan Fix For: 2.0.0-core Attachments: trin_2273_2_1.patch, trin_2273_2_1_part_deux.patch Original Estimate: 48h Remaining Estimate: 48h When UIViewRoot caching is enabled, the cached UIViewRoots can consume considerable memory across all of the users. The proposal is to extend the allowed values of the Servlet Initialization parameter: param-nameorg.apache.myfaces.trinidad.CACHE_VIEW_ROOT/param-name to support, in addition to the current true, and false values, the values of: strong UIViewRoot caching is enabled and always uses strong references to the cached UIViewRoot soft UIViewRoot caching is enabled and always uses soft references to the cached UIViewRoot, allowing the cached UIViewRoots to be purged if under memory pressure classname The fully qualified classname of an implementation of org.apache.myfaces.trinidad.util.ref.PseudoReferenceFactory returning any desired PseudoReference implementation. In addition, the value of true now uses the value of a PseudoReferenceFactory implementation registered under the service name org.apache.myfaces.trinidad.CACHE_VIEW_ROOT if one is registered, otherwise, it uses a strong reference, to duplicate the current functionality -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
