[
https://jira.jboss.org/browse/WELD-548?page=com.atlassian.jira.plugin.sys...
]
David Beaumont commented on WELD-548:
-------------------------------------
That's a shame, I think #{conversation} not working will trip a lot of people up.
Perhaps an example of how to 'reproduce' the conversation with a nicer name for EL
could go in the documentation?
Something like:
@Target({ TYPE, METHOD, PARAMETER, FIELD })
@Retention(RUNTIME)
@Documented
@Qualifier
public @interface ElProducer {}
public class Producers {
@Inject Conversation conversation;
@Produces @Named @ConversationScoped @ElProducer
public Conversation getConversation() {
return conversation;
}
}
The qualifier is needed to prevent an ambiguous injection point for Conversation.
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
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/jbo...
Also see:
http://seamframework.org/Community/ApparentInaccuraciesInConversationDocu...
--
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