Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 26367 invoked from network); 28 Jun 2007 16:55:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jun 2007 16:55:18 -0000 Received: (qmail 84031 invoked by uid 500); 28 Jun 2007 16:55:15 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 83988 invoked by uid 500); 28 Jun 2007 16:55:15 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 83977 invoked by uid 99); 28 Jun 2007 16:55:15 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jun 2007 09:55:15 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of rahul.akolkar@gmail.com designates 64.233.162.225 as permitted sender) Received: from [64.233.162.225] (HELO nz-out-0506.google.com) (64.233.162.225) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jun 2007 09:55:10 -0700 Received: by nz-out-0506.google.com with SMTP id l8so111064nzf for ; Thu, 28 Jun 2007 09:54:49 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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; b=XZCxsN9XjDLq47QpWGhFuE3jOYmCvPextLwMEWBZrdCA4KPKSKTKzbDbOP42BlNb1e78mdS+BUztgYzBc+eliF/Q9HEOUFgMp/nghVhOn/mtD++eSvWJjkxOgRysrGSyrBSvRYSPYnulNgo1vYiArvOV7tdyQLJgI97mcBl0LKI= 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=fLF9H7/03I2cGQqLemSWW1vTySWTx06iGukQ4d7LfLomGWMkZcMgDnELLF8t5g2ytlDfSo7wjUfGCKUJ7Q5fbtj51xGlOZwlOGZkSI8Lgb2lwHWbcEEsIDbjOsGaT5b6aWFvohbE15DwL6VuoxSqCg2WlfPsr3Gz62DJ9mt217w= Received: by 10.65.224.11 with SMTP id b11mr1268072qbr.1183049688955; Thu, 28 Jun 2007 09:54:48 -0700 (PDT) Received: by 10.65.186.12 with HTTP; Thu, 28 Jun 2007 09:54:48 -0700 (PDT) Message-ID: Date: Thu, 28 Jun 2007 12:54:48 -0400 From: "Rahul Akolkar" To: "Jakarta Commons Users List" Subject: Re: [SCXML] Querying if an event would cause a transition In-Reply-To: <380707.50289.qm@web50903.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <380707.50289.qm@web50903.mail.re2.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org On 6/28/07, Nestor Urquiza wrote: > Hi, > > Not to mention that some custom actions could have to be evaluated before knowing which transition will apply. > > It might mean that some side effects could come into scene, and if they do the "introspection mode" cannot be used. > Actions aren't executed unless a transition is actually followed, so we should be OK there. However, the guard conditions on candidate transitions would need to be evaluated, and they would need to be side-effect free (as they should be). In other words, the act of identifying which transition(s) should be followed is idempotent. -Rahul > Thanks, > > -Nestor > > ----- Original Message ---- > From: Rahul Akolkar > To: Jakarta Commons Users List > Sent: Wednesday, June 27, 2007 11:05:54 AM > Subject: Re: [SCXML] Querying if an event would cause a transition > > Please prefix the email subject with [SCXML], since this mailing list > is shared across all Commons components. I've added the prefix here. > > On 6/27/07, Christopher Giblin wrote: > > > > Hi, > > I am new to Commons SCXML. > > Is it possible to determine whether an event would result in a transition, > > without that transition occuring? Including evaluation of transition > > conditions? > > > While the idea is interesting, we do not have such an "introspection mode". > > It wouldn't take too much effort to implement it, but: > > a) Would probably increase the code smell factor a tad (if in > introspection mode, then follow transition else just report back etc.) > > b) Would require some API additions that might warrant a major release. > > If you don't mind sharing in this public forum, why do you need such > introspection? The SCXML specification doesn't talk about this. > Understanding that interaction pattern may or may not help better > answer the question, we will have to see :-) > > -Rahul > > > > Thanks, > > chris > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org