Book Review : Learning Ext JS 4

The folks at Packt asked me to review another of their book on Learning EXTJS 4 If you are interested in buying it (a judgment you may reserve until after you have read the review)EXTJS4 is on packt site
this is link you can go.Learning EXtJs 4 is on packt site

Crysfel Villa ,Armando Gonzalez are author of this book.Crysfel Villa is a Software Engineer with more than 7 years of experience with JavaScript on a daily basis.Armando Gonzalez is a Software Engineer with more than 4 years of experience
in developing enterprise applications with Ext JS. He has plenty of experience in
server-side technologies like PHP, Java J2EE, Node JS, and ROR.

The first thing you will probably notice is the size of the document. This is no brief summary of the new features. This is small book of over 40 pages covering to learn a new java script librart with a full index in the back. The structure of the book is:
Business overview

Step 1 – The Basics
Step 2 – The Core Concepts
Step 3 – Components and Layouts
Step 4 – It’s All About the Data
Step 5 – Buttons and Toolbars
Step 6 – Doing it with Forms
Step 7 –Give me the Grid
Step 8 – Architecture
Step 9 – DataViews and Templates
Step 10- The Tree Panel
Step 11 – Drag and Drop
Step 12 – Look and Feel
Step 13- From Drawing to Charting

I like this structure as it parallels the steps one would take in setting up a EXTJS 4. To add a bit of a flow to the book, they also put it in the examples,real life scenarios.

Its more a starter book.This book focuses on giving the reader a firm understanding of the core concepts of EXTJS, such as Drag and Drop and tree panel, and works through real-life app development scenarios. All core components of EXTJS’s amazing library are covered in detail, and strategies are outlined for getting the best use of time when developing with EXTJS.

Few components which i like to mention , which i enjoy reading alot – a clear explanation of how to make drag drop using EXTJS.
How tree panel compoenent work.How you can make charts components for example pie,bar , gauage. Skinning of application is well defined.

OVer all i can say this book for beginner.Few new features which is added in EXT JS 4 is added and describe well.A must purchase for those who want to learn EXT JS 4. You can also download the code which is available with the book

Happy coding with Techartifact and packt….

Changing the WHERE clause or VO Query at runtime in Oracle ADF

Requirement- To change the WHERE clause of a query at run time:

Create a String containing the new WHERE clause. Do not include the word “WHERE”. If you do want to remove the WHERE clause entirely, use null. For example, either of the following could be appropriate definitions:

Pass this string into setWhereClause(). For example, if OrdVO is a variable containing the view object instance to be changed, you would call:

String whereClause = “ORDER_TOTAL > 500”;
String whereClause = null;
ordVO.setWhereClause(whereClause);

You can write this method in AmImpl.Java.For example

    public void executeSearchInstanceNoExp(String instanceNo) {
    String whereClause="instance_status = 'EXPIRED'";
    ViewObjectImpl searchVO = this.getEmployeeVo(); //relaventVO
    searchVO.setWhereClause(whereClause);
    searchVO.executeQuery(); //executeVO with Criteria

    }

you can add ORDER BY clauses of a query at runtime by calling setOrderByClause() on the view object.

String orderByClause = "ORDER_TOTAL";
ordVO.setOrderByClause(orderByClause);

Change the VO query at runtime or changing the Table or view at runtime

createViewObjectFromQueryStmt is used to change the query .You can write this method in AmImpl.Java

    public void executeSearchVoExp() {
       String sqlStatement= "select * from EMP";
        ViewObject dynamicVO = this.findViewObject("SearchByCustomerVo1");  
        dynamicVO.remove();  
        dynamicVO = this.createViewObjectFromQueryStmt("SearchByCustomerVo1", sqlStatement);  
        dynamicVO.executeQuery(); //executeVO with Criteria

    }

New Features in JSF 2.0

With many new features, JSF 2.0 is an evolution from 1.2, but it’s also a step forward—for example, in
terms of PDL, where Facelets is preferred to JSP. New features of JSF 2.0 include the following:

• An alternative viewing technology to JSP based on Facelets

• Easier navigation between pages with implicit and conditional navigation

• JSF has been using POST HTTP requests intensively; this new release brings back GET requests as a first-class citizen (allowing users to bookmark pages)
• A new resource-handling mechanism (for images, CSS, JavaScript files, and so on)

• Additional scopes (view scope, flash and component scope)

• Easy development with annotations for managed beans, renderers, converters,validators, and so on.

• Reducing XML configuration by exploiting annotations and configuration by exception (faces-config.xml is optional)

• Ajax support

• Better error handling (provides information such as line numbers and not just a stack trace)

• Easy component development

I will also point some differences between JSF 1.2 and JSF 2.0
JSF 1.2 JSF 2.0
Pure JSF without any bells and whistles specific to JSF 2 (Ajax stuff and such) – the difference while in JSF 2.0 this has become mostly unnecessary. But that is not really where
won’t be that great. What you have additionally in JSF 1.2 is the need to declare everything i you lose the time.Only when you start to think about custom components will JSF
n a faces-config.xml file. 2.0 give you faster development cycle because it has made easier through facelets.
It take little more time than JSF 2.0 It can save your time compared to JSF 1.2