Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 29305 invoked from network); 5 Jul 2005 20:36:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Jul 2005 20:36:18 -0000 Received: (qmail 362 invoked by uid 500); 5 Jul 2005 20:36:15 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 313 invoked by uid 99); 5 Jul 2005 20:36:13 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2005 13:36:13 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id AEE9E15 for ; Tue, 5 Jul 2005 22:36:10 +0200 (CEST) Message-ID: <1780992928.1120595770715.JavaMail.jira@ajax.apache.org> Date: Tue, 5 Jul 2005 22:36:10 +0200 (CEST) From: "Jukka Zitting (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Resolved: (JCR-159) JCR-RMI UnmarshalException when calling getProperty() In-Reply-To: <1890166455.1120560551407.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-159?page=all ] Jukka Zitting resolved JCR-159: ------------------------------- Resolution: Fixed Thanks for the bug report! This problem should now be fixed in revision 209313. About the build warnings, they might be caused by JCR-162, and are most probably a result of the recent code reorganization (JCR-157). Please file a different bug report if the problems continue. > JCR-RMI UnmarshalException when calling getProperty() > ----------------------------------------------------- > > Key: JCR-159 > URL: http://issues.apache.org/jira/browse/JCR-159 > Project: Jackrabbit > Type: Bug > Components: core > Environment: Windows XP, j2se 1.4.2_07 > Reporter: Richard Osbaldeston > Assignee: Jukka Zitting > > I've been trying to get the JCR-RMI adaptors going to talk to my noddy test repository. It seems I can successfully login and traverse the nodes (getNode etc..) but whenever I try to get something from a nt:resource (actually I've subclassed nt:resource to add our own properties) I get the following exception: > org.apache.jackrabbit.rmi.client.RemoteRepositoryException: error unmarshalling return; nested exception is: > java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.jackrabbit.value.BinaryValue: error unmarshalling return; nested exception is: > java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.jackrabbit.value.BinaryValue > at org.apache.jackrabbit.rmi.client.ClientProperty.getValue(ClientProperty.java:139) > at org.apache.jackrabbit.rmi.client.ClientProperty.getString(ClientProperty.java:131) > at ClientTest.main(ClientTest.java:20) > Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: > java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.jackrabbit.value.BinaryValue > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:164) > at org.apache.jackrabbit.rmi.server.ServerProperty_Stub.getValue(Unknown Source) > at org.apache.jackrabbit.rmi.client.ClientProperty.getValue(ClientProperty.java:137) > ... 2 more > My svn is up-to-date as of this morning 2005/7/5 although the maven builds don't inspire much confidence as it falls over with Jelly exceptions at various points and there's a couple of dozen unit tests that fail. Don't know if this is the norm, the maven reports on the jackrabbit main site reports suggest not? But calling the same code with an in-process repository works fine. -- 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