ev <webobjects-dev@lists.apple.com>
Subject: Re: ERXWOConditional - where does it get installed?
Hi all,
I'm reporting back. I noticed my test app had WOConcurrentRequestHandling set
to false. Once I turned it on the dynamic elements started being shared across
the sessions.
Thanks everyone.
R
huck Hill <ch...@gevityinc.com> wrote:
>>>>
>>>> I’ve run into code that did this in the past. It is very, very much not
>>>> fun to debug. You could stash the values in a ThreadLocal or in the
>>>> context.userInfo(). But don’t ever add
>>> subclass.
>>>
>>> Chuck
>>>
>>> From: <webobjects-dev-bounces+chill=gevityinc@lists.apple.com> on
>>> behalf of Johann Werner <j...@oyosys.com>
>>> Date: Tuesday, March 21, 2017 at 2:19 PM
>>> To:
ner <j...@oyosys.com>
>> Date: Tuesday, March 21, 2017 at 2:19 PM
>> To: Ricardo Parada <rpar...@mac.com>
>> Cc: WebObjectsDev <webobjects-dev@lists.apple.com>
>> Subject: Re: ERXWOConditional - where does it get installed?
>>
>> Hi Ricardo,
&
.com>
> Cc: WebObjectsDev <webobjects-dev@lists.apple.com>
> Subject: Re: ERXWOConditional - where does it get installed?
>
> Hi Ricardo,
>
> you are ignoring one very important aspect of dynamic components: they must
> be thread-safe!
>
> As soon as you
com> on behalf of
Johann Werner <j...@oyosys.com>
Date: Tuesday, March 21, 2017 at 2:19 PM
To: Ricardo Parada <rpar...@mac.com>
Cc: WebObjectsDev <webobjects-dev@lists.apple.com>
Subject: Re: ERXWOConditional - where does it get installed?
Hi Ricardo,
you are ignoring o
Hi Ricardo,
you are ignoring one very important aspect of dynamic components: they must be
thread-safe!
As soon as you are holding local values you will head to a serious mess. In
your „manual“ tests of course you probably won’t ever encounter concurrency
problems as long as you are not doing
Hi all,
I’m just reporting back on my findings on whether saving state between
appendToResponse and a subsequent takeValuesFromRequest in a dynamic component
is bad or not.
I read Chuck’s Practical WebObjects, p. 193 where it talks about Dynamic
Elements. As he pointed out there, dynamic
Hi Ricardo,
>
> On 15 Mar 2017, at 12:23 am, Ricardo Parada wrote:
>
>> Have others experienced a problem where a form is submitted and then during
>> takeValuesFtomTequest a condition that was false when the page was rendered
>> becomes true all of a sudden causing some
Hi Ricardo,
On 15 Mar 2017, at 12:23 am, Ricardo Parada wrote:
> Have others experienced a problem where a form is submitted and then during
> takeValuesFtomTequest a condition that was false when the page was rendered
> becomes true all of a sudden causing some input
Hmm... Thanks for pointing that out. Do you know know how to do that without
storing state? Does wonder do something like that anywhere?
> On Mar 14, 2017, at 10:46 AM, Samuel Pelletier wrote:
>
> Ricardo,
>
> This patch seem dangerous to first. I do not thing it is safe
Ricardo,
This patch seem dangerous to first. I do not thing it is safe to have state in
WODynamicElement. I think they can be reused by the framework.
The correct way is to make sure the condition does not change during RR loop
cycle, same apply to WORepetition list for example.
Regards,
I patched both in a test application from within the Application’s
finishInitialization() method. After this, then MPVWOConditional is used
regardless of whether I use WOConditional in the .wod or in the .html.
@Override
public void finishInitialization() {
Hi Theodore,
If your .wod is using WOConditional then it uses WOConditional. You can test
it quickly by setting a breakpoint in ERXWOConditional’s appendToResponse
method. You’ll see that you won’t hit the breakpoint.
Now, if you change it back to then you’ll hit the breakpoint.
To
Thanks Samuel. I see that now.
Have others experienced a problem where a form is submitted and then during
takeValuesFtomTequest a condition that was false when the page was rendered
becomes true all of a sudden causing some input elements (textfields, pop-up
list, etc.) to participate in
Hi,
If you use inline bindings with ONGL, the class WOHelperFunctionTagRegistry
registers classes mapped to tag
WOHelperFunctionTagRegistry.registerTagShortcut("ERXElse",
"else");
WOHelperFunctionTagRegistry.registerTagShortcut("ERXWOConditional", "if");
Hi,
correct me if I'm wrong, but ERXWOConditional seems no to be a replacement to
WOConditional. Maybe you ask Anjo or Mike, why it is so...
On the other side, you may may patch ERXWOConditional (or WOConditional) in
your own Application.installPatches method.
Am 14.03.2017 um 00:46
17 matches
Mail list logo