[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    Re: [SCXML] Using SCXML + Daffodil in order to fully specify (industrial) protocols?
From:       Christofer Dutz <christofer.dutz () c-ware ! de>
Date:       2019-01-31 16:21:42
Message-ID: DBBPR05MB650625AA04528141285D3B35A2910 () DBBPR05MB6506 ! eurprd05 ! prod ! outlook ! com
[Download RAW message or body]


Hi all,

So I just finished a first operational scxml based state machine, that conn=
ects to a remote host and exchanges messages described by dfdl by serializi=
ng xml templates which I define inside my CustomAction elements of my scxml=
 document.

And the coolest thing is, that the remote Siemens PLC answered correctly :-=
)

Still needs a lot of work. Especially we would need at least working snapsh=
ots of commons-scxml (the ones on repo.apachr.org are hugely out of sync) .=
.. You need help with that? Had to tweak some minor things to build locally=
, but should be easy to fix.

Would be cool, if someone could review what I'm doing (haven't committed it=
 yet as it would break the build due to outdated snapshots) ... Don't wanna=
 walk into the wrong direction and if we work together, I bet this could be=
 for the benefit of Plc4x and commons-scxml :-)

Chris


Outlook f=FCr Android<https://aka.ms/ghei36> herunterladen

________________________________
From: Woonsan Ko <woonsan@apache.org>
Sent: Tuesday, January 29, 2019 4:49:16 PM
To: Commons Developers List
Subject: Re: [SCXML] Using SCXML + Daffodil in order to fully specify (indu=
strial) protocols?

Hi Chris,

On Tue, Jan 29, 2019 at 8:26 AM Christofer Dutz
<christofer.dutz@c-ware.de> wrote:
>
> Hi all,
>
> I am a member of the Apache PLC4X podling. There we are implementing driv=
ers for communicating with industrial hardware.
> Now we had started with manually implemented Java drivers, but it has alw=
ays been our goal to ship drivers in multiple languages.
>
> As we are currently starting work on the C++ versions, it was time to wor=
k on some way to universally define these protocols
> and have the drivers in each supported language generated.
>
> As a first step I wrote DFDL schemas and tests using Apache Daffodil and =
this worked perfectly for defining the format of the
> messages being exchanged. Now I still had to model the protocol itself: W=
hich message with what content is sent at which time?
> How does the information provided by users get in  requests and out of re=
sponses?
> So I was looking for some way to specify a State machine in XML =85 I stu=
mbled over SCXML
> And can you imagine my surprise when I noticed Apache has something for t=
his in its toolbox?
>
> Right now I=92m working on writing such a SCXML schema mixing together SC=
XML + DFDL + Custom extensions to achieve the
> goal of fully specifying these protocols. So far it=92s looking good, but=
 I would like to ask, if someone here (ideally with SCXML experience)
> would be interested in joining us and working on this.

Sounds cool! I'm not familiar with DFDL, but I'd like to help with
some of my experiences with SCXML and our current Commons SCXML
implementations.

>
> I know that the activity on the SCXML project seems to have been =85 well=
 minimal. But still I think it=92s a good option.
>
> Any opinions, suggestions, things I should consider?

One issue with the SCXML subproject is that it has been refactored a
lot since v2, but it has never been released for years. So, people
seem to feel hard to try it.
Another is that Ate and I have used it mostly for a specific use
case--document publication workflow in CMS--with M1 [1]; it kind of
lacks of diversity. In that sense, new faces from diverse backgrounds
will be more than welcome and more beneficial to the community.

Perhaps you can test some PoC or its scenarios in conceptual level
with M1 tag to see if everything is okay.

Another thing is that we should consider releasing it often (again
like 0.x's). Perhaps just because we bumped the version to 2.0.0
thanks to the expected whole refactoring, we might just have been
hesitant to cut a release of v2.x.x while we're not ready yet to
fulfill all the requirements of SCXML specification.

Regards,

Woonsan

[1] http://commons.apache.org/proper/commons-scxml/roadmap.html

>
> Chris

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



[prev in list] [next in list] [prev in thread] [next in thread]