Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Exception When CommandLink Clicked

 
Chacko Chen
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I have simple one to one page navigation, first page to second page and from second page to first page using faces-config.xml
When I click commandLink in second page to navigate back to first page, I am getting the following exception. How can I resolve this issue?



My faces-config.xml


 
Ilari Moilanen
Ranch Hand
Posts: 199
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You have defined two pages and outcomes, first.jspx and second.jspx but in the exception there is also a third page list.jspx. What is that? Is it one of your own pages or is it part of the ICEfaces (I guess you use ICEfeces but you do not mention it anywhere)? In any case your post is very unclear since you do not even mention what JSF version or implementation are you using.

The exception iteself may come from your own code as well so check that first.
 
Chacko Chen
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sorry about the third page list.jspx, it is nothing but first.jspx. I couldn't find any exception in that, however after navigating to second.jspx even when I refresh I am getting the same exception.

My JSF version is 1.1 and Icefaces is 1.8.2.




 
Ilari Moilanen
Ranch Hand
Posts: 199
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
OK, this might be a ICEfaces specific issue and I am not very familiar with ICEfaces. Maybe someone with more experience with icefaces can help you.

The exception itself is a little peculiar and since there is no "Caused By" part in it it seems that the exception is originating from code mady be evermind.com. I could be wrong. And in any case it could be caused be something very simple like forgetting to put right scope for your managed beans etc. Sorry, just guessing here and will shut up now
 
Chacko Chen
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks again for the reply.

If I add redirect in faces-config.xml, error disappears.



 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic