|Re: XPDL evolution (Import and Export) [message #27208 is a reply to message #27167]
||Wed, 14 January 2009 14:23
Originally posted by: mickael.istria.openwide.fr|
Indeed, the JWT to XPDL tranformation has never been tested with Shark,
since we targeted mainly Bonita in a first time.
However, XPDL is a standard, that means that if it works for Bonita, it
should work for Shark. But your experiment shows that it is not the case
yet and that the JWT to XPDL transformation requires more work and tests
to be done.
I don't think that current contributors have concretely planned to spend
a lot of time improving the transformation (Most of us are quite busy).
But it is sure that we want this transformation to be as good as
possible, and this includes that generated XPDL must become compliant
with Shark too.
What I suggest you in a first time is to open a bug on Eclipse bugzilla
(https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JWT, this will
require you to create an account if you do not have one yet). Please
attach your workflow files and describe why Shark is not able to run
this process. If you have a JUnit test that checks whether the generated
XPDL is valid or not, it will be very welcome!
From there, we'll be able to discuss about the difficulty to get the
Thanks in advance lot for your contribution.
Patricio.correia a écrit :
> We are using Together Worflow Editor to design our flow rules.
> As WorkFlow engine we use Enhydra Shark.
> We have already a lot of processes designed by the spicified tool.
> When we use JWT to design a simple process and exported to XPDL the process
> doesn't run in Enhydra Shark!!!
> And we are wondering if you are plannig in improving your XPDL related
> tools, in other words your export transformers. And if you have plans to
> transforms XPDL to JWT designer (Import XPDL).
> thanks in advance,
> Patrício Correia
Powered by FUDForum
. Page generated in 0.04276 seconds