Ah. All my non-synchronizing components are also stateless.
You could do something like this:
public void appendToResponse (WOResponse aResponse, WOContext
aContext) {
super.appendToResponse(aResponse, aContext);
reset();
}
public void takeValuesFromRequest(WORequest aRequest, WOContext
aContext) {
super.takeValuesFromRequest(aRequest, aContext);
reset();
}
public WOActionResults invokeAction(WORequest aRequest,
WOContext aContext) {
WOActionResults results = super.invokeAction(aRequest,
aContext);
reset();
return results;
}
On Sep 14, 2006, at 6:47 PM, Miguel Arroz wrote:
I tested reset, it's not called. By the documentation it's only
called on stateless components. This is not a stateless component,
it's just a normal (statefull) component with auto-synchronization
turned off! :)
Yours
Miguel Arroz
On 2006/09/15, at 02:36, Gary Teter wrote:
If you do it this way, you'll also need:
public void reset() {
user = null;
super.reset();
}
On Sep 14, 2006, at 6:12 PM, Chuck Hill wrote:
public User user() {
if (user == null) user = (User)valueForBinding
(USER_BINDING_NAME);
return user;
}
Not one one, but one important line. Is that close enough? :-)
--
WireHose: Smart metadata and personalization for WebObjects.
http://www.wirehose.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
