• 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: Reusable WORollover...trying to make stateless...nonsynchronizing...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reusable WORollover...trying to make stateless...nonsynchronizing...


  • Subject: Re: Reusable WORollover...trying to make stateless...nonsynchronizing...
  • From: Jean-François Veillette <email@hidden>
  • Date: Wed, 22 Jun 2005 14:38:48 -0400

I don't know if Chuck presented it in his book, and I don't know if my comment will apply to WORollover, but ...

Sometimes for stateless component, you need to keep variables values between the 3 phases, from takeValueFromRequest all the way to appendToResponse.
Since ivars in a stateless component can't handle this case (reset() will be called after each phase), you have to store the information somewhere. Just use context.userInfo dictionary, and put whatever value in there.
As the name imply, the value will only be good for this request only.


- jfv

Le 05-06-22, à 12:46, Chuck Hill a écrit :

There is some fairly OK information on stateless and nonsynchronizing components in Practical WebObjects. In a nutshell you need to use valueForBinding/setValueForBinding to access bound values and implement a public void reset() method that nulls all instance variables. This often requires design changes to your component.

Chuck


On Jun 22, 2005, at 8:14 AM, Nathan Walker wrote:

I have followed Ravi's purple book on creating a reusable WORollover component. It works great. In the next chapter he turns a WOMappedRollover component into a Stateless and nonsynchronizing one with a .plist file.

I am trying to do the same with just the WORollover. I want it to be Stateless and nonsynchronizing. But his concepts for the WOMappedRollover don't exactly fit the simple WORollover. And he doesn't explain how to make WORollover stateless/nonsynchronizing. I can't seem to figure out exactly how to make this stateless and nonsynchronizing. Am I trying to do what's already been done?

Or is it not possible to do this with this type of component. I looked in Project Wonder and didn't see any reusable WORollover like component. Anybody got anything?
This seems like this would be simple but I am surely puzzled. I feel pretty stupid.


Thanks,
Nathan


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


This email sent to email@hidden


--
Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects





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


This email sent to email@hidden


__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 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: 
 >Reusable WORollover...trying to make stateless...nonsynchronizing... (From: Nathan Walker <email@hidden>)
 >Re: Reusable WORollover...trying to make stateless...nonsynchronizing... (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: toHTMLString
  • Next by Date: Re: Further report on WO5.3 and OSXS 10.4
  • Previous by thread: Re: Reusable WORollover...trying to make stateless...nonsynchronizing...
  • Next by thread: Re: Reusable WORollover...trying to make stateless...nonsynchronizing...
  • Index(es):
    • Date
    • Thread