[
https://issues.apache.org/jira/browse/MYFACES-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14367225#comment-14367225
]
Jose Luis Freire commented on MYFACES-3964:
---
This issue is especially critical
[
https://issues.apache.org/jira/browse/ORCHESTRA-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12975265#action_12975265
]
Jose Luis Freire commented on ORCHESTRA-55:
---
Ok... There's already a
Access Scoped Conversation is incompatible with RichFaces 3.3.3
---
Key: ORCHESTRA-55
URL: https://issues.apache.org/jira/browse/ORCHESTRA-55
Project: MyFaces Orchestra
Issue Type:
Access Scope doesn't account for network latency (or other network events).
---
Key: ORCHESTRA-53
URL: https://issues.apache.org/jira/browse/ORCHESTRA-53
Project: MyFaces
There is no way to know if our conversation context id is invalid.
--
Key: ORCHESTRA-51
URL: https://issues.apache.org/jira/browse/ORCHESTRA-51
Project: MyFaces Orchestra
Issue
IllegalStateException on application startup when using conversations with
beans that implement ApplicationListener
---
Key: ORCHESTRA-43
URL:
[
https://issues.apache.org/jira/browse/ORCHESTRA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jose Luis Freire resolved ORCHESTRA-43.
---
Resolution: Invalid
I think it makes sense to have application listeners on all
commandButton inside datatable doesn't process action
-
Key: MYFACES-1357
URL: http://issues.apache.org/jira/browse/MYFACES-1357
Project: MyFaces Core
Type: Bug
Versions: 1.1.3
Environment: Windows XP
[
http://issues.apache.org/jira/browse/MYFACES-1357?page=comments#action_12419793
]
Jose Luis Freire commented on MYFACES-1357:
---
Sorry. Forgot to say I'm using facelets 1.1.11.
commandButton inside datatable doesn't process action