[ 
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: 1.0.0-CR1)
    Affects Version/s: 1.0.0-CR1
                           (was: M4)
             Priority: Minor  (was: Major)
          Component/s: Context and Scopes
                           (was: Injection and Lookup)

> 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: New Feature
>          Components: Context and Scopes
>    Affects Versions: 1.0.0-CR1
>            Reporter: YING WANG
>            Assignee: YING WANG
>            Priority: Minor
>             Fix For: 1.1.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.

Reply via email to