After reading your explanation Katya, the behavior of
WOSwitchComponent makes perfect sense. What would happen if it
removed the components from subcomponents after the WOComponent name
changed? Well, for one, WOSwitchComponent would probably be unusable
in a WORepetition. So, I don't th
Hi Katya;
The component that is actually switched seems to behave "quasi-
stateless" to me, but the tree of components below the switched one
seems to behave statefully. Maybe the awake() is issued to all of the
past sub-components of the switch in case the switched component
changes in t
Hi again,
The workaround is not what my initial e-mail was about - the reason
for this behaviour is what was bothering my colleague and me. After
spending some time investigating the issue it turned out that all
components that have at some point occupied the WOSwitchComponent are
registe
I'm a bit surprised by the behavior myself, and I'm not sure why it
does that. I would imagine using a stateless component might help
reduce the number of cached components. You can also simply return a
clean page like
public WOActionResults goToPageOne() {
System.o
Hello Katya;
That is interesting. So you mean that previous components which
previously resided in the switch are restored and awoken despite not
being the component named in the switch for the present request-
response cycle?
cheers.
We've stumbled upon an interesting thing when using
Hi list,
We've stumbled upon an interesting thing when using WOSwitchComponent
( WO 5.4.3 ).
The situation is as follows :
1. There is a base component that contains WOSwitchComponent element
and navigation menu.
2. Upon click on any of the navigation items a component action is
performed
On Jul 13, 2009, at 9:44 PM, J Stephanos wrote:
Chuck:
> NSLog.out.appendln(new RuntimeException());
This is a cool idea. :-)
That is one I use often when trying to track down odd behavior.
> If I understand your description, this is normal. One call is
from the invokeAction phase and
Chuck:
> NSLog.out.appendln(new RuntimeException());
This *is* a cool idea. :-)
> If I understand your description, this is normal. One call is from the
invokeAction phase and one from appendToReponse.
*This is exactly the case. * Also, I was calling another method from within
componentName (w
On Jul 13, 2009, at 5:49 PM, J Stephanos wrote:
I am using a WOSwitchComponent to select the relevant component to
be displayed via hyperlinks. componentName is a method that
returns the component name.
On clicking the link for the first time, everything works great.
Any subse
I am using a WOSwitchComponent to select the relevant component to be
displayed via hyperlinks. componentName is a method that returns the
component name.
*
*
On clicking the link for the first time, everything works great. Any
subsequent clicks shows some odd behaviour - the componentName
10 matches
Mail list logo
