Return-Path: 
 <dev-return-124215-apmail-commons-dev-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-dev-archive@www.apache.org
Received: (qmail 96291 invoked from network); 24 Feb 2011 03:55:45 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 24 Feb 2011 03:55:45 -0000
Received: (qmail 1748 invoked by uid 500); 24 Feb 2011 03:55:45 -0000
Delivered-To: apmail-commons-dev-archive@commons.apache.org
Received: (qmail 1158 invoked by uid 500); 24 Feb 2011 03:55:41 -0000
Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@commons.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@commons.apache.org>
List-Post: <mailto:dev@commons.apache.org>
List-Id: <dev.commons.apache.org>
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Delivered-To: mailing list dev@commons.apache.org
Received: (qmail 1150 invoked by uid 99); 24 Feb 2011 03:55:40 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 03:55:40 +0000
X-ASF-Spam-Status: No, hits=1.8 required=5.0
	tests=FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of rahul.akolkar@gmail.com
 designates 74.125.82.41 as permitted sender)
Received: from [74.125.82.41] (HELO mail-ww0-f41.google.com) (74.125.82.41)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 03:55:33 +0000
Received: by wwb17 with SMTP id 17so1123058wwb.0
        for <dev@commons.apache.org>; Wed, 23 Feb 2011 19:55:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type:content-transfer-encoding;
        bh=xoSP5LTNV4MBDVOFX6rObASk5NFtWxGpMoEK7QsfqRc=;
        b=vw9qhOAzwMQG+Jd+iNuUiuGZBl5ybD9LGCKeLC21iw9+PhhMYs8WHinlQi3Sn/sTF2
         ZJad1/+BWIudKIyWnn2CYFVM92v+iPuNwE+oDmILvTA0fx1N1O3J7GHJpIlgJtu1/zad
         qZZYrb4+MZYWB1hhH54YVeR2xsYQqVDR6bZAs=
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:content-transfer-encoding;
        b=krtHKhNh37uRtdXpyOhX544juoGFU80TLNIXySjFxcnnOe/U7Aeb8aGhirFjpxChzj
         3o2AMdcAPy3g1nAMCStD+zRYUU044jvUJDGZ0iXs9ARaY+r39or/5QuCAbIDAqNTHxKd
         JvWQaVZz88eLSOMGOvOTe5Rg1watYHT62T7uM=
MIME-Version: 1.0
Received: by 10.216.150.129 with SMTP id z1mr210316wej.113.1298519712092; Wed,
 23 Feb 2011 19:55:12 -0800 (PST)
Received: by 10.216.172.16 with HTTP; Wed, 23 Feb 2011 19:55:12 -0800 (PST)
In-Reply-To: <AANLkTikY82C2PAiDG=GHqA71FbgD8YFHTy5Tq3FqPRB2@mail.gmail.com>
References: <AANLkTimbw8RqMmniCcb8Ltvf_aMc=ALenQUuVyn4=UML@mail.gmail.com>
	<AANLkTi=SfabaPpcadpX23tbryYbB0ZgMeGEE+StOFn_7@mail.gmail.com>
	<AANLkTikY82C2PAiDG=GHqA71FbgD8YFHTy5Tq3FqPRB2@mail.gmail.com>
Date: Wed, 23 Feb 2011 22:55:12 -0500
Message-ID: <AANLkTikSxi3pFmi-S6qB2Vj4JAjbZn7nhYwedJSo9r7j@mail.gmail.com>
Subject: Re: [SCXML] Do Apache Commons SCXML support XInclude and XPath 2.0?
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

2011/2/23 Gavin Lei <gavingui2011@gmail.com>:
> Hi Rahul,
>
> Thank you for your answer. It means that we can take some measures to
> support XInclude and XPath 2.0 in Commons SCXML. Commons SCXML use
> Digester to support XInclude and use JDK's API to support XPath( In my
> memory, JDK use Apache Xalan library to support XPath, so there's a
> small question, Xalan support XPath 1.0 only, may be Commons SCXML
> support XPath 1.0 only ).
>
<snip/>

I pointed to an Evaluator that uses javax.xml.xpath in the previous
email. Similarly, one could author an Evaluator impl that uses Saxon,
for example, to get XPath 2.0 support. Evaluators are meant to be
pluggable (with corresponding Context impls) in Commons SCXML.


> Nowadays, I am developing a Flex ActionScript SCXML engine --
> SCXML4Flex [1], we have finished some basic functions (such as SCXML
> document parse job, custom action support ) for it. In the future,
> there are still three milestones for this project: XInclude support,
> XPath 2.0 support andEvent I/O Processors support. So, you have been
> working with SCXML for years, do you have any suggestions about these
> features ?
>
<snap/>

We've talked about XInclude and XPath 2.0 already in this thread.
Commons SCXML doesn't provide all the I/O processors yet (in the
manner described in the spec), so don't have much to add there.

-Rahul


>
> [1] http://code.google.com/p/scxml4flex/
>
> =D4=DA 2011=C4=EA2=D4=C224=C8=D5 =C9=CF=CE=E76:25=A3=ACRahul Akolkar <rah=
ul.akolkar@gmail.com> =D0=B4=B5=C0=A3=BA
>> 2011/2/23 Gavin Lei <gavingui2011@gmail.com>:
>>> Hi guys,
>>> Do Apache Commons SCXML support XInclude and XPath 2.0? Today i want
>>> to do some experiments to confirm this, but it seems that Commons
>>> SCXML does not support XInclude and XPath 2.0.
>>> 1. about XInclude
>>> I try to run such a SCXML document in Commons SCXML engine:
>>>
>>> <scxml initial=3D"s1" xmlns:xi=3D"http://www.w3.org/2001/XInclude">
>>> <xi:include href=3D"datamodel.xml" parse=3D"xml"/>
>>> <state id=3D"s1">
>>> <onentry>
>>> <script>x =3D x + 5;</script>
>>> </onentry>
>>>        <transition cond=3D"x &gt; 1" target=3D"print">
>>> </transition>
>>>    </state>
>>>    <state id=3D"print">
>>>     <onexit>
>>>     <log label=3D"Result" expr=3D"x"/>
>>>     </onexit>
>>>     <transition event=3D"result" target=3D"result" />
>>>    </state>
>>>   <final id=3D"result"/>
>>> </scxml>
>>>
>>> datamodel.xml:
>>>
>>> <datamodel>
>>> <data id=3D"x" expr=3D"1"/>
>>> </datamodel>
>>>
>>> But it seems that Commons SCXML does not work for me. So, i want to
>>> confirm that Commons SCXML support XInclude or not.
>>>
>> <snip/>
>>
>> It (the last release) doesn't, but it won't be difficult to add. The
>> last release used Commons Digester for parsing. Since then, Digester
>> has added XInclude support, so the actual change now necessary to the
>> SCXMLParser class is minimal.
>>
>> It may be possible to parse documents containing XInclude using the
>> new and unreleased parser class (i.e. SCXMLReader in the J6 branch in
>> SVN) by passing the appropriate inputs/options to the StAX parser.
>>
>>
>>> 2, about XPath 2.0
>>> In W3C's SCXML recommendation specification, it show that SCXML engine
>>> should support XPath 2.0 and XPath 2.0 functions. And i tried a SCXML
>>> document with this State in it:
>>>
>>> <state id=3D"errorSwitch" xmlns:fn=3D"http://www.w3.org/2005/xpath-func=
tions">
>>>  <datamodel>
>>>    <data id=3D"time"/>
>>>  </datamodel>
>>>
>>>  <onentry>
>>>    <assign location=3D"$time" expr=3D"fn:current-dateTime()"/>
>>>  </onentry>
>>>
>>>  <transition cond=3D"fn:year-from-dateTime($time) > 2009" target=3D"new=
Behavior"/>
>>>  <transition target=3D"currentBehavior"/>
>>> </state>
>>>
>>>
>>>
>>> But it seems that Commons SCXML does not work for me too. I think
>>> XInclude and XPath support are both very importmant in SCXML
>>> application.  So i want to confirm Commons SCXML support these
>>> features or not. If yes, how can we use them ? If not, may be we can
>>> do something to improve Commons SCXML. Thank You.
>>>
>> <snap/>
>>
>> You may use an XPathEvaluator like the one below and pass in the
>> functions you want supported (see 2nd constructor which takes a map,
>> for how arbitrary XPath functions support may be added):
>>
>> http://svn.apache.org/repos/asf/commons/proper/scxml/branches/J6/src/mai=
n/java/org/apache/commons/scxml/env/xpath/XPathEvaluator.java
>>
>> -Rahul
>>
>>
>>> --
>>> ---------------------------------
>>> Best Regards
>>> Gavin Lei (=C0=D7=D2=F8)
>>> Email: gavingui2011@gmail.com
>>>
>>
> --
> ---------------------------------
> Best Regards
> Gavin Lei (=C0=D7=D2=F8)
> Email: gavingui2011@gmail.com
>

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