[weld-issues] [JBoss JIRA] Updated: (WELD-548) Reference guide references #{conversation}, not #{javax.enterprise.context.conversation}
Pete Muir (JIRA)
jira-events at lists.jboss.org
Mon Aug 16 15:33:12 EDT 2010
[ https://jira.jboss.org/browse/WELD-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir updated WELD-548:
---------------------------
Fix Version/s: 1.1.0.BETA1
> Reference guide references #{conversation}, not #{javax.enterprise.context.conversation}
> ----------------------------------------------------------------------------------------
>
> Key: WELD-548
> URL: https://jira.jboss.org/browse/WELD-548
> Project: Weld
> Issue Type: Task
> Components: Conversations, Documentation
> Affects Versions: 1.0.1.Final
> Environment: GlassFish Server Open Source Edition 3.0.1 on Mac OS 10.6 and Windows 7. WELD-000900 1.0.1 (SP2)
> Reporter: David Beaumont
> Priority: Trivial
> Fix For: 1.1.0.BETA1
>
> Attachments: CdiConvoBug.war
>
>
> The Weld documentation states that you can use #{conversation} to access the conversation from within a facelets page. This does not work, though using #{javax.enterprise.context.conversation} does access the conversation. I discovered this by looking at the source at:
> http://anonsvn.jboss.org/repos/weld/core/trunk/impl/src/main/java/org/jboss/weld/conversation/ConversationImpl.java
> Also see: http://seamframework.org/Community/ApparentInaccuraciesInConversationDocumentation
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the weld-issues
mailing list