workflow parsing error in Java

Hi,

I am trying to parse a workflow specified in an external file in Java, and got parsing exception.

the error message is:
org.dom4j.DocumentException: Error on line 41 of document file:///U:/work/workspace/sws/etc/private/conf/iwwf.dtd : A ')' is required in the declaration of element type "submittask". Nested exception: A ')' is required in the declaration of element type "submittask".

The java code looks like this:
SAXReader reader = new SAXReader(false);
logger.debug("is valid: " + reader.isValidating());
reader.setIncludeExternalDTDDeclarations(false);
reader.setIncludeInternalDTDDeclarations(false);
doc = reader.read(file); // the exception is on this line

The workflow is a simple "hello world" which has been tested in Teamsite.
it is in the attachment.

It seems that the SAXReader could not parse the iwwf.dtd which is in the workflow xml file. I tried to turn off the xml parser invalidation to false, but still no use.

I am using TeamSite 6.7.1 SP1 and LiveSite 3.0.2, the DTD and libraries that the java codes uses are from the TeamSite/LiveSite runtime environment.

Also attached are the dtd file and exception.

Any suggestion will be greatly appreicated.

Regards

Martin

Find more posts tagged with

Comments

Adam Stoller

Create a copy of the DTD and edit it - try changing:

...
<!ELEMENT submittask (description?, areavpath, successorset|(success,failure?),
                      timeout?, files?, activation?, inactivate?, resets?,
                      eastartop*, eafinishop*, wfvarstartop*, wfvarfinishop*,
                      variables?)>
...
<!ELEMENT updatetask (description?, areavpath, successorset|(success,failure?),
                      srcareavpath, timeout?, files?, activation?, inactivate?, resets?,
                      eastartop*, eafinishop*, wfvarstartop*, wfvarfinishop*,
                      variables?)>
...

to:

...
<!ELEMENT submittask (description?, areavpath, (successorset|success,failure?),
                      timeout?, files?, activation?, inactivate?, resets?,
                      eastartop*, eafinishop*, wfvarstartop*, wfvarfinishop*,
                      variables?)>
...
<!ELEMENT updatetask (description?, areavpath, (successorset|success,failure?),
                      srcareavpath, timeout?, files?, activation?, inactivate?, resets?,
                      eastartop*, eafinishop*, wfvarstartop*, wfvarfinishop*,
                      variables?)>
...

or:

...
<!ELEMENT submittask (description?, areavpath, (successorset|(success,failure?)),
                      timeout?, files?, activation?, inactivate?, resets?,
                      eastartop*, eafinishop*, wfvarstartop*, wfvarfinishop*,
                      variables?)>
...
<!ELEMENT updatetask (description?, areavpath, (successorset|(success,failure?)),
                      srcareavpath, timeout?, files?, activation?, inactivate?, resets?,
                      eastartop*, eafinishop*, wfvarstartop*, wfvarfinishop*,
                      variables?)>
...

and see if that helps any

martinxue

Hi,

Thanks very much, I tried the second approach and it works perfectly, i.e. (successorset|(success,failure?)).

Just curious, I wonder how this DTD works in Interwoven? and is this a bug in the dtd definition?

Thanks

Regards

Martin

Adam Stoller

Hi,

Thanks very much, I tried the second approach and it works perfectly, i.e. (successorset|(success,failure?)).

Just curious, I wonder how this DTD works in Interwoven? and is this a bug in the dtd definition?

Thanks

Regards

Martin

It is a bug in the DTD file (feel free to file a case against it with Support)
It doesn't really matter for the application because the actual processing of the WFT is handled internally in code and not validated against the physical DTD file.

martinxue

Hi,

Thanks very much for the information.

Regards

Martin