Posted on

Satyam to fire 4500 employees

 

Satyam computers is in the process of pink slipping 4500 of its employees, this ranges from Mangement level to entry level software developers who doesnt have a good feedback from their immediate supervisors.

 

Many of the experienced employees, who got the letter this week were shocked in the way they were shabbily thrown out of the company. Satyam has been facing pressures ever since it had a very negative quarter results last few quarters. Few years back it was the star of the IT stocks and now the poor man’s gold.

 

The company will serve termination notices to more employees in the coming weeks. Many employees who have earned the grudge of higher management are very anxious about their future in the company.

Posted on

What are the JSP implicit objects ?

The Objects available in any JSP without any need for explicit declarations are implicit Objects. All of these objects have atleast page page level scope.

pageContext:The context for the JSP page. Provides access to various objects including:
servletContext: The context for the JSP page’s servlet and any web components contained in the same application. See Accessing the Web Context.
session: The session object for the client. See Maintaining Client State.
request: The request triggering the execution of the JSP page. See Getting Information from Requests.
response: The response returned by the JSP page. See Constructing Responses.

Apart from the above objects some more functionality is provided by following objects

param: Maps a request parameter name to a single value
paramValues: Maps a request parameter name to an array of values
header: Maps a request header name to a single value
headerValues: Maps a request header name to an array of values
cookie: Maps a cookie name to a single cookie
initParam: Maps a context initialization parameter name to a single value
Finally, there are objects that allow access to the various scoped variables described in Using Scope Objects.

pageScope: Maps page-scoped variable names to their values
requestScope: Maps request-scoped variable names to their values
sessionScope: Maps session-scoped variable names to their values
applicationScope: Maps application-scoped variable names to their values
When an expression references one of these objects by name, the appropriate object is returned instead of the corresponding attribute. For example, ${pageContext} returns the PageContext object, even if there is an existing pageContext attribute containing some other value.

Posted on

What is the use of managed-bean-scope flag in the faces-config.xml (JSF)?

What is the use of managed-bean-scope flag in the faces-config.xml in JSF ?


Managed bean scope defines the lifespan of managed bean. There are 4 possible values: “application”, “session”, “request” and “none”.

The request scope bean is short-lived. If the bean is needed and created when server receives an HTTP request, it will be destroyed as soon as the response is sent back to the client.

The session scope bean persists from the time that a session is established until session termination. A session terminates if the web application invalidate session manually, or if it times out (this timeout period is defined in your servlet container configuration, and usually lasts few minutes). This means that after your bean is created, it will last for some time and between requests. For example, in a shopping application, you want the server to remember the contents of the shopping cart for some user across several pages.

Application scope beans are persisted for the duration of the application.

“None” is not exactly a scope, and is used for beans that are used only as managed properties of another beans.