nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwwft_compile.ipl giving XML parsing error

Adam Stoller

Environment[indent]TS 7.2.0 on W2K3[/indent]Issue[indent]

\Programs\Interwoven\TeamSite\bin>iwwft_compile.ipl < d:\Programs\Interwoven\TeamSite\tmp\xx.xml
[color=red]ERROR: miscellaneous error occurred
Error parsing input XML: XML parse error :
no element found at line 1, column 0, byte -1 at \Programs\Interwoven\TeamSite\iw-perl\vendor\lib/XML/Parser.pm line 187

\Programs\Interwoven\TeamSite\bin>iwperl iwwft_compile.ipl < d:\Programs\Interwoven\TeamSite\tmp\xx.xml
<?xml version="1.0" standalone="no"?>
<!DOCTYPE workflow SYSTEM "iwwf.dtd">

<workflow name="Categorization Process" owner="domain\userid" creator="domain\userid" description="...">
<variables>
<variable key="Deployment_Env" value="UAT3"/>
</variables>

<externaltask name="Attach Dependencies" owner="domain\userid" description="Attach all file dependencies" start="t">
<areavpath v="/default/main/.../WORKAREA/Publishers"/>
<successors>
<successorset description="Done">
<succ v="End"/>
</successorset>
<successorset description="TIMEOUT">
<succ v="End"/>
</successorset>
</successors>
<command v="http://uslaxcmsdev01/iw-cc/urlexternaltask"/>
<timeout v="+000050">
<succ v="End"/>
</timeout>
<files>
<file path="/templatedata/category/datatype/data/dcrname" comment="Submitted by domain\userid"/>
</files>
<variables>
<variable key="ClassName" value="com.xx.wf.GetDependencies"/>
</variables>
</externaltask>

<endtask name="End">
<activation>
<pred v="Attach Dependencies"/>
</activation>
</endtask>
</workflow>
\Programs\Interwoven\TeamSite\bin>assoc .ipl
.ipl=iwperl

\Programs\Interwoven\TeamSite\bin>ftype iwperl
iwperl=D:\Programs\Interwoven\TeamSite\iw-perl\bin\iwperl.exe %1 %*[/color]

[/indent]If it weren't for the fact that running the command with iwperl seems to work when running it "natively" doesn't I'd assume the problem was in either the input file or WFT - but apparently the WFT is fine and so is the input file (since I'm passing in the file path and several other pieces of information via the input file).

Any ideas on what I might be missing here?

Find more posts tagged with

Comments

nipper

A bad shebang line in wft_compile.ipl ?

nipper

I would also be interested in adding a line to the wft_compile to see if you can print out the XML and see what the difference it. It looks like the redirection is handling things differently

Andy

Adam Stoller

A bad shebang line in wft_compile.ipl ?

Hmm - good idea, but that doesn't seem to be the case.

#!D:\Programs\Interwoven\TeamSite/iw-perl/bin/iwperl

(and yes, I tried making all the slashes go in the same direction (both ways) and it didn't have any effect on the situation)

nipper

Like my other post says, I expect the ...ipl < blah.xml is not behaving the way one would expect. Can you test that out ?

Adam Stoller

I would also be interested in adding a line to the wft_compile to see if you can print out the XML and see what the difference it. It looks like the redirection is handling things differently

Andy

The WFT is outputting the XML - but only when I run it explicitly with iwperl.

Okay - I added a bit of debugging to iwwft_compile.ipl and apparently the code for reading the input file:

...
sub parse_stdin
{
    my $input;
    my $input_ok = 1;

    my $input_xml;

    $input_xml = do { local $/; <STDIN> };
    ...
}

only actually retrieves the input on STDIN when you preface the command with "iwperl" - and that's why it's then failing (lower in the same subroutine) when it tries to parse the contents of $input_xml.

So - I guess I need to change the code that was running this script to preface it with iwperl -- or modify the iwwft_compile.ipl code to take an additional parameter (input file) and have it open and read it itself instead of looking for the input on STDIN.

While the latter would probably be a good improvement to the script, it's obviously less supported (without filing a feature request and waiting for it to get implemented) - so I'll try changing the script that's calling iwwft_compile.ipl to explicitly use iwperl.... (sigh)
(I really prefer Unix)

Adam Stoller

Heh - the code already was using iwperl explicitly - apparently the problem was due to a DCR not getting created before the workflow was kicked off...

nipper

oops.

Glad you got it working.