pe:documentViewer in dialog is caching?

[rider]

Hi all,

I´m currently try to create a PDF (which already working).
I´m creating the PDF from a URL.
So if I change something in the content from this URL and open the p:dialog again, also my PDF should be refreshed....

But it seems the content in the dialog is not updated. The pdf generation function is called, but it seems it´s still caching on client side?
Did I forgot something?

Function to call the PDF creation:

Code: Select all

<h:form id="myForm">
						<p:commandButton value="Show Preview" 
									update=":previewDialogForm" ajax="true" resetValues="true"
									actionListener="#{generatePdfDocumentDesignerController.createPDF()}"
									oncomplete="PF('previewWidgetDlg').show();">
									<p:resetInput target=":previewDialogForm" />
								</p:commandButton>
</h:form>

Dialog:

Code: Select all

	<h:form id="previewDialogForm">
		<p:dialog id="previewDialog" widgetVar="previewWidgetDlg"
			appendTo="@(body)" header="Vorschau" showHeader="true"
			maximizable="true" contentWidth="80%" contentHeight="80%"
			height="85vh" width="85vw" minimizable="false" dynamic="true"
			modal="true" resizable="false" closable="true" closeOnEscape="true">


			<pe:documentViewer id="generatedPdf"
				style="height: 83vh; width: 82vw" zoom="100" cache="false"
				value="#{generatePdfDocumentDesignerController.pdfFile}" />


			<f:facet name="footer">
				<div class="EmptyBox2"></div>
				<div class="Fright">
					<p:commandButton id="cancelBtn" value="Abbrechen"
						styleClass="RaisedButton" style="margin-right: 15px;"
						icon="fa fa-window-close" onclick="PF('previewWidgetDlg').hide()"
						type="button" />


				</div>
				<div class="EmptyBox2"></div>
			</f:facet>
		</p:dialog>
	</h:form>

Bean:

Code: Select all

@Named
@ApplicationScoped
public class GeneratePdfDocumentDesignerController implements Serializable {

...

	public void createPDF() {

		FacesContext facesContext = FacesContext.getCurrentInstance();

		try {

			String url = createUrl();
			pdfFile = null;

			PipedOutputStream os = new PipedOutputStream();
			PipedInputStream is = new PipedInputStream(os);

			managedExecutorService.submit(() -> {

				try {
					PdfRendererBuilder builder = new PdfRendererBuilder();
					XRLog.setLevel(XRLog.CSS_PARSE, Level.SEVERE);

					builder.withUri(new URL(url).toString());
					builder.toStream(os);

					builder.run();
					os.close();

				} catch (IOException e) {
					LOGGER.error(ExceptionUtils.getFullStackTrace(e));
				}
			});
			
			pdfFile = new DefaultStreamedContent(is, "application/pdf");

		}

		catch (Exception e) {
			ErrorMessage.showErrorMessage();
		}

		facesContext.responseComplete();

		LOGGER.info("END createPDF");
	}

Any ideas?

[Melloware]

Have you debugged that generatePdfDocumentDesignerController.createPDF() is actually generating a new PDF?

Can you create a small reproducible example using https://github.com/primefaces/primefaces-test so I can debug?

[rider]

Yes, it´s called the function if I press a second one the button to open the dialog...

Is there something missing in my p:commandButton to remove the content from the current p:dialog which was open before?
It seems for me stil it´s caching, because also the second time when I open the dialog is open much more quicker then the first time...

[Melloware]

No your update="" is telling the dialog to replace itself correctly. The only other thing you can try is to set your dialog to dynamic="true"

[rider]

I have already dynamic="true" in my p:dialog (please see above code). Or what do you mean?

[Melloware]

Ahh i didn't notice that. Dynamic="True" should do an AJAX call to get the contents of the dialog and your update="" should update.

Once again if you want me to debug it please provide a small reproducer using: https://github.com/primefaces/primefaces-test

[rider]

OMG!
I´ve debugged now also and it was the case also for outputText etc.

I had in my bean this code:

FacesContext facesContext = FacesContext.getCurrentInstance();
facesContext.responseComplete();

I removed that and it was working.
Sorry for this confusion.

[Melloware]

no problem. gad you got it solved.