Hi,
I'm using remoting and it works great! But unfortunately if I have a page
load partial content though remoting, the request seems to change the
underlying viewState of the JSF view.
I'm using the :
<context-param>
<param-name>org.apache.shale.remoting.FACES_SERVLET_MAPPING_INDEX</param-nam
e>
<param-value>1</param-value>
</context-param>
To point to the *.resources mapping:
<servlet-mapping>
<servlet-name>faces</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>faces</servlet-name>
<url-pattern>*.resources</url-pattern>
</servlet-mapping>
When a call to my resource
/dynamic/runableEntityHandler/getTaskExtraInfo.resources is made my log
shows:
exiting from lifecycle.execute in RESTORE_VIEW(1) because
getResponseComplete is true from one of the after listeners
exiting from lifecycle.execute in RENDER_RESPONSE(6) because
getResponseComplete is true from one of the before listeners
When then I use my page navigation which points to a simple JSF navigation
rule, it reloads the current view in stead of navigating to the new page.
When tried a second time (without using the remoting) the navigation
succeeds.
I have this need-to-click-twice-to-navigate in more situations and it must
have something to do with the underlying JSF viewState. I think there is a
concept here I'm missing, but I don't know what. Can anyone give me some
pointers as to where my problem lies?
Thank you,
joost
