OK. No answers. This could mean on of the following:
- Noone knows
- Noone cares
- It's so trivial that I could figure it out by my own.
Wich one is it?
Anyway. Since this is vital for my application I made up my mind and figured something out which could do it for me:
If I write an extra servlet (or a filter? but it has to be somewhere before the jsessionid is created) which handles all requests and passes them to the seam/jsf servlet I could:
- case: If the request contains no sessionid: remove it from the response, too. (remove cookie etc.)
- case: If the request contains a sessionid: pass through to seam/jsf servlet and don't alter response
- case: If some condition occurs (don't know how exactly. Has to be some flag indicating that someone wants to log in): pass it through anyways so that the next request will contain a sessoinid. Proceed with 1.
So: Would that work or do I miss something? Has anyone tried doing it this way?
I'm not completely sure what you're going for, but it's not a Seam question. You might have more luck asking on a different forum.