New thread started from thread entitled [avalon-jetty] Status update "Stephen McConnell" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I think we have to fix the SessionManager exposure first. The problem > is that this component will probabaly get a reasonable level of > attention and as such - we are just going to cause breakages in the near > future. >
If I can understand the problem a bit more clearly, then maybe I could make some changes in the next few days. To help, here is one of your post from the same thread: > I did had a problem concerning the SessionManager that may have crept in > as a result of the spi/impl separation. The value passed to the web-app > is a jetty SessionManager but the value acquired from the service > manager is a http.SessionManager (resulting in a class cast exception). > I've changed the http.SessionManager to extend jetty.SessionManager in > the SPI package as a temporary solution to get things going. > Hmmmmmm... Can you give me code example of where/when you were getting a cast exception? I wasn't having this problem, nor can I understand under what circumstances you were trying to do a class cast. > However - we will need to sort this out in order for the SPI to be > independent of the jetty implementation > (which I think we can do by > building a session instance dynamically based on meta-info pulled in > from the servlet class) and maybe through this we can eliminate the need > for servlet specific session classes which would bring things down to > just the servlet class and @avalon tags. I would like to get rid of having to extend the AvalonSessionManager for each "application" that uses avalon-http. This is an artifact from Henson's block, and basically provides a mechanism for the Jetty Session Manager to "carry" a ServiceManager instance that knows about the dependent services you want the servlet(s) to have access to. If there's a better and cleaner way of getting the service dependencies into the servlet container's session manager, then I'm all for that. Let's noodle on it and discuss it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
