Very Rare Photos-Railway Line Construction in Ceylon in 18th Century ( Sri Lanka )

Highway and Railway near Banderawela, Ceylon.

A mountain station Ohiya, Ceylon in 1894.

Riding on the railroad

Tunnels on the Railway near Ohiya, Ceylon

 

Sensation Rock, Kadugannawa Railroad Incline 1910 - Kadugannawa, Ceylon

 

Colombo to Kandy Railway, Ceylon

 

 

sensation rock

 

View on the Railway Columbo to Kandy, Ceylon

 

 

Undergoing constructions of a Tunnel, Colombo - Kandy Railway Line, c. 1860

 

 

Undergoing constructions of Colombo - Kandy Railway Line 1860

 

 

 

 

A Government Railway bridge in Ceylon 1880-1890

 

 

Kadugannawa Railway Station Colombo - Kandy, Ceylon

 

 

Construction on Government Railway Line, Ceylon

 

Undergoing constructions of Colombo - Kandy Railway Line 1860

 

 

Colombo Central Railway Station, Ceylon 1860 to 1880

 

 

Colombo to Badulla on the main line at Kadugannawa incline

 

 

Railway Bridge Over Gintota River (Gin Ganga), Galle in 1894

 

 

Lion's Mouth Colombo Kandy Line

 

 

Pothuhera Railway Station, Kurunegala, Ceylon 1890's

 

 

Ceylon Railway Engine 66 at Kurunegala in 1909

 

 

Railway tracks to Kandy, Ceylon c1890s

 

  

JSF Core & HTML Tags

JSF HTML Tags :

• column                              creates column in a dataTable
• commandButton                creates button
• commandLink                   creates link that acts like a pushbutton
• dataTable                         creates a  table control
• form                                 creates a form
• graphicImage                    displays an image
• inputHidden                      creates hidden field
• inputSecret                       creates input control for password
• inputText                          creates  text input control (single line)
• inputTextarea                    creates  text input control (multiline)
• message                           displays the most recent message for a component
• messages                          displays all messages
• outputFormat                    creates  outputText, but formats compound messages
• outputLabel                      creates label 
• outputLink                        creates anchor
• outputText                        creates single line text output
• panelGrid                         creates html table with specified number of columns
• panelGroup                      used to group other components where the specification requires one child element
• selectBooleanCheckbox   creates checkbox
• selectManyCheckbox       creates set of checkboxes
• selectManyListbox           creates multiselect listbox
• selectManyMenu              creates multiselect menu
• selectOneListbox              creates single select listbox
• selectOneMenu                creates single select menu
• selectOneRadio                creates set of radio buttons 

JSF CORE Tags: 

• f :view                                 Creates the top-level view
• f:subview                             Creates a subview of a view
• f:attribute           Adds an attribute  to a component
• f:param                                Constructs a parameter component
• f:converter            Adds an arbitrary converter to a component
• f:converterDateTime      Adds a datetime converter to a component
• f:converterNumber       Adds a number converter to a component
• f:actionListener          Adds an action listener to a component
• f:valueChangeListener     Adds a valuechange listener to a component
• f:validator              dds a validator to a component
• f:validateDoubleRange    Validates a double range for a component’s value
• f:validateLength         Validates the length of a component’s value
• f:validateLongRange      Validates a long range for a component’s value
• f:facet                 Adds a facet to a component
• f:loadBundle            Loads a resource bundle, stores properties as a Map
• f:selectitems            Specifies items for a select one or select many component
• f:selectitem             Specifies an item for a select one or select many component
• f:verbatim              Adds markup to a JSF page

JSF - Java Server Faces

JSF:  A server side user interface component framework for Java™ technology-based web applications.Java-server Faces (JSF) is an industry standard and a framework for building component-based user interfaces for web applications. JSF contains an API for representing UI components and managing their state; handling events, server-side validation, and data conversion; defining page navigation; supporting internationalization and accessibility; and providing extensibility for all these features. Java Server Faces applications are just like any other Java web application. They run in a servlet container.

ADV:  Faces has the following advantages over Struts:
     Eliminated the need for a Form Bean
     Eliminated the need for a DTO Class
     Allows the use of the same POJO on all Tiers because of the Backing Bean
# A separate rendering model that defines how to render the components in various ways. For example, a component used for selecting an item from a list can be rendered as a menu or a set of radio buttons.
# An event and listener model that defines how to handle events generated by activating a component, such as what to do when a user clicks a button.

Managed BEAN :
Java Bean objects managed by a JSF implementation are called managed beans. A managed bean describes how a bean is created and managed. It has nothing to do with the bean's functionality.

Backing Beans	Managed Beans
A backing bean is any bean that is referenced by a form.	A managed bean is a backing bean that has been registered with JSF (in faces-config.xml) and it automatically created (and optionally initialized) by JSF when it is needed.
	The advantage of managed beans is that the JSF framework will automatically create these beans, optionally initialize them with parameters you specify in faces-config.xml,
Backing Beans should be defined only in the request scope	The managed beans that are created by JSF can be stored within the request, session, or application scopes

View Object : 

A view object is a model object used specifically in the presentation tier. It contains the data that must display in the view layer and the logic to validate user input, handle events, and interact with the business-logic tier. 

Domain Object :
Domain object model is about the business object and should belong in the business-logic tier. It contains the business data and business logic associated with the specific business object.

Difference between JSP-EL and JSF-EL?

JSP-EL	JSF-EL
In JSP-EL the value expressions are delimited by ${…}.	In JSf-EL the value expressions are delimited by #{…}.
The ${…} delimiter denotes the immediate evaluation of the expressions, at the time that the application server processes the page.	The #{…} delimiter denotes deferred evaluation. With deferred evaluation ,the application server retains the expression and evaluates it whenever a value is needed.

Declare the managed beans in the faces-config.xml file?

The bean instance is configured in the faces-config.xml file:

<managed-bean>
  <managed-bean-name>login</managed-bean-name>
  <managed-bean-class>com.developersBookJsf.loginBean</managed-bean-class>
  <managed-bean-scope>request</managed-bean-scope>
  </managed-bean>
  

Page navigation (navigation rules) in faces-config.xml file ?

Navigation rules tells JSF implementation which page to send back to the browser after a form has been submitted. We can declare the page navigation as follows:

<naviagation-rule>
    <from-view-id>/index.jsp</from-view-id>
    <navigation-case>
  <from-outcome>login</from-outcome>
  <to-view-id>/welcome.jsp</to-view-id>
    </navigation-case>
  </naviagation-rule>
    
  

  [If no navigation rule matches a given action, then the current page is redisplayed.]

JSF LIFE CYCLE

Leadership and Organizational Behavior

Organizational Behavior (OB) is the study and application of knowledge about how people, individuals, and groups act in organizations. It does this by taking a system approach. That is, it interprets people-organization relationships in terms of the whole person, whole group, whole organization, and whole social system. Its purpose is to build better relationships by achieving human objectives, organizational objectives, and social objectives.

http://www.nwlink.com/~donclark/leader/leadob.html

Difference between Portal, Portlet, Blog, Forum ?

A Portal is a web site that acts as hub, gateway or window to other information and services on the Web. Common Web portals are Yahoo, Netscape, etc.

A Portlet is a specialised content area that occupies a small window of a portal page. Portlets from different sources (Portlet Providers) can be integrated into the portal framework. Example portlets: weather info, news flashes, stock tickers, etc.

 A Blog is Yours, and A Forum is Not

Blog, you set up your account and site, design it to look the way you want it to look, add advertising in some cases, and write regularly. Over time, both by your own design and as a result of what you've written, your blog develops a "personality". You can elect to allow comments or not. Blogs are often devoted to a specific topic, although some are devoted to a number of topics (for example, "All the things I've thought" or "What I did today") that, essentially, are only related by virtue of the fact that the same person wrote them.
A forum belongs to someone else (a company, an online site, a non-profit organization, or anyone who who creates and runs the forum).

A Forum is a collection of posts offered by the general public, often in a question-and-answer format although some forums are nothing but comments on a post that, itself, was nothing but a comment.

 

Warren Buffett

"I always knew I was going to be rich. I don't think I ever doubted it for a minute" - Warren Buffett

Difference JSF Version's

JSF started its journey from version 1.0 and now it has come to the latest version of JSF is 1.2. The listing of versions released so far are :

1. JSF 1.2 (11 may 2006) -     Latest release of JSF specification.
2. JSF 1.1 (27 may 2004) -     Bug fix release. No specification changes. No HTML renderkit changes.
3. JSF 1.0 (11 mar 2004) -     Initial release of JSF specification.

There are many releases of 1.1 and 1.2 and these are listed below showing released date also:

1. 1.2_04 P01  (20 Mar 2007)
2. 1.2_04         (5 Mar 2007)
3. 1.2_02         (25 Aug 2006)
4. 1.2_01         (14 July 2006)
5. 1.1_02         (24 Apr 2006)   
6. 1.1_01         (07 Sep 2004)

The JSF specification was developed under the Java Community Process (JCP) as JSR 127, which released JSF 1.0 and 1.1, and JSR 252 which released JSF 1.2. The first release of JSF is JSF 1.0 in 2004. JSF 1.0 supports servlet 2.3 and jsp 1.2. After JSF 1.0, JSF 1.1 was released. The main purpose of this release was bug-fixing. There were no specification or HTML renderkit changes. This version also works with same version of servlet 2.3 and jsp 1.2 as in the case of JSF 1.0.

JSF 1.1_01 release features bug fixes and performance improvements. Improvements include compression of views serialized to the client, failover support when storing views on the server, renderer fixes, and several other bug fixes and enhancements.It supports JDK 1.3.1 or later.  Many bugs have been fixed so if your application depends on one of these bugs, it needs to be changed.

JSF  1.2 is the latest release and it works with servlet 2.5 and jsp 2.1. If you want to run JSF 1.2 on Tomcat, you want 6.0 not 5.5. So JSF needs a web container that supports atleast servlet 2.3 and jsp 1.2 and these are part of J2EE 1.3.

New in JSF 1.2

In this section we will go through some new features and changes in JSF 1.2 specification. JSF 1.1 was designed for JSP 1.2 and so could not take advantage of newer JSP features and JSP could not be changed to fill the needs of JSF. This resulted in a number of new features and changes. For ex.

1. Unified Expression Language(EL) :
   Unified EL has been added to JSTL to overcome problems when integrating JSP EL with the JSF EL.EL was used to access data objects in a simple way. It is used mainly as a short-hand for accessing values. Later it was included in JSP 2.0 with more functionality.When JSF was released it also needed EL.JSF and JSP each has its own EL.The JSP EL is much flexibile to the web application developer but JSF people were unsatisfied by the JSP EL.One of the reason was that it requires JSP engine to evaluate expression at the appropriate time during the lifecycle, but JSP expressions are evaluated immediately. The second reason behind it was that JSP functions could only call static methods in TLD and they cannot be used to invoke public methods dynamically on server side objects during lifecycle to validate data and handle component evevts.
   So these were the reasons for developing such an EL that would work for both JSP and JSF and make using JSP and JSF together easier. This new EL is called unified EL. So this was inspired by EL used in JSTL and JSP. There is a package "el" in javax package that represents EL.
   
   In addition to the features already available in the JSP EL, unified EL has the following features :
   1.  Deferred evaluation of expressions i.e.evaluation of the expression at the appropriate time during the page lifecycle from JSP engine.
   2.  Support for expressions that can set and get values
   3.  Support for expressions that can invoke methods.
   4.  A pluggable API for resolving expressions
   
2. Ajax Support :
   JSF framework can make things a little easier to write AJAXian JSF components.JSF allows to map different instances of the FacesServlet with different lifecycles.For example, one mapping for standard JSF requests and another for AJAX JSF requests.
   
3. New Tree Creation and Content Interweaving Model for Faces applications that use JSP :
   We can make JSF application without using any JSP page but it can also be developed using both JSP and JSF.Using JSP makes some developers easy to handle.Sometimes When integrated it did not respond as we expect. These problems have been resolved in JSF 1.2.There have been made some changes in specification of the implementation of the FacesViewHandler for JSP and JSP custom tag base class.
   
4. Integration with JSTL :
   Using JSTL's tag to contain Faces input components was one of the problem, because JSP has no notion of a postback, it was not possible to apply the values correctly to the nested input components on postback. Some new concepts in EL make it possible to use this tag fully with any kind of JSF component.
   
5. Back Button issues and Multi Frame or Multi Window Faces Apps :
   JSF have fixed the problem related to Multi Frame or Multi Window applications.The browser back button also created some problems. These problems were because of deficiency in the State Management API.
   
6. Associating a message with a particular component in the page :
   Previously we could not include label of a component dynamically in an error message for that component. Now it's possible in new JSF 1.2.It's also possible to override the conversion or validation message that is displayed to the user on a per-instance basis.
   
7. Expose an application wide ResourceBundle to the EL :
   element in faces-config allows listing many resource bundles that should be exposed to the EL using the new ELResolver chain.This optimize performance and prevent the need to create a ResourceBundle for every request.
   
8. Use of multiple renderKits.
9. Provide XML Schema for the config files, instead of using DTD.
10. Security enhancements for client side state saving.
11. Solve the "duplicate button press" problem.
12. The portlet related bug-fixes.

Rifidi

Rifidi is a complete middleware platform for building all facets of an RFID application.   With the industry leading prototyping tools and a cutting edge RFID middleware server, Rifidi can take you from an RFID Idea to a production application. 

Rifidi makes it possible to do rapid RFID prototyping and production deployments on a high performance, open source platform.

http://www.rifidi.org/

Apache Struts 2

Apache Struts 2 is MVC (Model View Controller) design pattern based user interface development (UI) framework. Struts2 plays the role of Controller within the MVC design, where the View could be any view technology like JSPs/Tiles, JSF etc and the Model could be JavaBeans or Enterprise Java Beans(EJBs) etc. Just like other major J2/EE frameworks it is POJO (Plain Old Java Objects) based development framework, which facilitates testing and decoupling.

It is an elegant, extensible framework for creating enterprise-ready Java web applications. The framework is designed to streamline the full development cycle, from building, to deploying, to maintaining applications over time.
Apache Struts 2 was originally known as WebWork 2. After working independently for several years, the WebWork and Struts communities joined forces to create Struts². This new version of Struts is simpler to use and closer to how Struts was always meant to be.

JBPM - Workflow

jBPM is a flexible Business Process Management (BPM) Suite. It makes the bridge between business analysts and developers. Traditional BPM engines have a focus that is limited to non-technical people only. jBPM has a dual focus: it offers process management features in a way that both business users and developers like it.

What does jBPM do?

jBPM takes process descriptions as input. A process is composed of activities that are connected with transitions. Processes represent an execution flow. The graphical diagram of a process is used as the basis for the communication between non-technical users and developers.
Each execution of a process definition is called a process instance.  jBPM manages the process instances. Some activities, like sending an email or executing a script, are automatic. Other activities involve waiting for an external ocurrence, such as a person completing a task or an application calling back with the results of a request. jBPM keeps track of the state of the process executions during those wait periods.