on redeployment glassfish recreates sessions with same sessionID - without calling my sessionListener ?
Working with glassfish 3.1.2 - whenever I hit save on eclipse (juno) it redeploys my app (a photo submitting site). When I am submitting a photo I create a session - the session gets invalidated by redeployment (the request attributes are not invalidated however - correct ?) but apparently glassfish creates a session with the same ID - without calling the session listener. Is this expected behavior ? How could I amend it ?