JBossDeveloper

I had a similar problem upgrading from 2.0.2.SP1 to 2.2.0.GA.

"JSF1013: Unable to find matching navigation case from view ID '/index.xhtml' for outcome 'verification' and action '#{com.mydomain.abc.action.security.indexAction.login()}'

First working solution I found was using "How to configure multiple page.xml files in Seam 2.2" outlined in post above.

I had two issues with that solution:

1. I had to change each of my *.page.xml files to use the <pages><page>...</page></pages> tags whereas my previous implementation was simply using <page>...</page> without parent <pages></pages> tag.  My application was quite large which made this process very tedious.

2. Updating the components.xml file to register each *.page.xml file within <navigation:pages><navigation:resources>...</navigation:resources></navigation:pages> tags. Again this is a tedious process and triggers memories of working in struts where each action/page had to be configured in the application.

The solution worked but for me but, I found a better, easier way.

Second working solution I stumbled across was to simply update my components.xml file from:

<component name="org.jboss.seam.core.init"> 
     <property name="debug">true</property> 
</component>   

to

<component name="org.jboss.seam.core.init"> 
     <property name="debug">false</property> 
</component>  

I reverted my changes of including the <navigation:pages><navigation:resources>...</navigation:resources></navigation:pages> tags in the components.xml file as well as changing all my *.page.xml files back to only using the <page>...<page> tag.  With just changing the debug property value to false, the JSF1013 issue went away and my navigation worked as it did previously throughout my entire application.

This seems like a bug in seam when running in debug ... yes, no?