Return-Path: Delivered-To: apmail-commons-issues-archive@locus.apache.org Received: (qmail 83554 invoked from network); 28 Nov 2008 14:54:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2008 14:54:06 -0000 Received: (qmail 27437 invoked by uid 500); 28 Nov 2008 14:54:16 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 27386 invoked by uid 500); 28 Nov 2008 14:54:16 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 27375 invoked by uid 99); 28 Nov 2008 14:54:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2008 06:54:16 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2008 14:52:57 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5A176234C2A7 for ; Fri, 28 Nov 2008 06:53:44 -0800 (PST) Message-ID: <649173552.1227884024367.JavaMail.jira@brutus> Date: Fri, 28 Nov 2008 06:53:44 -0800 (PST) From: "Rahul Akolkar (JIRA)" To: issues@commons.apache.org Subject: [jira] Updated: (SCXML-95) profile attribute of In-Reply-To: <1764423084.1227738164882.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/SCXML-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Akolkar updated SCXML-95: ------------------------------- Fix Version/s: 0.10 I think we should start with (1). Something like (2) would be good if there is some sort of SCXMLExecutor 'factory' that the application maintains, so its more an application concern I think. Setting fix version to v0.10. > profile attribute of > ---------------------------- > > Key: SCXML-95 > URL: https://issues.apache.org/jira/browse/SCXML-95 > Project: Commons SCXML > Issue Type: New Feature > Affects Versions: 0.8 > Reporter: Ingmar Kliche > Fix For: 0.10 > > > SCXML defines a profile attribute. This should be reflected in the model. The profile attribute could be used in two ways: > 1) check profile name within parsed document against registered context/evaluator and throw error in case of mismatch > 2) allow registration of multiple context/evaluators and executor should instantiate context/evaluator based on profile attribute of parsed document. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.