Allow display of the detail message in tc:messages and tc:message
-
Key: TOBAGO-362
URL: https://issues.apache.org/jira/browse/TOBAGO-362
Project: MyFaces Tobago
Issue Type:
[
https://issues.apache.org/jira/browse/TOBAGO-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-362.
--
Resolution: Fixed
Allow display of the detail message in tc:messages and tc:message
[
https://issues.apache.org/jira/browse/TOBAGO-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-360.
--
Resolution: Fixed
Allow definition of supported markup in tobago-config.xml
[
https://issues.apache.org/jira/browse/MYFACES-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491223
]
Martin Haimberger commented on MYFACES-1220:
Hi,
I have looked over this issue and it seems to me
Is there any reason for not making it part of the AJAX api ?
The AjaxDecodePhaseListener is also part of the package
org.apache.myfaces.custom.ajax.api
One more, can we make the package named
org.apache.myfaces.ajax.api
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog:
[
https://issues.apache.org/jira/browse/MYFACES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda updated MYFACES-1222:
--
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Status: Resolved (was:
What do you guys think the chances are of moving this into the next Tomahawk
release?
On 4/24/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Is there any reason for not making it part of the AJAX api ?
The AjaxDecodePhaseListener is also part of the package
[
https://issues.apache.org/jira/browse/MYFACES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda reopened MYFACES-1222:
---
Hi, I have reverted the patch as the test DefaultFacesInitializerTest is not
passing. Could
[
https://issues.apache.org/jira/browse/MYFACES-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda updated MYFACES-1204:
--
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/MYFACES-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491261
]
Bruno Aranda commented on MYFACES-1221:
---
Thanks for the patch with the test Martin. Does this mean that the
[
https://issues.apache.org/jira/browse/MYFACES-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda updated MYFACES-1221:
--
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/MYFACES-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda updated MYFACES-1444:
--
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/MYFACES-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1255.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Closing it, then. Thanks Martin
[
https://issues.apache.org/jira/browse/MYFACES-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1230.
---
Resolution: Invalid
Fix Version/s: 1.2.0-SNAPSHOT
Assignee: Bruno Aranda
[
https://issues.apache.org/jira/browse/MYFACES-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1436.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
True. The code generator already
[
https://issues.apache.org/jira/browse/MYFACES-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1212.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
This was already implemented
[
https://issues.apache.org/jira/browse/MYFACES-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1439.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Assignee: Bruno Aranda
[
https://issues.apache.org/jira/browse/MYFACES-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda updated MYFACES-1484:
--
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Assignee: Bruno Aranda
[
https://issues.apache.org/jira/browse/MYFACES-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul McMahan resolved MYFACES-1592.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
patch applied with a minor
Well, if it's wrong, it still might be worth fixing since JSF 1.2
won't be an option in many environments for quite some time. But
since you're the one interested in fixing it, if you don't pursue it,
it won't be changed. In my own use cases, I'm not concerned about
strict html or xhtml
[
https://issues.apache.org/jira/browse/MYFACES-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491302
]
Martin Haimberger commented on MYFACES-1253:
Hi,
the problem described in the bug 147 is not a bug in
[
https://issues.apache.org/jira/browse/MYFACES-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1253.
---
Resolution: Invalid
Fix Version/s: 1.1.6
Assignee: Bruno Aranda
Ok for me.
Why not.
Ernst, do you think it is stable ?
Are all requirements fulfilled for a possible graduation of that component ?
-Matthias
On 4/24/07, Dennis Byrne [EMAIL PROTECTED] wrote:
What do you guys think the chances are of moving this into the next Tomahawk
release?
On 4/24/07, Matthias
Passthrough attribute acceptcharset for form not being rendered
-
Key: MYFACES-1594
URL: https://issues.apache.org/jira/browse/MYFACES-1594
Project: MyFaces Core
Issue Type:
spec compliance for HtmlCommandButton
-
Key: MYFACES-1595
URL: https://issues.apache.org/jira/browse/MYFACES-1595
Project: MyFaces Core
Issue Type: Bug
Components: JSR-252
Affects Versions:
[
https://issues.apache.org/jira/browse/MYFACES-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul McMahan resolved MYFACES-1595.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
spec compliance for
[
https://issues.apache.org/jira/browse/MYFACES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Ebner updated MYFACES-1222:
-
Status: Patch Available (was: Reopened)
JSR-252 Issue #51: Allow implementations to
[
https://issues.apache.org/jira/browse/MYFACES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491359
]
Christoph Ebner commented on MYFACES-1222:
--
The DefaultFacesInitializerTest isn't practicable anymore.
[
https://issues.apache.org/jira/browse/MYFACES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda updated MYFACES-1222:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Ok, patch applied. Thanks
Hi *,
Nice greatings from Christoph Ebner and me. A lot of issues have been
resolved since our last status update, but there are also some new
issues.
Here is the updated list of last time:
MYFACES-1563 - Martin will ovetake this from Christoph.
MYFACES-1255 - resolved
MYFACES-1264 - Christoph
In an inputText, If the autocomplete attribute is not set or the value is
on, render nothing.
-
Key: MYFACES-1596
URL:
[
https://issues.apache.org/jira/browse/MYFACES-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491374
]
Bruno Aranda commented on MYFACES-1596:
---
Just in case, render nothing means not render that attribute and
[
https://issues.apache.org/jira/browse/MYFACES-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491376
]
Bruno Aranda commented on MYFACES-1596:
---
And the same for inputSecret
In an inputText, If the autocomplete
Hi Martin, I am looking at MYFACES-1587 below and the corresponding Geronimo
JIRA (GERONIMO-3038)
Thanks,
Tim McConnell
Martin Haimberger wrote:
Hi *,
Nice greatings from Christoph Ebner and me. A lot of issues have been
resolved since our last status update, but there are also some new
In inputTextarea, pass thru attributes cols and rows should not be rendered
if they are not set
---
Key: MYFACES-1597
URL:
JSF 1.2 TLD compliance: attributes binding and converter with wrong
deferred-type
-
Key: MYFACES-1598
URL: https://issues.apache.org/jira/browse/MYFACES-1598
JSF 1.2 TLD compliance: attribute action with wrong deferred-method signature
Key: MYFACES-1599
URL: https://issues.apache.org/jira/browse/MYFACES-1599
Project: MyFaces
JSF 1.2 TLD compliance: wrong deferred value for rendered and id should be
false for the rtexpr value
-
Key: MYFACES-1600
URL:
JSF 1.2 TLD compliance: attribute var from dataTable with wrong configuration
---
Key: MYFACES-1601
URL: https://issues.apache.org/jira/browse/MYFACES-1601
Project: MyFaces
[
https://issues.apache.org/jira/browse/MYFACES-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated MYFACES-1467:
Resolution: Fixed
Status: Resolved (was: Patch Available)
There is no conflict in the
dataTable does not render any content
-
Key: MYFACES-1602
URL: https://issues.apache.org/jira/browse/MYFACES-1602
Project: MyFaces Core
Issue Type: Bug
Components: JSR-252
Reporter:
markup attribute for progress component
---
Key: TOBAGO-363
URL: https://issues.apache.org/jira/browse/TOBAGO-363
Project: MyFaces Tobago
Issue Type: Improvement
Components: Core
Affects
TabGroup rendered wrong tab if the rendered attribute of the current tab is
false
--
Key: TOBAGO-364
URL: https://issues.apache.org/jira/browse/TOBAGO-364
Project:
CommandLink problem with DataList
-
Key: MYFACES-1603
URL: https://issues.apache.org/jira/browse/MYFACES-1603
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 1.1.4
Environment: Linux
[
https://issues.apache.org/jira/browse/MYFACES-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul McMahan resolved MYFACES-1594.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
applied fix similar to MYFACES-1510
[
https://issues.apache.org/jira/browse/MYFACES-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated MYFACES-1587:
---
Status: Patch Available (was: Open)
generated h.tld doesn't conform to schema
[
https://issues.apache.org/jira/browse/MYFACES-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491508
]
Paul Norrie commented on MYFACES-1528:
--
I've just found the same bug.
Myfaces implementation of dataTable
[
https://issues.apache.org/jira/browse/TOMAHAWK-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491510
]
Paul Norrie commented on TOMAHAWK-89:
-
Apparantly not. Just found this issue myself. Had to change the
Partial Refresh does not work if triggerButton comes after the last
PPRPanelGroup
-
Key: TOMAHAWK-969
URL: https://issues.apache.org/jira/browse/TOMAHAWK-969
Project:
There is one issue I'd like to sort out before that:
https://issues.apache.org/jira/browse/TOMAHAWK-969
I hope I'll find time to do that on the weekend or next week during the con.
other than that since I'm using the PPRPanelGroup sucessfully in 2
projects for 8 months now I have the feeling
50 matches
Mail list logo