[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-4250) Contexts are not in sync when using SeamResourceBundle and seam Log

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBSEAM-4250.
-----------------------------

    Resolution: Rejected


Please use the forums for support

> Contexts are not in sync when using SeamResourceBundle and seam Log
> -------------------------------------------------------------------
>
>                 Key: JBSEAM-4250
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4250
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.1.GA
>            Reporter: Ian Michell
>            Priority: Blocker
>
> Hi,
> Using Seam 2.1.1.GA I am injecting the messages map (@In Map<String, String> messages) and setting eventContext variables before using get on the map and I'm getting an exception that states that it cannot resolve the value... Code follows:
> Code for a single purchase order in my document history
> --------------------------------------------------------------------------------------------
> Contexts.getEventContext().set("trn.viewTransactions.poDocument", poList.get(0));
> Contexts.getEventContext().set("trn.viewTransactions.supplierName", poList.get(0).getSupplierOrgs().first().getCommonName());
> Contexts.getEventContext().set("trn.viewTransactions.poList", messages.get("mytransactions.messages.generated.link"));
> Contexts.getEventContext().flush();
> history.setActionDescription(messages.get("mytransactions.messages.generated.single"));
> --------------------------------------------------------------------------------------------
> Expected output: This requisition also generated this order: Order 12345 - ACME Suppliers
> Expression: This requisition also generated this order: #{trn.viewTransactions.poList}
> It throws an exception saying viewTransactions cannot be resolved on the seam namespace, this generally means that it can't find the values in the expression.
> I have tried flushing the event context to see if it makes a difference (hence the flush above). Is this a bug, or am I doing the entire thing wrong?
> Any help would be appreciated.
> Ian

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira