Connecting the {Dots}

If you really want to get a feel of  Node.js, Express, Jade , then check out  the following tutorial- simple and easy to follow : http://cwbuecheler.com/web/tutorials/2013/node-express-mongo/

If you had tried using   Contexts and Dependency Injection (CDI) in your ADF app targeting WLS 12C, you might have already noticed the issue that I'm mentioning here - CDI things are not working in the application by default. Well, here is a solution. See this blog which talks about the same: post  https://weblogs.java.net/blog/mriem/archive/2013/12/10/jsf-tip-54-enable-cdi-when-bundling-jsf?force=659 To keep things simple, do the  following: Download the cdi-enabler jar from the following mavne repo:  https://maven.java.net/content/groups/public/com/oracle/cdi-enabler/cdi-enabler-1_0/1/cdi-enabler-1_0-1.jar Add it as dependency to your view controller project where you use CDI. Open the beans.xml file and add alternatives as shown below: <?xml version = '1.0' encoding = 'windows-1252'?> <beans xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://java.sun.com/xml/ns/javaee http://java.sun....

While working on large projects, you may split business components among multiple projects to improve the modularity and re-usability of the code. Obviously you can share business components between multiple model projects by packaging them in ADF library. While doing so, you may want to expose view objects from an ADF library as web service through an application module that reside in a consuming project. Though this is pretty straight forward task, you need to be aware of one point while packaging view objects in ADF library that may be later exposed as web service from another project. The point here is that,  you need to generate Service Data Object for view object  in the owning project itself. In other words you cannot expose view objects from ADF library as web service  if the view objects in ADF library are not having Service Data Object generated. To generate SDO for a view object: Go to the project that you want to share as ADF library. Open the view objec...

In case, if you hit the below error while deploying MAF application to android device, this post is for you. [12:11:31 PM] Cannot run program "xxx\adt-bundle-windows-x86_64-20140321\sdk\tools\zipalign"": CreateProcess error=2, The system cannot find the file specified [12:11:31 PM] CreateProcess error=2, The system cannot find the file specified When generating an deployable artifact(apk), JDeveloper uses zipalign.exe that comes with ADT. This used to be located in /sdk/tools, but (with latest ADT release) it is now located in /sdk/build-tools/ folder. A quick work around (till the fix is available in Jdev) for the above issue is to copy the appropriate  zipalign.exe to /sdk/tools folder. 

I'm not really sure how many of you have noticed af:codeEditor component that comes with ADF Faces. If you have note, see this demo: http://jdevadf.oracle.com/adf-richclient-demo/faces/components/codeEditor.jspx This UI component  allows you to view or edit content or program code in  text, xml, javascript or groovy at run time. It has also support for adding content validations. See the sample in Oracle ADF Faces Components Demo source ( see codeEditorMessaging.jspx and DemoCodeEditorMessagingBean.java ) which can be downloaded from here: http://www.oracle.com/technetwork/developer-tools/adf/downloads/index.html

If you want to perform functional testing of ADF Faces application with tools such as Oracle Application Test Suite(see this blog ), you may want to set few parameters in web.xml and one in trinidad-config .xml Add the following context parameters in web. xml : < context - param > < param - name > oracle . adf . view . rich . automation . ENABLED </ param - name > < param - value > true </ param - value > </ context - param > < context - param > < param - name > org . apache . myfaces . trinidad . DISABLE_CONTENT_COMPRESSION </ param - name > < param - value > true </ param - value > </ context - param > < context - param > < param - name > javax . faces . PROJECT_STAGE </ param - name > < param - value > SystemTest </ param - value > </ context - param > In trinidad-config. xml add the following: < animation - enabled > false ...

A while back I blogged about extending Java Bean Data Control to add some useful  features such as declarative view criteria support. If you have not  seen it , here is the link: http://www.jobinesh.com/2014/01/customizing-pojo-based-bean-data.html In this post I'm sharing the same solution as JDev extension. With  this extension, you can leverage the built-in editor support for building view criteria for a Bean DC (even if it's model is not backed up by JPA). You may also see the view criteria displayed in data control palette as in case of JPA based Bean DC.  In nutshell,this extension lifts your POJO based bean data control  to the level of JPA based bean DC. What is the JDev version supported by BeanDCExtension?  This is built using 12.1.3.0.0 release.  How to use this extension? Step 1. Down load the extension https://svn.java.net/svn/adf-samples~jobinesh/zipped-src/BeanDCExtension.zip Ste 2: Open JDeveloper 12.1.3.0.0...