• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOSwitchComponent question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOSwitchComponent question


  • Subject: Re: WOSwitchComponent question
  • From: Ramsey Lee Gurley <email@hidden>
  • Date: Thu, 22 Oct 2009 08:06:34 -0400

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.out.println("Main.goToPageOne");
WOComponent result = pageWithName(Main.class.getName());
result.takeValueForKey(ComponentOne.class.getSimpleName(), "componentName");
return result;
}


if the multiple awakes are causing you some problem.

Ramsey

On Oct 22, 2009, at 2:22 AM, Katya Yurukova wrote:

Hi Andrew,

Yes, awake() and sleep() are called for previously loaded components despite that they are no longer present in the current R-R loop.
Here's a simple test case for anyone interested.



<WOSwithcComponentTest.zip>



Cheers,
Katya


On Oct 22, 2009, at 2:14 AM, Andrew Lindesay wrote:

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 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 in which the WOComponentName binding of the WOSwitchComponent is changed to the desired page name and null is returned.


The thing is whenever you navigate to some page awake() is called for all previously visited pages. The question is why are those components awaken and is this behaviour normal and expected?

___ Andrew Lindesay www.lindesay.co.nz

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com


This email sent to email@hidden

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

  • Follow-Ups:
    • Re: WOSwitchComponent question
      • From: Katya Yurukova <email@hidden>
References: 
 >WOSwitchComponent question (From: Katya Yurukova <email@hidden>)
 >Re: WOSwitchComponent question (From: Andrew Lindesay <email@hidden>)
 >Re: WOSwitchComponent question (From: Katya Yurukova <email@hidden>)

  • Prev by Date: Re: Getting attribute-level userInfo at run-time
  • Next by Date: Re: War deploy; maven archetypes problems; web.xml filtering
  • Previous by thread: Re: WOSwitchComponent question
  • Next by thread: Re: WOSwitchComponent question
  • Index(es):
    • Date
    • Thread