Skip to main content

Part I: Migrating to 12c not so easy - Oracle ADF Jdeveloper 12c Findings


This post is part of 12c Migration project which lists all updates and deprecated stuff in 12c from its predecessors. These are all known findings so far I'll try to update this as I come across new stuff, bugs or fixes:

Java8 👏👏👏👏 - you know what it means 👼

No Groovy Expression to Generate Sequence:

 Common requirement is to use a database sequence to populate key attribute and you can achieve this by adding a groovy expression to the expression tab of attribute in entity object.

(new oracle.jbo.server.SequenceImpl("YOUR_SEQUENCE_NAME", adf.object.getDBTransaction())).getSequenceNumber()

 Trying to use the same logic in 12C will result in following runtime exception:

JBO-25152: Calling the constructor for class oracle.jbo.server.SequenceImpl is not permitted.

Here's a quick fix for this issue:

  1. Open EO in the source view.
  2. Search for trustMode.
  3. Change trustMode="untrusted" to trustMode="trusted".

R.I.P  InvokeAction, commandButton, goLink, commandToolbarButton😪: 

- invokeAction is deprecated though it's usage is minimal in ADF applications they're a handful scenarios where is used it now I had to modify the places i used it.

- The change to decrease multiple buttons and links is understandable to keep one thing for a specific/similar purpose however changes to existing properties is not something I appreciate. As a developer of an enterprise application with multiple libraries I would be happy if it is simple for me to migrate on import rather me taking care of all the changes to components across libraries 😑

I wish i would question Mr. Frank Nimphus. Why did you make partialSubmit="true" now?

Much wanted freedom: 🙌

A pain for every developer is to skip the following multiple validations and instead show a message for the specific input component, which involved lot of coding in the bean earlier. 

Thanks to <af: target> tag now you can really target which component to re-render and which validations to fire again. This is a very welcoming change after all those pain getting your hands dirty with immediate, ppr and lot of coding.

Hot Deployment 💣: save your most valuable commodity

- We all know the pain we had to go through while developing apps using earlier versions of JDeveloper make a change kill your server and restart.

- However you can save some time by adding CHECK_FILE_MODIFICATION to true for some UI changes it is still not helping for model, bindings and changes with other config files. The new 12c somehow got the magic to do this for most cases.

- Require Deployment: web.xml

Responsive! Responsive! Responsive! 

This was very near to impossible with earlier versions though you can achiever this with some tweaks  like putting them in a separate and use it in an af:resource this is not really straight forward but now with <af:matchMediaBehavior /> it's more control on your components based on screen size.

Dependency Viewer:

Gives a nice visual view of dependencies/ references for the file.

Known Issues so far:

- getFilterCriteria() deprecated so you may have to change your filter reset logic.
- Filters not working for tables built on Read only VO.




Labels:

Comments

Post a Comment

Popular posts from this blog

Spring Boot - RestTemplate PATCH request fix

  In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this  bug Fix: This can b...
Post a Comment
Read more

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...
Post a Comment
Read more

Stored Procedures in ADF

One of the common requirements for ADF programmers is to invoke Stored Procedures and Functions. Implementing this is so simple with few lines of code in Java classes used under business components. Following code snippets from fusion guide  will help execute different procedures with and without arguments. Execute stored procedure with No Arguments: public void callProcWithNoArgs() { getDBTransaction().executeCommand( "begin devguidepkg.proc_with_no_args; end;"); } Execute stored procedure with only IN arguments: Procedures often take arguments in order to process some business logic. Arguments are limited from none to many. In order to use stored procedures with argument mode we need to use JDBC PreparedStatement object. How To: Create connection Create a JDBC PreparedStatement with procedure details wrapped in a PL/SQL begin..end block. Assign the values to arguments if any. Execute the statement. Close the statement. protected void callStoredPr...
Post a Comment
Read more