[jboss-user] [JBoss Seam] - Re: Breaking changes to pageflow

rpiaggio do-not-reply at jboss.com
Tue Jul 11 11:43:02 EDT 2006


Ok, solved the problem.

The ClassCastException seems to happen when the flow cannot land on a page. In this case, the problem of not working on the page action seemed to derive from having an unnamed transition on the start-state. This would match on a normal action but not on the page action. This is how the pageflow and code looked like:


  |    <start-state name="start">
  |    	  <transition to="selectSource">
  |    	  	  <action expression="#{sourceManager.selectSource}"/>
  |    	  </transition>
  |    </start-state>
  | 
	@Begin(pageflow="PaymentAuthorization")
  | 	public	void	start() {
  | 	}
  | 

Everything worked OK when I changed to:
   <start-state name="start">
  |    	  <transition name="proceed" to="selectSource">
  |    	  	  <action expression="#{sourceManager.selectSource}"/>
  |    	  </transition>
  |    </start-state>	@Begin(pageflow="PaymentAuthorization")
  | 	public	String	start() {
  | 		return	"proceed";
  | 	}
  | 

If this is a bug, it's a very minor one.

Actually, I think that having an unnamed transition should make it the default one, and should always be triggered when all other transitions don't match. This would ensure the pageflow always works. Any opinions on this feature request before I JIRA it?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957052#3957052

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957052



More information about the jboss-user mailing list