Re: Reusable WORollover...trying to make stateless...nonsynchronizing...
Re: Reusable WORollover...trying to make stateless...nonsynchronizing...
- Subject: Re: Reusable WORollover...trying to make stateless...nonsynchronizing...
- From: Nathan Walker <email@hidden>
- Date: Wed, 22 Jun 2005 14:50:47 -0400
Is the public void reset() absolutely necessary? Does this need to go
in all stateless/nonsynchronizing components?
I love everything in your Practical WebObjects book, especially the
in depth coverage of the Object Graph, Managing Data freshness, and
in depth look at the life of components. That book is a staple for
the WebObjects world I think.
I am DYING to see some video seminars on WebObjects, I wish there
were DVD's of sessions out there. Do you guys have any? I would buy
everything available. I went to a session in Atlanta once and found
it INCREDIBLY helpful and inspiring as to what is possible with
WebObjects. I would make my own if I was a good enough expert but I'm
just not quite at that level yet. I wouldn't want to further confuse
interested on-lookers if my methods were not sound and tested enough.
Thanks,
Nathan
On Jun 22, 2005, at 12:46 PM, Chuck Hill wrote:
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:
40global-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:
This email sent to email@hidden