Apple

Thanks Johann. I’m not caching anything but it is a subclass of ERDCustomEditComponent so perhaps so state information is being cached inappropriately only in production. I might have to try debugging in a production environment.

Mark

On 7 Nov 2014, at 10:20, Johann Werner <email@hidden> wrote:

Hi Mark,

do you cache the binding values within your component? When using stateless components you need to clean any local variables yourself within the reset method.

jw

Am 07.11.2014 um 10:33 schrieb Mark Wardle <email@hidden>:

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

References:
	>Component caching? (From: Mark Wardle <email@hidden>)
	>Re: Component caching? (From: Johann Werner <email@hidden>)
	>Re: Component caching? (From: Mark Wardle <email@hidden>)