Dileep Kumar Rongali

Many might have faced this situation while fixing bugs in ADF application. There will be one main application and it uses task flows or classes from different shared libraries. For example there is an issue in one shared library, to fix that we just run that particular project/application and try to fix the issue in that shared library project. But if the application is ADF security enabled then it is little difficult to perform exact test cases what we do when it is integrated with main application after fix. Because all the security settings are in main application jazn-data.xml file. We can disable security for a while and test the application. But it is not a good idea. Because by disabling security we are not doing full testing at all. So how to overcome this situation?   There is a sample way. We can create some dummy test users and test roles in development weblogic server. These test roles names should be same as the one we defined in jazn-data.xml in...

In real time application deployment, few values for application will be changing from environment to environment. Example, Database details. In development, Testing and in production environments we use different JDBC connection details. So hard coding this details in the code is not a good approach. Because every time we change these details we need to recreate the EAR and deploy. Instead we can refer these values from external file and use in the code, we no need to recreate EAR every time when we change environments. Or any other application properties which will change time to time from environment to environment. To handle the above scenario we have option called properties files. Property file is simple flat text file which stores key-value information like java.util.Map. In runtime, we read this property file and get the value for which key we need the code. Below is the sample property file. ---------------------------------------------------------------------------...

oracle.jbo.InvalidOperException: JBO-25221: Method EmployeeAppModuleDataControl.dataProvider.getEmployees() not supported For above issue there could be several reasons.    1)   Check in the method binding any special html characters are present. Because ADF bindings does not support generics. So for example the input value for client method has generics, there are chances that in the pageDef method binding might have special hmtl character when we drag and drop the client method in page or page fragment. We can remove those special characters to resolve the issue. For more information refer to https://community.oracle.com/message/4304798     2)   Second reason could be if AM client method and pageDef method binding not in sync. Whenever we modify client method in AM, we need to update the same in pageDef method binding also. Otherwise it will give above error.    3)   If none of the above are causing the issue then...