Jasper,

We need to fix this at some point.

As a not-so-nice workaround, you could have your scheduler perform an HTTP request, and implement the PDF generation from that service.

-Erik

On Mon, May 2, 2011 at 6:14 AM, Jasper Linthorst <[hidden email]> wrote:

Hi All,

I've noticed that when I use the 'xhtml-to-pdf' processor from a pipeline that's run through the scheduler it fails at the point where it tries to resolve an external resource (like my css).

It generates a NullPointerException at 

org.orbeon.oxf.processor.pdf.XHTMLToPDFProcessor$1.resolveURI(XHTMLToPDFProcessor.java:77)

Whenever I run the pipeline through an http request (using the pfc) all works fine.

The problem probably has to do with the lack of a ExternalContext/Request object when running a pipeline through the scheduler. Could anyone let me know if there's a workaround to this?

Thanks in advance!

Jasper

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws