Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 50500 invoked from network); 15 Nov 2007 19:11:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Nov 2007 19:11:00 -0000 Received: (qmail 9187 invoked by uid 500); 15 Nov 2007 19:10:46 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 9121 invoked by uid 500); 15 Nov 2007 19:10:46 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 9112 invoked by uid 99); 15 Nov 2007 19:10:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2007 11:10:46 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rahul.akolkar@gmail.com designates 209.85.128.187 as permitted sender) Received: from [209.85.128.187] (HELO fk-out-0910.google.com) (209.85.128.187) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2007 19:10:16 +0000 Received: by fk-out-0910.google.com with SMTP id 18so92527fkq for ; Thu, 15 Nov 2007 11:09:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=UXHk7cJk6CZBNk62QkHKnzDtE4nQEC7fMrzldKReUHA=; b=DJTECh15eFm5Uc10tDUyjaX/eTqB9JnoQPG5IpEzn7vUaKB/d+zMfU2undZ2U718FFyWrcvnguCBlCNp11ZvT6rdHTDds2MX2UPHTqDG0p8T3l4Aq10mlWk/xzqy+OXC+1FPc5n1bnNkJKN4rOC97SeOxtMKtjhAB+zBVz7V18Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TNcj1PATNN85IzyZKhk3OT3FN9y85+xXdoBSzdLnAKBsByF5Rb9UROl3JmMrx8mCnPQZpQ1DPf3WKKKUMA02Y/p1uHVfGpYYL6Y6AO0YCTA4ED2QrNxptdIyJSqBif3Ur4hRYFujvolyuFJYb5fpboyfrdIxkQCLRUwVHOxlFeM= Received: by 10.82.155.10 with SMTP id c10mr2743672bue.1195153796582; Thu, 15 Nov 2007 11:09:56 -0800 (PST) Received: by 10.82.140.14 with HTTP; Thu, 15 Nov 2007 11:09:56 -0800 (PST) Message-ID: Date: Thu, 15 Nov 2007 14:09:56 -0500 From: "Rahul Akolkar" To: "Jakarta Commons Developers List" Subject: Re: A newbie question for SCXML and its persistence In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org Please do not reply in an existing thread and ask an unrelated question, start a new thread instead. Response below ... On 11/15/07, Hongming Xiao wrote: > Since SCXMLExecutor implemented Serializable interface, I guess the simplest > way is to store serialized object somewhere for recovery purpose. Does it > work? And/or, any other suggestion? > Thanks in advance. Yes, it works. In fact, many of our JUnit test cases that run nightly round trip (serialize and then deserialize) SCXMLExecutor instances. You are correct this is the simplest persistence mechanism at the moment. There was some discussion towards easily allowing alternative persistence mechanisms, see SCXML-20 [1], for example. We need to revisit this later (at v1.0 time). -Rahul [1] http://issues.apache.org/jira/browse/SCXML-20 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org