Return-Path: 
 <user-return-24664-apmail-commons-user-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-user-archive@www.apache.org
Received: (qmail 45946 invoked from network); 24 Jun 2010 20:24:17 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 24 Jun 2010 20:24:17 -0000
Received: (qmail 10872 invoked by uid 500); 24 Jun 2010 20:24:16 -0000
Delivered-To: apmail-commons-user-archive@commons.apache.org
Received: (qmail 10295 invoked by uid 500); 24 Jun 2010 20:24:15 -0000
Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@commons.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@commons.apache.org>
List-Post: <mailto:user@commons.apache.org>
List-Id: <user.commons.apache.org>
Reply-To: "Commons Users List" <user@commons.apache.org>
Delivered-To: mailing list user@commons.apache.org
Received: (qmail 10187 invoked by uid 99); 24 Jun 2010 20:24:15 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jun 2010 20:24:15 +0000
X-ASF-Spam-Status: No, hits=-0.2 required=10.0
	tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of rahul.akolkar@gmail.com
 designates 209.85.212.43 as permitted sender)
Received: from [209.85.212.43] (HELO mail-vw0-f43.google.com) (209.85.212.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jun 2010 20:24:08 +0000
Received: by vws5 with SMTP id 5so2662286vws.30
        for <user@commons.apache.org>; Thu, 24 Jun 2010 13:23:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:in-reply-to
         :references:date:message-id:subject:from:to:content-type;
        bh=ICL9h1UgtLNgFH1IJoMmQrX0oIyO9MZY4iDl2bSlQw8=;
        b=rXX3M+uJSumZj/INw8SBE7/82Jqkxx1HeZvLmjK8uExuof2ibGXO97FfGYIJcV6LeD
         glJFNkt2NUl0cmfBGz6Gqj06JRz1PRwYDiDqVtg/KiXjhWvkhWyb9Y7lWNRICtE+fypr
         f7+1xPx/TpXN62wBl1doAVU5ZJJbb3Fl5uXT8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=UD0GujhylCaD3w1H2vO/i7gi0Y0zxWhMbC9bltSoX5kziAeXcMjTqBSZIhAut76Nx6
         P8kYvVjz8soLrN49C1lx+LkLsa4/hvR9pourz0JSgkBrp4ep3ZHJD5T4MXYD+cXr2qb/
         lWvo7m9CVRth2eDbhQF+/YjcUyxOg7K41+oBY=
MIME-Version: 1.0
Received: by 10.220.58.69 with SMTP id f5mr1405455vch.145.1277411027870; Thu,
	24 Jun 2010 13:23:47 -0700 (PDT)
Received: by 10.220.111.6 with HTTP; Thu, 24 Jun 2010 13:23:47 -0700 (PDT)
In-Reply-To: <AANLkTilyB8iWIgwdzBYK940sLyiYL_4kbj6hJXkea22-@mail.gmail.com>
References: <AANLkTilyB8iWIgwdzBYK940sLyiYL_4kbj6hJXkea22-@mail.gmail.com>
Date: Thu, 24 Jun 2010 16:23:47 -0400
Message-ID: <AANLkTim1DpboIZVYGhdcfD1095NNr77sv1ErdwTgLThh@mail.gmail.com>
Subject: Re: [scxml] templates, url and parameters
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Commons Users List <user@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 21, 2010 at 2:50 PM, Fabrizio Morbini <fmorbini@gmail.com> wrote:
> Hi, concerning the wiki page:
> http://wiki.apache.org/commons/SCXML/Tutorials/Templating
>
> There the src attribute is given the value:
> "accept-connection.scxml?call-id=incoming-line".
>
> How is the parameter call-id used/accessed?
<snip/>

The point that needs to be made better perhaps on that page is that
the URI needn't point to a static resource. So what is src'ed in could
be any dynamic server-side resource that generated an SCXML document
or fragment in some parameterized fashion where the number and
semantics of the parameters are application specific.

In the context of templating, one could imagine such a parameterized
script, where the dynamic portions are limited to appending unique
prefixes to ids and idrefs such that the same document or fragment may
be src'ed in multiple times (since each src'ed in URI would create
unique ids for the including state machine's scope -- along the lines
of "foo.scxml.jsp?suffix=1" and "foo.scxml.jsp?suffix=2").


> Would the same be possible also with xinclude?
>
<snap/>

Using XInclude to similarly point to dynamic resources is possible
(and even fragments, using an appropriate XPointer, may be possible if
the parser has the necessary support).

The said dynamic resource/script is part of the application (and needs
to be authored and deployed).

-Rahul


> thanks,
> fabrizio.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org