-
1. Re: injecting session-scoped component into conversation-scoped component
gonorrhea Jun 17, 2009 6:42 PM (in response to gonorrhea)I changed the code to the following:
@Name("manageSiteId") @Stateful @Scope(ScopeType.CONVERSATION) @AutoCreate public class ManageSiteIdAction implements ManageSiteIdLocal{...}
and removed the @Begin(join=true) annotations from the two business methods, and now the drop-down
magically
behaves properly (the drop down value is properly set and displayed in different situations).We actually want the properties associated with HtmlSelectOneMenu and that component to be session-scoped. How can I fix this problem and use an injected session-scoped component?
pages.xml:
<page view-id="/ManageEquipment.xhtml"> <description>Manage Equipment</description> <!-- <action execute="#{manageEquipment.init}" if="#{not manageEquipment.isInitComplete()}"/> --> <begin-conversation join="true"/> <action execute="#{manageSiteId.init}"/> <navigation from-action="#{manageEquipment.processRepairHistorySelection}"> <redirect view-id="/RepairCaseDetails.xhtml"/> </navigation> <navigation from-action="#{manageEquipment.searchSerialNumber}"> <redirect view-id="/ManageEquipment.xhtml"/> </navigation> </page>
-
2. Re: injecting session-scoped component into conversation-scoped component
gonorrhea Jun 17, 2009 7:00 PM (in response to gonorrhea)well apparently you should be able to inject a session-scoped component into a conversation-scoped component. I checked the older version of my code and it works as intended.
still not sure exactly what's causing the anomalous behavior (now on to backfactoring!)
-
3. Re: injecting session-scoped component into conversation-scoped component
gonorrhea Jun 17, 2009 7:45 PM (in response to gonorrhea)I fixed it but not sure how. Anyways, I'm wondering if non-matching scoped injection will be supported in Seam 3 and/or Web Beans???