| AW: [jwt-dev] RE: 0.6 to 0.7 Converter ignores Data Parameters |
|
Hi Ravi, I tried adding
support for data parameters. At the first look the
resulting file seems to be correct. Regards, Chris Von:
jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag
von RAVI K. THAPLIYAL Hi Florian, Hi Chris, Along with switching
to JWT 0.7, I’m providing Events functionality in my next app release. The ATL
converter is also having troubles with migrating Event nodes from 0.6 to 0.7 .
Please find the ATL exception stack trace attached. With the ATL failing with
Event nodes too I wouldn’t be able to develop and test the events functionality
being added to the editor properly. My app fires ATL
every time someone checks out a workflow from database (stored in our internal
format) to work on it. Our DB2JWT component create s a 0.6 file only and simply
opens it up in editor from where your ATL takes over. Now, if the ATL fails or
misses out on something the users are left unable to work on or deploy the
workflows again. So, I sincerely
request you guys to get back as soon as possible. Please, let me know
if I can assist in providing any more details required. Regards, Ravi From: jwt-dev-bounces@xxxxxxxxxxx
[mailto:jwt-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Saad Hi Ravi, it’s great that you
were able to adapt your application to 0.7. For your request, unfortunately I’m
not an ATL expert at all but I’ll look into this issue this week and fix this
problem. Regards, Chris Von:
jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag
von RAVI K. THAPLIYAL Hi Chris, Could you please help
provide a fix for this defect? I’m nearing my next app release and since I’m
not creating 0.7 files directly it’s absolutely essential that it gets fixed
for 0.6 workflow compatibility. I’ve tried figuring
out the way subpackages and elements tags are being transformed but haven’t
been able to replicate the syntax correctly. Regards, Ravi From: RAVI K. THAPLIYAL Hi Florian, Hi Chris, Any updates on this
bug? For my next release
I’m sticking with using the ATL converter to automatically update the 0.6
workflow that my customized workflow wizard generates. I’ve suppressed all the
prompts. I’m generating the layout data for both the views and with some more
patches the application nearly feels like 0.6 again. J This is the only
defect that remains between releasing my app on JWT 0.7 now. I’ve tried to
understand the ATL some more but it gets a bit arcane while handling children
elements with recursion. I would greatly
appreciate any help in providing a bug fix for this. Regards, Ravi From: RAVI K. THAPLIYAL Hi Florian, I’ve logged a new bug
for this here.
Workflow files have been attached for reference. Regards, Ravi From: Florian Lautenbacher
[mailto:florian.lautenbacher@xxxxxxxxxxxxxxxxxxxxxxxxxx] Hi Ravi, yes, this is a bug.
It seems we have forgotten the conversion of the parameters from 0.6 to 0.7.
Could you please open a new bug for this and attach the sample files and
describe the experienced behavior? We will then have a look at that. Thanks and best
regards, Florian Von: RAVI K. THAPLIYAL
[mailto:RAVI.THAPLIYAL@xxxxxxxxxx] Hi Chris, Hi Florian, The ATL converter that’s used to convert
0.6 workflow files to 0.7 doesn’t convert Data elements correctly. The <elements> tag is being copied as
is ignoring all <parameters> child elements. I’m sending attached two
.workflow files one of version 0.6 that has data parameters and the other one
after it has been converted to 0.7 with all its data parameters lost. There’s a generic Bug 296235
already logged against the converter. I guess we can either reopen it or log a
new one once you guys confirm. Regards, Ravi
|
Attachment:
JWT60toJWT70.asm
Description: Binary data
Attachment:
JWT60toJWT70.atl
Description: Binary data