The first time after loading the app on a fresh Android emulator, the app CSS files didn't load, and navigating to the ExtLib test page led to a complaint that a class name including an encoded query string with JSESSIONID wasn't found. Launching the app again, though, made it behave like normal, without the ID in the query string.
It's not necessarily the end of the world of Jetty serves up JSESSIONID in the URL, but it's odd that it did once.
Regardless, it'd be good to figure out why it thought that the session ID was part of the view name and not just the query string. Unless it was entirely a fluke, there may be something in the runtime that passes the whole server-relative URL in as the path info instead of splitting out the query string portion.
The first time after loading the app on a fresh Android emulator, the app CSS files didn't load, and navigating to the ExtLib test page led to a complaint that a class name including an encoded query string with JSESSIONID wasn't found. Launching the app again, though, made it behave like normal, without the ID in the query string.
It's not necessarily the end of the world of Jetty serves up JSESSIONID in the URL, but it's odd that it did once.
Regardless, it'd be good to figure out why it thought that the session ID was part of the view name and not just the query string. Unless it was entirely a fluke, there may be something in the runtime that passes the whole server-relative URL in as the path info instead of splitting out the query string portion.