Apparent inaccuracies in Conversation documentation

[skunk]

According to the docs:
http://docs.jboss.org/weld/reference/latest/en-US/html/scopescontexts.html#d0e1882 conversations can be accessed via

#{conversation}

However this doesn't seem to work for me. Instead I have to do

#{javax.enterprise.context.conversation}

This is on the versions of glassfish and weld that come with Netbeans 6.9 RC1.

---

Another problem is that the conversation is propagated by default with h:link tags, not via an explicit parameter like the documentation says. So my tag:

<h:link value="Index" outcome="/index.xhtml" />

Outputs:

<a href="/SecurityTest/index.jsf?cid=12">Index</a>

And this can't be got rid of by doing something like

<f:param name="cid" value="" />

as Weld will go mad trying to lookup a blank conversation id. If you can't get rid of the conversation surely it is a session! I'm apparently not the only one having this trouble: http://stackoverflow.com/questions/2686240/can-one-suppress-the-conversation-propagation-with-an-hlink

Dave

[bleathem]

Indeed, the documentation seems to be inaccurate. Maybe in the preceeding pages, they spoke about creating a producer to access the conversation?  Either way, the Seam 3 Faces module adds support for accessing the conversation via this simplified EL.
http://seamframework.org/Seam3/FacesModule

Still waiting to figure how to suppress the conversation propagation with an <h:link>

Brian

[pmuir]

David Beaumont wrote on Jun 06, 2010 19:29:


According to the docs:
http://docs.jboss.org/weld/reference/latest/en-US/html/scopescontexts.html#d0e1882 conversations can be accessed via

#{conversation}

However this doesn't seem to work for me. Instead I have to do

#{javax.enterprise.context.conversation}

This is on the versions of glassfish and weld that come with Netbeans 6.9 RC1.

Please file an issue in JIRA, we'll get this fixed :-)

Another problem is that the conversation is propagated by default with h:link tags, not via an explicit parameter like the documentation says. So my tag:

<h:link value="Index" outcome="/index.xhtml" />

Outputs:

<a href="/SecurityTest/index.jsf?cid=12">Index</a>

And this can't be got rid of by doing something like

<f:param name="cid" value="" />

as Weld will go mad trying to lookup a blank conversation id. If you can't get rid of the conversation surely it is a session! I'm apparently not the only one having this trouble: http://stackoverflow.com/questions/2686240/can-one-suppress-the-conversation-propagation-with-an-hlink

This is a bug, please file an issue in JIRA :-)

[bleathem]

Pete, if you are saying that #{conversation} should work natively in weld, why is the Seam 3 Faces extension advertising this as a feature?

Not that I'm complaining! just curious...

[skunk]

First one is: https://jira.jboss.org/browse/WELD-548

Dave

[skunk]

And the second one: https://jira.jboss.org/browse/WELD-549

Thanks both.

[pmuir]

Sorry, I mean that the documentation was wrong, and needs to say to use #{javax.enterprise.context.conversation}