Comments on: ADF: making an operation (binding) available in every Page Definition (Binding Container)

By: AdamA

AdamA — Fri, 04 Apr 2008 20:17:20 +0000

Hi Lucas. Do you think that this workaround might solve the problem mentioned the comments section of your article at http://technology.amis.nl/blog/?p=1709#comment-304824? Namely: The problem of not being able to display data bound components of a “content” page referenced in an adf region tag…I appreciate your help!

By: Lucas Jellema

Lucas Jellema — Sun, 03 Feb 2008 19:42:15 +0000

Sort of. Actually we are working round the fact that a record presented in the screen may have a reference to a record – created by another user – to a record we are not allowed to access. For example: we are looking at Employee SCOTT who is assigned to Department 10 – SALES. However, we are not privileged to see Department 10. The business requirements for our project state that in this case we should have a Dropdownlist that is disabled – we cannot assign SCOTT to another Department as he is currently in a department we are not privileged for. However, the Dropdownlist should show the label SALES for the referenced Department. And to retrieve that label for a user who strictly speaking cannot see SALES at all, we had to punch a hole in our VPD like data authorization mechanism – which we did in a rather elegant way I believe, for which we used this solution by Steve Muench.

regards,

Lucas

By: Jan Vervecken

Jan Vervecken — Sun, 03 Feb 2008 16:40:50 +0000

Thanks for your reply Lucas.
Indeed that sounds like a fairly complicated story. I’m not sure I understand correctly, but are you implementing (part of) your data authorization rules in the view layer which requires you to have this operation binding available?
regards
Jan Vervecken

By: Lucas Jellema

Lucas Jellema — Sun, 03 Feb 2008 14:38:08 +0000

Jan, That is a fairly complicated story involving dropdown items that are displayed as LOVs when they contain more than a specific configurable threshold and that may contain a value that is associated with a (lookup) value that the current user is not allowed to see considering the data authorization rules for which we will display the read-only label. For this, we have a bean that can complement the set of allowable values for the dropdown element with that one value it would normally not contain, by calling a method on the application module that in turn consults a PL/SQL function to return the display label for that particular value. Since potentially every page can contain one or more dropdown elements, we may need to invoke the ApplicationModule's method from every page in the application, hence we need the operation binding in all PageDef files.

Perhaps you should come and see it in order to understand exactly what we are trying to achieve....

Best regards, Lucas

By: Jan Vervecken

Jan Vervecken — Sat, 02 Feb 2008 20:59:48 +0000

Thank you Lucas.
I’m just wondering what the specific use case would be for this, “from every one of our 100+ pages we would like to be able to invoke a specific operation on the ApplicationModules Client Interface”.
regards
Jan Vervecken

By: Rob Brands

Rob Brands — Sat, 02 Feb 2008 19:26:27 +0000

Thats what we hoped for. Good start of the weekend

By: Edwin Biemond

Edwin Biemond — Sat, 02 Feb 2008 11:21:44 +0000

Very nice. In jdev 11g you can add this in the pagedef of the jsf page template.