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
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,
If you use inline bindings with ONGL, the class WOHelperFunctionTagRegistry
registers classes mapped to tag
WOHelperFunctionTagRegistry.registerTagShortcut("ERXElse",
"else");
WOHelperFunctionTagRegistry.registerTagShortcut("ERXWOConditional", "if");
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 all,
there is a problem left with the wonder build on the new jenkins host. The
documentation doesn't get built correctly. There is an output, but it only
contains the "com" and "er" subdirectories, without all the html index files
and stuff. Is anyone familiar with that kind of problem? I
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
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() {
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,
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
Great thing, looks very useful.
> On 11.03.2017, at 23:41, Ricardo Parada wrote:
>
> Hi all,
>
> Over the years, I’ve worked on an class for doing ad hoc queries. This class
> has gotten better and better. At first, the API of this class and some
> implementation details
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
11 matches
Mail list logo