[
https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-321:
--
Fix Version/s: (was: 1.1.1)
1.2.0
> Conversation beans could not be populated to no
[
https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-321:
--
Fix Version/s: (was: 1.1.1)
1.2.0
> Conversation beans could not be populated to no
[
https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OWB-321:
--
Fix Version/s: (was: 1.1.0)
1.2.0
moved to target 1.2.0
> Conversation beans could
[
https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu updated OWB-321:
---
Issue Type: New Feature (was: Bug)
Fix Version/s: 1.1.0
(was:
But we can support it anyway! :) So, conversation context is used by core
JSP/Servlet environment.
Thanks,
--Gurkan
2010/3/11 Gurkan Erdogdu
> Hello Ying;
>
> After re-reading ConversationContext from specification, I think that there
> is some misunderstanding regard to non-faces-request term
Hello Ying;
After re-reading ConversationContext from specification, I think that there
is some misunderstanding regard to non-faces-request term.
ConversationContext is used in JSF environments in the specification, not in
JSP or Core Servlet.
When specification says non-faces-request, I think t
[
https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YING WANG updated OWB-321:
--
Attachment: owb321.patch
Could someone help review my change? Thanks in advance.
> Conversation beans could not b
[
https://issues.apache.org/jira/browse/OWB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu updated OWB-321:
---
Fix Version/s: 1.0.0
Assignee: YING WANG (was: Gurkan Erdogdu)
> Conversation beans could not
