ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I'd like to render PDFs using the Seam-PDF feature. I borrowed "whyseam.xhtml" from the seam-ice-itext project to use as a test case. Using it doesn't seem to matter what link technology I use (s:link, ice:outputLink), I get this:
Caused by: java.lang.NullPointerException
at com.icesoft.faces.context.DOMResponseWriter.enhanceAndFixDocument(DOMResponseWriter.java:315)
at com.icesoft.faces.context.DOMResponseWriter.endDocument(DOMResponseWriter.java:186)
at com.icesoft.faces.context.DOMResponseWriter.cloneWithWriter(DOMResponseWriter.java:251)
at org.jboss.seam.pdf.ui.ITextComponent.extractText(ITextComponent.java:265)

Before I bomb everyone with a ton of detail Has anyone ever gotten this, or a similar error? As far as I know the packaging is done correctly. What should I look for? Thanks.

Stack == Seam 2.2.0.CR1 / ICEfaces 1.8.1 / JBoss 5.1.0.GA

when you are integrating with seam-pdf, you pretty much have to use jsf delegation. Have you configured this correctly? Also, did this work for you on jboss-4.2.3.GA? (I hadn't tested it on jboss-5.1.0.GA although it should work fine there as well).

Some emendations.

1. I finally noticed that in seam-ice-itext example, references to '.xhtml' were <ui:remove>'d and replaced with references to ".jsf', which of course causes the Sun servlet to handle the instead of icefaces. Once I did the same thing in the non-workflow portions of my app, it worked perfectly i.e. use the '.jsf' extension as opposed to '.xhtml'.

2 . The same approach doesn't work inside Seam pageflows.
When either the '.jsf' or the '.xhtml' extensions are used, the exception is sustained.

When '.jsf' is used in combination with <redirect/> in the <page/> directive, it gets even more weird. Firefox says:
<quote>
The page isn't redirecting properly
----
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
</quote>

Nice.

Can you share what the recommended approach is in this case?

Thanks very much. This forum has been a great help.

Since it might depend on how you use pageflows, I would suggest creating a simple sample application which illustrates the problem, creating a jira and then attaching the sample to the jira.

Will do. Thanks. When done, I'll update this with the JIRA number.

ICE-4813