Comments on: ADF 11g – implementing conditionally required input fields – by playing client side hide and seek

By: Roopam

Roopam — Thu, 13 Oct 2011 11:34:06 +0000

Hi Lucas,
I need to know how can I call different css classes for a page depending up differnt browsers.Like if i want to implement different set of css classes on a page for ie9.And i am using more of ADF tags in my web page.

By: john

john — Wed, 05 Oct 2011 21:55:26 +0000

hi lucas i want to do something like u did but i ant to do it with the buttons, i have a submit button and i have another one that cleans the fields but if i setRequired property to true in the fields the button that cleans the fields doesnt work and the message with the require fields keeps showing i just want it to show when i press submmit button
ps. thx

By: Johan

Johan — Tue, 13 Sep 2011 10:43:49 +0000

hi lucas, i’ve seen you’re solution. But to me it is not practical. I have pages with hundreds of required fields, are there other solutions to this problem?

By: Amar

Amar — Sat, 29 Jan 2011 09:20:11 +0000

I’ve a requirement wherein I need to refer to different details table based on a id ie the data for the details table can come either from Table A or Table B.Is there any best way to achieve this in ADF?

By: Joe

Joe — Mon, 15 Feb 2010 11:09:07 +0000

Lucas, do you think there is a way of achieving this purely with the ‘Validation Rules’ feature of ADF BC? If this could be implemented in the model I think it would save a lot of time, plus it would be portable to any page of you without the need for more backing beans.
Given the ‘Conditional Execution’ feature I’m sure there is a way to work this out

By: Lucas Jellema

Lucas Jellema — Fri, 18 Dec 2009 06:01:37 +0000

Hi Sten,

Duncan’s First Law however is one that is not attainable in real life. As a guiding principle to limit the volume of (unstructured, hard to maintain, difficult to upgrade, challenging to make multi-browser proof) JS code I subscribe to it. At the same time, to achieve scalable, responsive web applications, we need to not overdo on the PPR and the number of times we engage the server to step in. Latencies of 0.5 secs or more (we are talking internet application here with unpredictable network speeds) are simply too long for some PPR. So we try to limit the JS – but there are some very good use cases and validation is one of them.

By the way, my colleague on the project (Robert) has created an alternative solution that is even more concise. I will write about it in more detail shortly.

Lucas

By: Sten Vesterli

Sten Vesterli — Thu, 17 Dec 2009 19:37:38 +0000

Very clever!
I must point out, though, that it violates Duncan’s First Law: “Thou Shalt Not Write JavaScript”