Skip to main content

UKOUG Day 4

Image
By
The last day of the conference already...

The day started with a presentation on Datamodelling using JDev. The presenter showed how JDev could replace Designer for modelling. Imho JDev doesn't support logical modelling at all (he misused Java class models to represent a logical model), there is no repository and no relation between a logical and physical model. For just physical modelling JDev is fine, because all 11g database options are included. This modelling option will become available in SQL Dev also....

''After that I went to see my esteemed colleague Peter Lorentzen's talk on How to make your APEX Application Secure. He stated that APEX is secure, but developers make it unsecure. Nice statement Peter! One of his (many) good advices was not to use XE for an APEX (open) production environment as XE is not patched and you will be vulnerable to all kinds of attacks. He also showed a script attack by adding a small "Hello World" script as a value for a database varchar2 column - if you don't check the input and escape the output more dangerous scripts can be executed than just a small pop up box saying Hello. Even with Pete Finnigan on the front row making him kinda nervous, Peter did a good job!

My last session of the day - and the conference - was a two hour Masterclass on ADF by Duncan Mills. He showed us how all the XML files in JDev are created, what the connection was between all these XML files and how to tweak it. For instance how to change (as an example : change the backgroud color) the drag and drop feature in the faces_creator_configuration file. Great session, although he couldn't get through all his 72 (!) slides and tons of examples - have to buy the book (as I didn't win the signed copy).

After that the trip home. Doug Burns made the waiting at the airport more pleasant (and/or the Guinness) , but it still was a long trip. Thanks for the organisation for this great event, I hope to get back next year!

Comments

Post a Comment

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more