-
1. Re: Malformed jsessionid during redirect
mkouba Jan 9, 2014 9:51 AM (in response to daniell)Hi Daniel,
I'm not sure whether jsessionid may be part of the viewId but in any case it seems you can get rid of ".undefined" suffix by setting your own instance-id in AS7 web subsystem. See also https://community.jboss.org/thread/201760.
-
2. Re: Malformed jsessionid during redirect
daniell Jan 9, 2014 10:05 AM (in response to mkouba)Hi Martin!
Thanks for your answer. I've seen, that i can set the instance-id to some value to eliminate the ".undifined"-suffix. But then, the URL contains the jsessionid with the specified instance-id as suffix. Thus instead of ".undefined" there is ".mynode" (or whatever is specified) which becomes replaced by ".jsf" and the problem still exists.
-
3. Re: Malformed jsessionid during redirect
mkouba Jan 9, 2014 11:08 AM (in response to daniell)I see. AFAIK a dot is not a reserved character and doesn't have to be encoded, i.e. "1234.undefined" is a legal session ID. So with regard to viewId question - I did not find anything relevant in the JSF spec so far.
-
4. Re: Malformed jsessionid during redirect
mkouba Jan 9, 2014 11:23 AM (in response to daniell)Perhaps FacesUrlTransformer should rather use FacesContext.getViewRoot().getViewId() to obtain the correct viewId (without the jsessionid). But I'm no JSF expert so I may be missing something...
-
5. Re: Malformed jsessionid during redirect
daniell Jan 10, 2014 3:13 AM (in response to mkouba)Me too. 7.4.2. of the spec states that the "?" and all following characters should be removed from the viewId when looking for a navigation-outcome, but the path-parameter introduced by a ";" is not mentioned anywhere. The current behavior of getActionURL() is exactly described in section "7.5.2 Default ViewHandler Implementation" (replacement of the extension beginning from the last period-position).
I still think that the page-parameter is not part of the view-id. When looking in the configuration-file which does the navigation, obviously the page-params cannot be part of it (otherwise a navigation-rule from-view-id could not work).
-
6. Re: Malformed jsessionid during redirect
mkouba Jan 10, 2014 6:17 AM (in response to daniell)Actually ConversationPropagationFilter is deprecated and should not be registered any more. This was fixed in Weld integration code. So either switch to EAP 6.1.0 or WildFly8. See also https://issues.jboss.org/browse/WELD-1262 and https://issues.jboss.org/browse/JBPAPP6-1664.
-
7. Re: Malformed jsessionid during redirect
daniell Jan 13, 2014 7:27 AM (in response to mkouba)I deployed the application using EAP 6.2.0. The suffix of the JSessionID is not modified any more and it works as expected.
For those facing the same problem and tied to the JBoss AS 7.1.1: using the PrimeFaces' p:commandLink instead of h:commandLink worked around the problem (since this makes an ajax-request).