Hot Deploy of Toplink requires OC4J restart

Question

Hi
I have encountered the issue where redeploying an EAR containing Toplink references requires a restart of the OC4J instance.
I understand that the Toplink session manager is not re-initialized within this deployment, and therefore an execption is thrown - "missing descriptor".
Is there any way round this; i.e. having to execute an oc4j restart following each EAR file deployment?
Thanks
Marc

Answer 1

Marc,
Here is a sample method I use that leverages the new API.
     * Helper method to lookup the singleton server session using the sessions
     * configuration location and session name. It ensure that the session is
     * logged in but will not refresh it if it already exist. It also checks to
     * ensure that the class-loader has not changed. If it has the SessionManager
     * will force the session to be refreshed.
     * @param sessionsXML Resource name for the sessions.xml configuration file.
     *                    Typically this is 'META-INF/sessions.xml'
     * @param sessionName Name of the session. This method assumes it is a server
     *                    session
     * @return The server session already logged in
    private Server lookupSession(String sessionsXML, String sessionName) {
        XMLSessionConfigLoader loader =
            new XMLSessionConfigLoader(sessionsXML);
        ClassLoader cl = Thread.currentThread().getContextClassLoader();
        return
            (Server) SessionManager.getManager().getSession(loader,
                                                            sessionName,
                                                            cl,
                                                            true, // login
                                                            false, // refresh
                                                            true); // check loader
    }Doug