Natural Conversations: conversation id evaluated to null -------------------------------------------------------- Key: JBSEAM-3666 URL: https://jira.jboss.org/jira/browse/JBSEAM-3666 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Environment: Ubuntu/Linux 7.10, Tomcat 6.0.16 Reporter: Arron Ferguson This is a repost of https://jira.jboss.org/jira/browse/JBSEAM-3368 which was closed but not fixed. The following errors occur with natural conversations (based on the attached use case): If I'm at page 4 (http://localhost:8080/test/register4.html) and I type: http://localhost:8080/test/register2.html (i.e., without the natural conversation id appended at the end like this: http://localhost:8080/test/register1.html?memberID=2), I get the following evaluated to null error: conversation id evaluated to null: regmem The exception is spewed to the log file but shouldn't be and should use the rules in the pages.xml file for error handling (see attached project). However, even if I type http://localhost:8080/test/register1.html?memberID=2, this is still broken because the rules in the pages.xml file are not being honored. The pages.xml file specifies: <rule if="#{memberreg.acceptedInformation}"> <redirect view-id="/register3.xhtml"/> </rule> Which states that this state should cause a redirect which is not happening. So, to recap, The included test project includes the Ant build script, and in the third party directory a list of the jar files used. Note: you don't need the DA.jar file. The jboss-archive-browsing.jar file is not included in the JBoss Seam download and so I had to grab it from the JBoss site. The version of the jboss-archive-browsing.jar (according to the manifest in the jar) is: Implementation-Version: 2.0.2.Alpha As I mentioned in the previous version of this bug report that was closed, Shane mentioned that there was a little more "noise" in the file than needed. It was quickly discovered however that this project test file was useful for spotting other bugs (I believe he said it helped him find another bug) and so I'm hoping that the same perspective will be used this time around as well. This example project in particular can be used to test many of the use cases and ensure that natural conversation processing is robust. -- 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