m[2] = new Integer(30);
m[3] = new Integer(45);
NSArray minuteList = new NSArray(m);
return minuteList;
}
}
Tim
On May 15, 2008, at 2:02 PM, Chuck Hill wrote:
On May 15, 2008, at 1:22 PM, T Worman wrote:
All:
I
custom class and it's toString() will just print
the time value as "hours:minutes." At this point I don't have
anything else in the wod or the html since I stripped it out for
troubleshooting. The "reason" for the error message is:
<edu.ucla.gseis.ets.co
e
anything else in the wod or the html since I stripped it out for
troubleshooting. The "reason" for the error message is:
<edu.ucla.gseis.ets.components.NonExemptTimeEditComponent
subcomponents: null >>: A stateless component can not have a
stateful child (name: edu.ucla.gseis.ets
this point I don't have anything
else in the wod or the html since I stripped it out for
troubleshooting. The "reason" for the error message is:
<edu.ucla.gseis.ets.components.NonExemptTimeEditComponent
subcomponents: null >>: A stateless component can not have a
time value as "hours:minutes." At this point I don't have anything
else in the wod or the html since I stripped it out for
troubleshooting. The "reason" for the error message is:
<edu.ucla.gseis.ets.components.NonExemptTimeEditComponent
subcomponents: nu
t this point I don't have anything
else in the wod or the html since I stripped it out for
troubleshooting. The "reason" for the error message is:
<edu.ucla.gseis.ets.components.NonExemptTimeEditComponent
subcomponents: null >>: A st
On May 15, 2008, at 1:22 PM, T Worman wrote:
All:
I'm having a problem using a stateless component and I'm not sure
why. My app has a stateless component that has WOPopUpButtons for
selecting hours and minutes for entering time-based data. I'm trying
to abstract these WOPo
All:
I'm having a problem using a stateless component and I'm not sure why.
My app has a stateless component that has WOPopUpButtons for selecting
hours and minutes for entering time-based data. I'm trying to abstract
these WOPopUpButtons to a new stateless component
API docs: "For extra efficiency, you can create
stateless components: components that can be shared between
sessions. Stateless components aren't replicated each time they're
needed; rather, a single shared instance is referenced each time the
component is used."
But
, Apr 2, 2008 at 11:37 PM, Archibald Singleton <
> > > [EMAIL PROTECTED]> wrote:
> > > Hello,
> > >
> > > >From the WO API docs: "For extra efficiency, you can create stateless
> > > components: components that can be shared between sessions. Sta
or extra efficiency, you can create
stateless components: components that can be shared between
sessions. Stateless components aren't replicated each time
they're needed; rather, a single shared instance is referenced
each time the component is used."
But logging calls to
ts that can be shared between
sessions. Stateless components aren't replicated each time they're
needed; rather, a single shared instance is referenced each time
the component is used."
But logging calls to my stateless component constructor (subclass
of ERXStatelessComponent)
sessions. Stateless components aren't replicated each time
they're needed; rather, a single shared instance is referenced
each time the component is used."
But logging calls to my stateless component constructor (subclass
of ERXStatelessComponent), I see that's it's b
is referenced each time
the component is used."
But logging calls to my stateless component constructor (subclass
of ERXStatelessComponent), I see that's it's being called for
every request and that new instances are created for each request.
Maybe worth noting is the fa
create
stateless components: components that can be shared between
sessions. Stateless components aren't replicated each time they're
needed; rather, a single shared instance is referenced each time
the component is used."
But logging calls to my stateless co
On 03 Apr 2008, at 14:39, Chuck Hill wrote:
On Apr 3, 2008, at 10:28 AM, Tonny Staunsbrink wrote:
The top level component is allways created, subcomponents are
reused, not sure why
Because they have to go in the page cache as unique instances
recording page state. Stateless and page
they're
needed; rather, a single shared instance is referenced each time the
component is used."
But logging calls to my stateless component constructor (subclass of
ERXStatelessComponent), I see that's it's being called for every
request and that new instances are creat
ts: components that can be shared between sessions. Stateless
> components aren't replicated each time they're needed; rather, a single
> shared instance is referenced each time the component is used."
>
> But logging calls to my stateless component constructor (subcl
a single shared instance is referenced each time the
component is used."
But logging calls to my stateless component constructor (subclass of
ERXStatelessComponent), I see that's it's being called for every
request and that new instances are created for each request.
Maybe wor
is used."
But logging calls to my stateless component constructor (subclass of
ERXStatelessComponent), I see that's it's being called for every
request and that new instances are created for each request.
Maybe worth noting is the fact that the component is instantiated by a
20 matches
Mail list logo
