import org.springframework.beans.factory.xml.XmlBeanFactory;
import org.springframework.core.io.ClassPathResource;

public class Dcm_spring_factory {
private static XmlBeanFactory factory = new XmlBeanFactory(new ClassPathResource(“/META-INF/spring/applicationContext.xml”));

public static XmlBeanFactory getFactory() {
return factory;
}

public void setFactory(XmlBeanFactory factory) {
this.factory = factory;
}

}
As you can see ,we had used private static XmlBeanFactory factory = new XmlBeanFactory(new ClassPathResource(“/META-INF/spring/applicationContext.xml”));
That’s the first part of the Singleton’s desing pattern is that to make the attribute Static so that can be shared by all the object instancited from the class Dcm_spring_factory.
The next and the last part of the Singleton desing pattern is to make all the classes heritates from our Factory class Dcm_spring_factory.
Example:
public class Task_page_site_admin extends dcm.controller.global_factory.Dcm_spring_factory

Enjoy

http://java.sun.com/javafx/

http://www.redhat.com/developers/partners/exadel/

Max will speak about New Richfaces 4.0 and guess what i had found.The first datasheet of the new Richfaces 4.0 API.

http://www.jboss.org/community/wiki/RichFaces40Planning

The good news is that Richfaces 4.0 will be 100 % compatible with the new JSF 1.2 RI.

The bad news is that the first stable version will be availble in 2010.

Enjoy

Test-driven development (TDD) is a software development technique that uses short development iterations based on pre-written test cases that define desired improvements or new functions. Each iteration produces code necessary to pass that iteration’s tests. Finally, the programmer or team refactors the code to accommodate changes. A key TDD concept is that preparing tests before coding facilitates rapid feedback changes. Note that test-driven development is a software design method, not merely a method of testing.

Test-Driven Development is related to the test-first programming concepts of Extreme Programming, begun in 1999,[1] but more recently is creating more general interest in its own right

Programmers also apply the concept to improving and debugging legacy code developed with older techniques
The following sequence is based on the book Test-Driven Development by Example,[4] which many consider to be the canonical source text on the concept in its modern form.

1. Add a test
In test-driven development, each new feature begins with writing a test. This test must inevitably fail because it is written before the feature has been implemented. (If it does not fail, then the proposed “new” feature is obviated.) To write a test, the developer must clearly understand the feature’s specification and requirements. The developer can accomplish this through use cases and user stories that cover the requirements and exception conditions. This could also imply a variant, or modification of an existing test. This is a differentiating feature of test-driven development versus writing unit tests after the code is written: it makes the developer focus on the requirements before writing the code, a subtle but important difference.

2. Run all tests and see if the new one fails
This validates that the test harness is working correctly and that the new test does not mistakenly pass without requiring any new code.

The new test should also fail for the expected reason. This step tests the test itself, in the negative: it rules out the possibility that the new test will always pass, and therefore be worthless.

3. Write some code
The next step is to write some code that will cause the test to pass. The new code written at this stage will not be perfect and may, for example, pass the test in an inelegant way. That is acceptable because later steps will improve and hone it.

It is important that the code written is only designed to pass the test; no further (and therefore untested) functionality should be predicted and ‘allowed for’ at any stage.

4. Run the automated tests and see them succeed
If all test cases now pass, the programmer can be confident that the code meets all the tested requirements. This is a good point from which to begin the final step of the cycle.

5. Refactor code
Now the code can be cleaned up as necessary. By re-running the test cases, the developer can be confident that refactoring is not damaging any existing functionality. The concept of removing duplication is an important aspect of any software design. In this case, however, it also applies to removing any duplication between the test code and the production code — for example magic numbers or strings that were repeated in both, in order to make the test pass in step 3.

Repeat
Starting with another new test, the cycle is then repeated to push forward the functionality. The size of the steps should always be small – as few as 1 to 10 edits between each test run. If new code does not rapidly satisfy a new test, or other tests fail unexpectedly, the programmer should undo or revert in preference to excessive debugging. Continuous Integration helps by providing revertible checkpoints. When using external libraries it is important not to make increments that are so small as to be effectively merely testing the library itself,[2] unless there is some reason to believe that the library is buggy or is not sufficiently feature-complete to serve all the needs of the main program being written.

http://livedemo.exadel.com/richfaces-demo/richfaces/actionparam.jsf

That’s for you Fatma
looooooooooooool

XmlBeanFactory factory = new XmlBeanFactory(
   new ClassPathResource("/META-INF/spring/applicationContext.xml"));
   Task_operation_project_leader task_operation_project_leader_ =   (Task_operation_project_leader)factory.getBean("task_operation_project_leader");
  
   Integer ressource_id_=Integer.parseInt(this.session.getAttribute("ressource_id").toString());
   task_operation_project_leader_.add_new_task
   Shared_data_implements shared_data_implements_ =   (Shared_data_implements)factory.getBean("shared_data_implements");
  
  
   //clear
 
   this.add_task_members_=new Task_members(); ;
  this.binding_modal_panel_add_task.setRendered(false);//Well here we make render attribute of rendered in the modal panel false
 
  return true;
}


One of them is that we must make the modal panel outside the h:form (i mean the main form)

A second thing we must focus on is that ModalPanel API has been changed from its first appearance in 3.1.0 version so keep in mind to have a look at Migration Guide

Here is an example
 <!–  Start of Modal panel of Add New Project –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>

<rich:modalPanel id=”add_new_project” rendered=”false”   showWhenRendered=”true” binding=”#{pole_manager_page.binding_modal_panel_show_add_new_project_pole_sky_project}” width=”700″ height=”600″ autosized=”true” resizeable=”false”>
 <f:facet name=”header”>
            <h:panelGroup>
                <h:outputText value=”Add New Project”></h:outputText>
            </h:panelGroup>
        </f:facet>
 <f:facet name=”controls”>
            <h:panelGroup>
                <h:graphicImage value=”close.png” styleClass=”hidelink” id=”hidelink_add_new_project”/>
                <rich:componentControl for=”add_new_project” attachTo=”hidelink_add_new_project” operation=”hide” event=”onclick”/>
            </h:panelGroup>
        </f:facet>
<h:form id=”id_add_new_project”>
<div style=”position:absolute;
 left:30px;
 top:30px;
 width:670px;
 height:570px;
 background-color:#ffffff;
 overflow:auto;”>

 
<table width=”474″ border=”0″>
  <tr>
    <td width=”177″>Final Customer </td>
    <td width=”281″>
    <h:inputText required=”true” id=”id_add_new_project_final_customer” value=”#{pole_manager_page.add_new_project_members_.final_customer}”>
     <rich:ajaxValidator event=”onblur”/>
      <f:validateLength minimum=”3″ maximum=”40″/>
     </h:inputText>
      <rich:message for=”id_add_new_project_final_customer”></rich:message>
    </td>
 
  </tr>

  <tr>
    <td>Project Name </td>
    <td><h:inputText required=”true” id=”id_add_new_project_project_name” value=”#{pole_manager_page.add_new_project_members_.project_name}” >
   <f:validateLength minimum=”3″ maximum=”40″/>
      <rich:ajaxValidator event=”onblur”/>
   </h:inputText>
      <rich:message for=”id_add_new_project_project_name”></rich:message>
    </td>
  </tr>
 
 
  <tr>
    <td>Project Reference  </td>
    <td><h:inputText value=”#{pole_manager_page.add_new_project_members_.project_reference}” required=”true”>
    <f:validateLength minimum=”3″ maximum=”40″/>
     <rich:ajaxValidator event=”onblur”/>
    </h:inputText>
      <rich:message for=”id_add_new_project_project_name”></rich:message>
    </td>
  </tr>
 
 
 
 
 
  <tr>
    <td>Project Description</td>
    <td><h:inputText id=”id_add_new_project_project_description” value=”#{pole_manager_page.add_new_project_members_.project_description}” required=”true”>
    <f:validateLength minimum=”3″ maximum=”50″/>
         <rich:ajaxValidator event=”onblur”/>
       
    </h:inputText>
    <rich:message for=”id_add_new_project_project_description”></rich:message>
    </td>
  </tr>
 
 
 
 
 
 
 
  <tr>
    <td>Project Leader</td>
    <td><rich:comboBox value=”#{pole_manager_page.add_new_project_members_.selected_project_leader}”><f:selectItems value=”#{pole_manager_page.add_new_project_members_.available_project_leader}” /></rich:comboBox></td>
  </tr>

  <tr>
    <td>project_start_initial_base_line_date <rich:calendar required=”true” datePattern=”yyyy-MM-d” value=”#{pole_manager_page.add_new_project_members_.project_start_initial_base_line_date}”/></td>
    <td>project_end_initial_base_line_date  <rich:calendar required=”true”  datePattern=”yyyy-MM-d” value=”#{pole_manager_page.add_new_project_members_.project_end_initial_base_line_date}”/></td>
  </tr>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  <tr>
    <td>Project Cost(BCWS)
  
  
    <h:inputText  required=”true”
     value=”#{pole_manager_page.add_new_project_members_.project_bcws_initial}” >
     <f:validateLength minimum=”0″ maximum=”50″/>
         <rich:ajaxValidator event=”onblur”/>
             </h:inputText>
       
        
 
  
    </td>
  

  </tr>
 
 
 
 
 
 
 
 
 
 
  <tr>
    <td><h:commandButton value=”Save” action=”#{pole_manager_page.confirm_add_new_project}”/></td>
    <td><h:commandButton value=”Cancel” immediate=”true” action=”#{pole_manager_page.cancel_show_modal_panel_x}”/></td>
  </tr>
</table>

 
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
</div>
</h:form>

</rich:modalPanel>

 
<!–  End  of Modal panel of Add New Project –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>
<!–///////////////////////////////////// –>

In the backend bean :

public void cancel_show_modal_panel_x()
 {
  this.binding_modal_panel_show_add_new_project_pole_sky_project.setRendered(false);

 }

/**
  * @uml.property  name=”binding_modal_panel_show_add_new_project_pole_sky_project”
  */
 private HtmlModalPanel binding_modal_panel_show_add_new_project_pole_sky_project = null;

 /**
  * Getter of the property <tt>binding_modal_panel_show_add_new_project_pole_sky_project</tt>
  * @return  Returns the binding_modal_panel_show_add_new_project_pole_sky_project.
  * @uml.property  name=”binding_modal_panel_show_add_new_project_pole_sky_project”
  */
 public HtmlModalPanel getBinding_modal_panel_show_add_new_project_pole_sky_project() {
  return binding_modal_panel_show_add_new_project_pole_sky_project;
 }

 /**
  * Setter of the property <tt>binding_modal_panel_show_add_new_project_pole_sky_project</tt>
  * @param binding_modal_panel_show_add_new_project_pole_sky_project  The binding_modal_panel_show_add_new_project_pole_sky_project to set.
  * @uml.property  name=”binding_modal_panel_show_add_new_project_pole_sky_project”
  */
 public void setBinding_modal_panel_show_add_new_project_pole_sky_project(
   HtmlModalPanel binding_modal_panel_show_add_new_project_pole_sky_project) {
  this.binding_modal_panel_show_add_new_project_pole_sky_project = binding_modal_panel_show_add_new_project_pole_sky_project;
 }

Remember getter and setter must be available to make the modal panel works

Enjoy

Let’s see it

<rich:scrollableDataTable rowKeyVar="rkv" frozenColCount="1" height="400px"
selection="#{pole_manager_page.data_table_value_pole_sky.selection}"
binding="#{pole_manager_page.data_table_value_pole_sky.table}"
width="700px" id="id_data_scrollable_table_projects"
rows="#{pole_manager_page.data_table_value_pole_sky.data_scrollable_table_size}"
columnClasses="col"
value="#{pole_manager_page.data_table_value_pole_sky.allCars}" var="category" sortMode="single"
>

</h:outputText>
</rich:column>
</rich:scrollableDataTable>


Now let’s define our magic object Data_table_value_pole_sky.

This object has been got from this class DataScrollableTableProjectsPoleManager.

It’s not a good practise to implement the DataScrollableTable in the same class as your bean class .

public class DataScrollableTableProjectsPoleManager extends dcm.controller.global_factory.Dcm_spring_factory{
/****************************Start of Local Variable **********************************************/
/*************************************************************************************************/
/************************************************************************************************/
/***********************************************************************************************/

/**
* @param data_scrollable_table_size the data_scrollable_table_size to set
*/
public void setData_scrollable_table_size(Integer data_scrollable_table_size) {
this.data_scrollable_table_size = data_scrollable_table_size;
}
}


I think it’s very good Unit test API well docmented in Jboss website

have a look

http://www.jboss.org/jsfunit/