Component caching?
Component caching?
- Subject: Component caching?
- From: Mark Wardle <email@hidden>
- Date: Fri, 07 Nov 2014 09:33:17 +0000
Hi. I’m generating a PDF report : WOComponent page = ERXApplication.application().pageWithName(componentName(), privateContext()); page.takeValueForKey(obj, "object"); page.takeValueForKey(report, "report"); WOResponse response = page.generateResponse(); report.setInterimHtml(response.contentString());
This looks up a named WOComponent and generates the response, storing the HTML and allowing users to fine-tune the HTML in a web-based HTML editor. This has worked perfectly previously.
Now I have added a custom “display boolean” component which is used within the report WOComponent. This is a stateless component but it displays the same value again and again when in production. In development, the component works properly.
It is like the content of the component is being cached inappropriately. I thought component caching was related to caching the contents of the WOD file, not the bindings.
Does anyone have any thoughts? Debugging this on a production machine quite tricky so if anyone can thing of something obvious, I’ll try that first!
Thanks,
Mark |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden