Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 36129 invoked from network); 9 Aug 2005 14:12:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Aug 2005 14:12:15 -0000 Received: (qmail 20984 invoked by uid 500); 9 Aug 2005 14:12:06 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 20967 invoked by uid 500); 9 Aug 2005 14:12:05 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 20950 invoked by uid 99); 9 Aug 2005 14:12:05 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2005 07:12:05 -0700 X-ASF-Spam-Status: No, hits=4.0 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,NO_REAL_NAME,RCVD_BY_IP,RCVD_DOUBLE_IP_LOOSE,RCVD_NUMERIC_HELO X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [204.127.198.54] (HELO rwcrmhc12.comcast.net) (204.127.198.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2005 07:12:28 -0700 Received: from 204.127.197.111 ([204.127.197.111]) by comcast.net (rwcrmhc14) with SMTP id <20050809141128014008haere>; Tue, 9 Aug 2005 14:11:28 +0000 Received: from [170.135.241.45] by 204.127.197.111; Tue, 09 Aug 2005 14:11:28 +0000 From: pietila.meghan@comcast.net To: axis-user@ws.apache.org Subject: Re: stumped on deserializer problem Date: Tue, 09 Aug 2005 14:11:28 +0000 Message-Id: <080920051411.16865.42F8B990000061D5000041E12200737478020E08090A03D20E04079B0A079F@comcast.net> X-Mailer: AT&T Message Center Version 1 (Dec 17 2004) X-Authenticated-Sender: cGlldGlsYS5tZWdoYW5AY29tY2FzdC5uZXQ= X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Sounds great, Thad! I'm currently stuggling with the custom (de)serialization-within-custom-(de)serialization problem, so I'll appreciate your writeup if I don't get it working first! Meghan Pietila Granite Consulting On Tuesday 08 August 2005 17:49, thad@mindwrap.com wrote: >Bingo! I've cracked the custom (de)serialization for my classes. Moreover, >I've managed to figure out custom (de)serialization for a class when it >contains members that also require custom (de)serialization. >The later case was difficult because the exception I was getting in my >real-world problem didn't point to the source of the error. To solve this, I >created a simplified set of classes and (de)serializer. This pointed me >straight to the problem. I intend to write the axis-dev folks and offer a >write-up and my example for the user's manual.