You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by Gurkan Erdogdu <cg...@gmail.com> on 2010/03/11 17:03:34 UTC
Re: [jira] Updated: (OWB-321) Conversation beans could not be
populated to non-faces request by a JSF redirect navigation rule
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 that it wants to talk
about JSF GET requests, i.e GET requests handled by JSF Servlet and go
through WebBeansPhaseListener. When it talks about Faces-Request, it wants
to emphasize that requests coming from JSF Form submitting via commandButton
or commandLink. Therefore, if you do not use </redirect> in
faces-config.xml, you have to give cid via URL, like
http://localhost:vbxbvdf/page.jsf?cid=1 etc.
Therefore I think that, it is not necessary to handle JSP case redirects.
Thanks;
--Gurkan
2010/3/11 YING WANG (JIRA) <ji...@apache.org>
>
> [
> 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 be populated to non-faces request by a JSF
> redirect navigation rule
> >
> ------------------------------------------------------------------------------------------------
> >
> > Key: OWB-321
> > URL: https://issues.apache.org/jira/browse/OWB-321
> > Project: OpenWebBeans
> > Issue Type: Bug
> > Components: Injection and Lookup
> > Affects Versions: M4
> > Reporter: YING WANG
> > Assignee: YING WANG
> > Fix For: 1.0.0
> >
> > Attachments: owb321.patch
> >
> >
> > I have the following JSF redirect navigation rule, which redirect a JSF
> page to a jsp page:
> > <navigation-rule>
> > <from-view-id>/cellphonebuy.xhtml</from-view-id>
> > <navigation-case>
> > <from-outcome>toListingPage</from-outcome>
> > <to-view-id>/cellphonelist.jsp</to-view-id>
> > <redirect/>
> > </navigation-case>
> > </navigation-rule>
> > However, in cellphonelist JSP page, I could not access beans of the
> conversation context and "No active conversation context" Exception is
> thrown. I do see the cid parameter being appended at the end of my jsp link.
> > According to 8th and 9th bullets under 6.7.4, a long-run conversation
> context should be populated to non-face requests if JSF redirect is used or
> the application generates a link with such cid parameter. (please assign to
> me)
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
--
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com
Re: [jira] Updated: (OWB-321) Conversation beans could not be
populated to non-faces request by a JSF redirect navigation rule
Posted by Gurkan Erdogdu <cg...@gmail.com>.
But we can support it anyway! :) So, conversation context is used by core
JSP/Servlet environment.
Thanks,
--Gurkan
2010/3/11 Gurkan Erdogdu <cg...@gmail.com>
> 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 that it wants to talk
> about JSF GET requests, i.e GET requests handled by JSF Servlet and go
> through WebBeansPhaseListener. When it talks about Faces-Request, it wants
> to emphasize that requests coming from JSF Form submitting via commandButton
> or commandLink. Therefore, if you do not use </redirect> in
> faces-config.xml, you have to give cid via URL, like
> http://localhost:vbxbvdf/page.jsf?cid=1 etc.
>
> Therefore I think that, it is not necessary to handle JSP case redirects.
>
> Thanks;
>
> --Gurkan
>
>
> 2010/3/11 YING WANG (JIRA) <ji...@apache.org>
>
>
>> [
>> 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 be populated to non-faces request by a JSF
>> redirect navigation rule
>> >
>> ------------------------------------------------------------------------------------------------
>> >
>> > Key: OWB-321
>> > URL: https://issues.apache.org/jira/browse/OWB-321
>> > Project: OpenWebBeans
>> > Issue Type: Bug
>> > Components: Injection and Lookup
>> > Affects Versions: M4
>> > Reporter: YING WANG
>> > Assignee: YING WANG
>> > Fix For: 1.0.0
>> >
>> > Attachments: owb321.patch
>> >
>> >
>> > I have the following JSF redirect navigation rule, which redirect a JSF
>> page to a jsp page:
>> > <navigation-rule>
>> > <from-view-id>/cellphonebuy.xhtml</from-view-id>
>> > <navigation-case>
>> > <from-outcome>toListingPage</from-outcome>
>> > <to-view-id>/cellphonelist.jsp</to-view-id>
>> > <redirect/>
>> > </navigation-case>
>> > </navigation-rule>
>> > However, in cellphonelist JSP page, I could not access beans of the
>> conversation context and "No active conversation context" Exception is
>> thrown. I do see the cid parameter being appended at the end of my jsp link.
>> > According to 8th and 9th bullets under 6.7.4, a long-run conversation
>> context should be populated to non-face requests if JSF redirect is used or
>> the application generates a link with such cid parameter. (please assign to
>> me)
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
>
> --
> Gurkan Erdogdu
> http://gurkanerdogdu.blogspot.com
>
--
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com