Hi Ying;

I have added you in JIRA. After that you are able to work on issues 
(assign,resolve etc..)


Thanks;

--Gurkan




________________________________
From: YING WANG (JIRA) <[email protected]>
To: [email protected]
Sent: Tue, March 9, 2010 12:03:27 AM
Subject: [jira] Created: (OWB-321) Conversation beans could not be populated to 
non-faces request by a JSF redirect navigation rule

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: Gurkan Erdogdu


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.


      ___________________________________________________________________
Yahoo! Türkiye açıldı!  http://yahoo.com.tr
İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!

Reply via email to