Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 37659 invoked from network); 3 Jun 2007 01:29:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jun 2007 01:29:37 -0000 Received: (qmail 79966 invoked by uid 500); 3 Jun 2007 01:29:41 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 79589 invoked by uid 500); 3 Jun 2007 01:29:40 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 79580 invoked by uid 99); 3 Jun 2007 01:29:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jun 2007 18:29:40 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jun 2007 18:29:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C4919714043 for ; Sat, 2 Jun 2007 18:29:15 -0700 (PDT) Message-ID: <25566434.1180834155802.JavaMail.jira@brutus> Date: Sat, 2 Jun 2007 18:29:15 -0700 (PDT) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Resolved: (JCR-419) Request for other RMI binding options in RepositoryStartupServlet In-Reply-To: <7111051.1146256537557.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-419. ------------------------------- Resolution: Fixed Implemented alternative JNDI binding and access servlets in revision 543821. See JCR-956 for related information. > Request for other RMI binding options in RepositoryStartupServlet > ----------------------------------------------------------------- > > Key: JCR-419 > URL: https://issues.apache.org/jira/browse/JCR-419 > Project: Jackrabbit > Issue Type: Improvement > Components: rmi > Environment: Weblogic 8.1 T3 > Reporter: Paul Dennis > Assignee: Jukka Zitting > Priority: Minor > Fix For: 1.4 > > > The current deployment options for RepositoryStartupServlet bind a local repository to JNDI and/or register a remote ServerRepository via RMI using an RMIServerSocketFactory and LocateRegistry. > The LocateRegistry mechanism does not appear to work by default in a Weblogic environment. > I would like to request the option of binding a ServerRepository in registerRMI() to JNDI using the servlets current context instead of attempting LocateRegistry.createRegistry() and then LocateRegistry.getRegistry(). This JNDI binding option could use a different name so as to not interfere with the JNDI binding attempted in registerJNDI(). > For example, if requested in the web.xml config, registerRMI() could bind the following using it's reference to a ServerRepository: > Context ctx = new InitialContext(); > ctx.bind(repositoryName + "Remote", remote); > This allows for easy remote access using weblogic's native T3 protocol using the following on the client with: > Context ctx = new InitialContext(); // with say -Djava.naming.provider.url and -Djava.naming.factory.initial set > Object ref = ctx.lookup(repositoryName + "Remote"); > LocalAdapterFactory laf = new ClientAdapterFactory(); > Repository remote = laf.getRepository((RemoteRepository) ref); > From the initial tests I have done this appears to work well inside the Weblogic container. > - Paul. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.