Hi,
the workflow I've set up contains a user component, which is mapped to a variable of type document. The variable gets populated with an e-mail attachment of type PDF, which the user sends to the workflow server. The attachment is extracted using the EmailReceiver QPAC. The form template of the user component is set to the XDP file, which corresponds to the PDF being sent.
The EmailReceiver QPAC works fine. No exceptions are thrown, no errors logged. But the user component repeatedly throws the same exception about a gazillion times:
> 2006-04-05 11:10:02,431 INFO [STDOUT] org.xml.sax.SAXParseException: Content is not allowed in prolog.
>
2006-04-05 11:10:02,431 INFO [STDOUT] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>
2006-04-05 11:10:02,431 INFO [STDOUT] at javax.xml.parsers.SAXParser.parse(Unknown Source)
>
2006-04-05 11:10:02,431 INFO [STDOUT] at javax.xml.parsers.SAXParser.parse(Unknown Source)
>
2006-04-05 11:10:02,431 INFO [STDOUT] at com.adobe.fm.indexing.FormDataFieldExtractor.extractFields(FormDataFieldExtractor.java:160)
>
[...]
In the JBoss server log file the last line of this error reads:
> 2006-04-05 16:49:40,422 WARN [org.jboss.ejb.plugins.jms.DLQHandler] Message resent too many times; sending it to DLQ; message id=ID:xxxxxxxxxxxxxxxxxx
Interestingly though, the workflow works.
I learned that the 'Content is not allowed in prolog' error is sometimes related to whitespaces in the XML header. But neither in the PDF nor the XDP template are whitespaces in the header section. I also tried including and excluding an XML schema in the form. It didn't change the SAX Exception.
Does anyone have an idea, what peculiarities to take into account regarding the mapping of documents in the user component? What does the SAX Exception actually means?
Regards,
Steve