Maybe I'm missing something here. But calling setStoresIDsInURLs(false) from
one's session constructor takes care of this issue:
public Session() {
super();
setStoresIDsInURLs(false);
}
We were caught by surprise with this new "feature". But the above one-liner
took care of it. We actually did this in our BaseSession class, which all
apps subclass from. While we're on the subject of session IDs, also do this
in the constructor:
setStoresIDsInCookies(true);
^James
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
