Modern Java Coding

In an enterprise application deployment scenario, there are many cases where some libraries are used/referenced by multiple applications. It would indeed be a bad design to include such common libraries with every application deployed on the WebLogic server. Not only does it prevent redundancy of resources on the server, it also consumes valuable space & deployment time - especially when the libraries are huge. WebLogic server offers the shared library concept using which EARs, JARs, EJBs and WARs can be shared across applications in a WebLogic domain. Let us now see how to package and deploy a shared library in WebLogic server; Step 1: Create a folder structure as shown below Step 2: Copy all the libraries (in this case JAR files) that you would want to share across applications to the lib folder under WEB_INF Step 3: Create a file under META_INF folder by name "MANIFEST.MF" Step 4: Contents of the MANIFEST.MF file are shown below Manifest-Version: 1....

Configure ADF Logger 12c Oracle ADF 12c has very good error or exception logging mechanism. You have to define logger for your class or package and handler using em. Open logging.xml file stipulated at loc : <Middleware_home>/ Oracle_Home\user_projects\domains\XXX_domain\config\fmwconfig\servers\AdminServer Add logger to this file as below, <logger name=<class name or package name> level='FINEST' useParentHandlers='true'> Note: use full qualified class and package name and set appropriate logger level In EM, go to Log configuration for your application, Create you handler as below, Provide specific logger for you handler as below; Set appropriate logger level as you defined in your logger. Add your logger name that you have created in Logging.xml file. And verify you logs in file or EM.