Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 17344 invoked from network); 30 Nov 2006 09:56:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Nov 2006 09:56:47 -0000 Received: (qmail 13718 invoked by uid 500); 30 Nov 2006 09:56:53 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 13690 invoked by uid 500); 30 Nov 2006 09:56:53 -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 13663 invoked by uid 99); 30 Nov 2006 09:56:53 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2006 01:56:53 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= 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; Thu, 30 Nov 2006 01:56:43 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3E47B7142FD for ; Thu, 30 Nov 2006 01:56:22 -0800 (PST) Message-ID: <29514652.1164880582252.JavaMail.jira@brutus> Date: Thu, 30 Nov 2006 01:56:22 -0800 (PST) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Resolved: (JCR-206) Extend the current RMI implementation to support IIOP MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/JCR-206?page=all ] Jukka Zitting resolved JCR-206. ------------------------------- Resolution: Won't Fix I'm resolving this as Won't Fix due to the lack of demand and the fact that there is no easy way to achieve proper garbage collecting with IIOP. The existing patches change some fundamental parts of the current implementation (for example turning the serialized value instance to remote references), so I will not even apply them partially. Please reopen this issue if you'd still like to see this implemented and have some ideas on how to solve the garbage collecting issue. > Extend the current RMI implementation to support IIOP > ----------------------------------------------------- > > Key: JCR-206 > URL: http://issues.apache.org/jira/browse/JCR-206 > Project: Jackrabbit > Issue Type: Improvement > Components: rmi > Environment: Win XP, Sun JDK 1.5.0 > Reporter: Michael Singer > Assigned To: Jukka Zitting > Attachments: o.a.j.rmi.remote.additions.zip, o.a.j.rmi.server.additions.zip, rmi-iiop.patch > > > In order to get remote access to jackrabbit from .NET it would make sense to extend the current RMI implementation to support RMI-IIOP [1]. The use of projects like IIOP.NET from http://iiop-net.sourceforge.net/ would then be possible. > What do you think? > [1] http://java.sun.com/j2se/1.5.0/docs/guide/rmi-iiop/index.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira