Important HR Interview Questions

1.Are your work practices similar or different from ours?
(If Experienced)
2.Describe our (products/services).
3.Describe our company for me.
4.Describe our corporate environment for me.
5.Describe your work (methods/processes) in comparison to ours?
(If Experienced)
6.Do our competitors do things that we should be doing?
7.Do you have any concerns about working here?
8.Do you have any questions about (our/this) company?
9.Do you know how long we have been in business?
10.Do you know what products we make?
11.How could you have prevented your (judgmental) errors?
12.How do you think our company determines success?
13.How does you present employer communicate with others in your
deprtment? (If Experienced)
14.Tell me how you found out information about (our/this) company?
15.Tell me what you know about (our/this) company?
16.Was there anything your company could have done to be more
successful?
17.What about our company do you like best?
18.What about your present employer (do/did) you like best?
19.What advantages do you think our competitors have over us?
20.What advantages do you think we have over our competitors?
21.What are the greatest challenges that this company faces?
22.What concerns do you have about this company?
23.What direction do you think this company is headed in?
24.What do you dislike about our company?
25.What do you know about (our/this) company?
26.What do you know about (our/this) operation?
27.What do you know about our competitors?
28.What do you know about our customers?
29.What do you know about our products?
30.What do you know about our products or services?
31.What do you know about our stock?
32.What do you know about our web site?
33.What do you know about the way our company (works/operates)?
34.What do you know about this position?
35.What do you think are the challenges facing this company?
36.What do you think are the greatest challenges facing this company
in the near future?
37.What do you think it takes to be successful in a company like
ours?
38.What do you think it takes to be successful in our company?
39.What do you think the atmosphere here is like?
40.What is the financial stability of your last company?
41.What questions do you have about our organization?
42.What would make someone successful in our business?
43.What is the (best/worst) thing you have heard about (our/this)
company?
44. What is the (best/worst) thing you have heard about
(our/this) department?

Important Basic CVS Commands

login
-----
cvs -d :pserver:username:password@:2401/reposname login

import
------

cvs -d :pserver:username:password@:2401/reposname import -m "message" foldername INITIAL start

for example
/home/srinivas/test contains testzip folder

go to the path

cd /home/srinivas/test

execute the following command

cvs -d :pserver:username:password@:2401/reposname import -m "test" testzip INITIAL start

checkout
--------

cvs -d :pserver:username:password@:2401/reposname checkout modulename

What are the difference between DDL, DML and DCL commands?

DDL is Data Definition Language statements. Some examples:

• CREATE - to create objects in the database

• ALTER - alters the structure of the database

• DROP - delete objects from the database

• TRUNCATE - remove all records from a table, including all spaces allocated for the records are removed

• COMMENT - add comments to the data dictionary

• GRANT - gives user's access privileges to database

• REVOKE - withdraw access privileges given with the GRANT command

DML is Data Manipulation Language statements. Some examples:

• SELECT - retrieve data from the a database

• INSERT - insert data into a table

• UPDATE - updates existing data within a table

• DELETE - deletes all records from a table, the space for the records remain

• CALL - call a PL/SQL or Java subprogram

• EXPLAIN PLAN - explain access path to data

• LOCK TABLE - control concurrency

DCL is Data Control Language statements. Some examples:

• COMMIT - save work done

• SAVEPOINT - identify a point in a transaction to which you can later roll back

• ROLLBACK - restore database to original since the last COMMIT

• SET TRANSACTION - Change transaction options like what rollback segment to use

Hibernate Caching

An Introduction to Caching
Caching is widely used for optimizing database applications. A cache is designed to reduce traffic between your application and the database by conserving data already loaded from the database. Database access is necessary only when retrieving data that is not currently available in the cache. The application may need to empty (invalidate) the cache from time to time if the database is updated or modified in some way, because it has no way of knowing whether the cache is up to date.

Hibernate Caching
Hibernate uses two different caches for objects: first-level cache and second-level cache. First-level cache is associated with the Session object, while second-level cache is associated with the Session Factory object. By default, Hibernate uses first-level cache on a per-transaction basis. Hibernate uses this cache mainly to reduce the number of SQL queries it needs to generate within a given transaction. For example, if an object is modified several times within the same transaction, Hibernate will generate only one SQL UPDATE statement at the end of the transaction, containing all the modifications. This article focuses on second-level cache. To reduce database traffic, second-level cache keeps loaded objects at the Session Factory level between transactions. These objects are available to the whole application, not just to the user running the query. This way, each time a query returns an object that is already loaded in the cache, one or more database transactions potentially are avoided.

In addition, you can use a query-level cache if you need to cache actual query results, rather than just persistent objects.

Cache Implementations
Caches are complicated pieces of software, and the market offers quite a number of choices, both open source and commercial. Hibernate supports the following open-source cache implementations out-of-the-box:

* EHCache (org.hibernate.cache.EhCacheProvider)
* OSCache (org.hibernate.cache.OSCacheProvider)
* SwarmCache (org.hibernate.cache.SwarmCacheProvider)
* JBoss TreeCache (org.hibernate.cache.TreeCacheProvider)

Each cache provides different capacities in terms of performance, memory use, and configuration possibilities:

* EHCache is a fast, lightweight, and easy-to-use in-process cache. It supports read-only and read/write caching, and memory- and disk-based caching. However, it does not support clustering.
* OSCache is another open-source caching solution. It is part of a larger package, which also provides caching functionalities for JSP pages or arbitrary objects. It is a powerful and flexible package, which, like EHCache, supports read-only and read/write caching, and memory- and disk-based caching. It also provides basic support for clustering via either JavaGroups or JMS.
* SwarmCache is a simple cluster-based caching solution based on JavaGroups. It supports read-only or nonstrict read/write caching (the next section explains this term). This type of cache is appropriate for applications that typically have many more read operations than write operations.
* JBoss TreeCache is a powerful replicated (synchronous or asynchronous) and transactional cache. Use this solution if you really need a true transaction-capable caching architecture.

What is SDLC ?

System Development Life Cycle

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project from an initial feasibility study through maintenance of the completed application. Various SDLC methodologies have been developed to guide the processes involved including the waterfall model (the original SDLC method), rapid application development (RAD), joint application development (JAD), the fountain model and the spiral model. Mostly, several models are combined into some sort of hybrid methodology. Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely particular plan was followed.

The image below is the classic Waterfall model methodology, which is the first SDLC method and it describes the various phases involved in development.


The Waterfall Model

Briefly on different Phases:

Feasibility

The feasibility study is used to determine if the project should get the go-ahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development.

Requirement Analysis and Design

Analysis gathers the requirements for the system. This stage includes a detailed study of the business needs of the organization. Options for changing the business process may be considered. Design focuses on high level design like, what programs are needed and how are they going to interact, low-level design (how the individual programs are going to work), interface design (what are the interfaces going to look like) and data design (what data will be required). During these phases, the software's overall structure is defined. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.

Implementation

In this phase the designs are translated into code. Computer programs are written using a conventional programming language or an application generator. Programming tools like Compilers, Interpreters, Debuggers are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen.

Testing

In this phase the system is tested. Normally programs are written as a series of individual modules, these subject to separate and detailed test. The system is then tested as a whole. The separate modules are brought together and tested as a complete system. The system is tested to ensure that interfaces between modules work (integration testing), the system works on the intended platform and with the expected volume of data (volume testing) and that the system does what the user requires (acceptance/beta testing).

Maintenance

Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.

Very Impartant Java Links...

http://java.sun.com/j2ee/1.4/docs/tutorial/doc/EJBConcepts3.html

http://java.boot.by/ibm-287/ch05.html

http://www.allapplabs.com/glossary/idempotent.htm

http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html

http://www.javacamp.org/scwcd/httpservlet.html

https://java-net.dev.java.net/

http://java.sun.com/j2ee/1.3/docs/tutorial/doc/

http://www.javacoffeebreak.com/articles/toptenerrors.html

http://faq.javaranch.com/view?ScjpFaq

http://struts.apache.org/1.x/struts-extras/index.html

http://www.laliluna.de/first-steps-with-struts-free-tools-en.html

http://www.myeclipseide.com/ContentExpress-display-ceid-16.html

http://www.myeclipseide.com/images/tutorials/Hibernate/Hibernate.html

http://www.myeclipseide.com/images/tutorials/StrutsTutorial.htm

http://www.myeclipseide.com/images/tutorials/webprojectdemo.htm

http://www.myeclipseide.com/images/tutorials/Struts_Dyna.html

http://www.myeclipseide.com/images/tutorials/Struts_Dispatch.html

http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/DEA2eIX.html



http://ga.the-free-downloads.net/



http://www.javacoffeebreak.com/articles/toptenerrors.html

http://faq.javaranch.com/view?ScjpFaq



http://struts.apache.org/1.x/struts-extras/index.html



http://www.laliluna.de/first-steps-with-struts-free-tools-en.html



http://www.myeclipseide.com/ContentExpress-display-ceid-16.html



demo hibernate with myeclipseide: http://www.myeclipseide.com/images/tutorials/Hibernate/Hibernate.html



demo struts with myeclipseide: http://www.myeclipseide.com/images/tutorials/StrutsTutorial.htm



demo Ejb with myeclipseide:

http://www.myeclipseide.com/images/tutorials/MYSQL_Dbase.html

http://www.myeclipseide.com/images/tutorials/WebLogic_Setup.html

http://www.myeclipseide.com/images/tutorials/Entity_Bean.html

http://www.myeclipseide.com/images/tutorials/Client.html



imp java book : http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/DEA2eIX.html



http://worldebookfair.com/

http://worldebookfair.com/Technical_eBook_Colleciton.htm







http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/deployment/deployment4.html#1035644



http://sourcelabs.com/webinar/public/user/welcome?user[id]=360&key=21996947150ad71d55ab2b0475e4e5c034b3d4b0



www.theserverside.com

http://www.click-now.net



www.planetpdf.com



http://www.kevinboone.com/ejb-transactions.html

http://www.kevinboone.com/PF_ejb-transactions.html

http://www.idevelopment.info/

http://www.idevelopment.info/data/Programming/java/

http://www.idevelopment.info/data/Programming/java/PROGRAMMING_Java_Programming.shtml

http://onjava.com/

www.codeguru.com

http://www.developer.com/java/
http://www.dhtmlgoodies.com/index.html?page=ajax
http://www.dhtmlgoodies.com/index.html
http://www-128.ibm.com/developerworks/java/library/j-ajax1/index.html
http://www-128.ibm.com/developerworks/java/library/j-ajax2/
http://www.unwieldy.net/ajaxim/
http://www.ajaxmatters.com/r/resources?id=17
http://developer.mozilla.org/en/docs/AJAX:Getting_Started
https://ajax4jsf.dev.java.net/nonav/ajax/ajax-jsf/download.html
http://ajaxanywhere.sourceforge.net/
http://www.ajaxdna.com/

http://ajaxtags.sourceforge.net/quickstart.html
http://www.aptana.com/
https://blueprints.dev.java.net/ajax-faq.html
http://www-128.ibm.com/developerworks/views/web/libraryview.jsp?search_by=Mastering+Ajax
http://an9.org/ddq/
http://getahead.ltd.uk/dwr/
https://dwr.dev.java.net/
http://www.dynamicdrive.com/dynamicindex17/ajaxtabscontent/index.htm
http://dojo.jot.com/FAQ
http://www.fjax.net/
http://www.javapassion.com/ajaxcodecamp/#handsonlabdwr
https://bpcatalog.dev.java.net/nonav/ajax/jsf-ajax/frames.html
http://developer.iamalpha.com/dojo-intro
http://www.jamesdam.com/ajax_login/login.html
http://ajaxpatterns.org/Java_Ajax_Frameworks
http://www.firstpartners.net/red-piranha/knowledgebase/AjaxJavaLibraries
http://aspalliance.com/716
http://prototype.conio.net/
http://www.prototypedoc.com/
http://openrico.org/
https://swato.dev.java.net/
http://dojotoolkit.org/docs/

Sample Project Architecture...

project approch is different from project architecure. sorry here i can't insert my own project architecure diagram.

Client tier:

• IE Browser (default) from which the end user will access the application
• The request from the browser will be submitted to the Application Server using HTTP protocol.
• The Response from the presentation layer (struts framework) will be interpreted into html pages to view on the browsers.
• Presentation Tier:

Struts Framework with Tiles
• On Request from the browser, the appropriate Action Class handles the user request. The Action class then connects to the business tier via Service Business Delegate.
• Tiles have been used to create a set of pages with a consistent user interface (e.g.: the same navigation bar, header, footer, etc.).
• Taglibs are used for displaying tabular data (e.g. search results) in a consistent fashion, with pagination.
Business Delegate layer
• Enable the Struts Action classes to be unaware of underlying Session Beans
• Encapsulates the invocation of Service Locator to locate them.

Advantages of Struts
‘Centralized File-Based Configuration’, i.e. rather than hard-coding information into Java programs, many Struts values are represented in XML or property files.
This loose coupling means that many changes can be made without modifying or recompiling Java code.
Validation of the user entry fields in the jsps to be handled by entries in the validation.xml and defining validation rules in validator-rules.xml.
Internationalization of the static components of the screen as field and button labels, titles, error messages etc.
This approach also lets Java and Web developers to focus on their specific tasks (like implementing business logic, presenting certain values to clients.) without needing to know about the overall system layout.

Business Tier

• The Business Delegate identifies the business service class (the Session EJBs) and delegates client request to the EJBs. Internally, the session beans are shallow, and delegate all business logic requests to business logic POJOs, which in turn implement the actual functionality.
• The Business Logic POJOs encapsulate the server side business logic. They do not use Hibernate directly, but instead call upon Data Access Objects (DAO) to work with the model. Parameters and return values are modeled as Data Transfer Objects (DTO), and hence no Hibernate model classes will ever leave the DAO layer. The business logic is made available in the business service class, which increases maintainability and easy debugging, if necessary.

Hibernate/DB Tier
The DAOs encapsulates the database access. For all practical purposes, we are using Hibernate (v 2.1) as the OR mapping layer. This saves development time to write SQLs for executing insert and update statements, find by primary key etc. For each value object that directly or compositely represent a table in the database, we have Hibernate mapping files.
For some complex data retrieval, however we will be using raw SQLs (independent of database) from the DAOs and populate the Value Object POJOs. In those specific cases, the DAOs will be having direct access to the Databases using the available connection. The connection properties of the ‘DB Manager’, holding the data sources, direct the request to the appropriate database.

Issues that may rise of Hibernate
• Hibernate no longer supports dynamic proxies
• The Hibernate has issues using Microsoft's driver especially when using SqlServer2000. It appears that the failures are due to some strange handling of dates.
• Hibernate has issues with Informix Databases due to the way JDBC implementation is done in Informix.

keeps smiling and mailing

bora_srinivasarao@yahoo.co.in
Hyderabad

"HELP EVER HURT NEVER"&"IMPOSSIBLE AS POSSIBLE"

java : http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/DEA2eIX.html

Is Tomcat an app server?

Confusion over whether Tomcat is an application server tends to result in heated discussion among Java developers -- some claiming it absolutely is and some that it definitely is not. In truth, Tomcat often is used as an app server, and for some scenarios it is perfectly suited to that role. For developers using Tomcat as an application server, it makes sense to classify it as such, regardless of formal definition.

In this article I tackle the question of whether Tomcat is an application server. I start by explaining the distinctions between app servers, Web servers, and Java EE containers, and then look at some scenarios where a Web server like Tomcat could be used appropriately as an app server. I show a scaled architecture, starting with the sort of lightweight implementation where Tomcat shines, and concluding with a complex service-oriented architecture, where you would be better off with a full-fledged Java EE application server...

What is the Differnence b/w Application Server and Web Server?

"App server, Web server: What's the difference?" Java Q&A author Tony Sintes summarized the distinction as follows:

"A Web server exclusively handles HTTP requests, whereas an application server serves business logic to application programs through any number of protocols, including HTTP [...] While a Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object (or a function in the procedural world).

Such application server clients can include GUIs (graphical user interface) running on a PC, a Web server, or even other application servers. The information traveling back and forth between an application server and its client is not restricted to simple display markup. Instead, the information is program logic. Since the logic takes the form of data and method calls and not static HTML, the client can employ the exposed business logic however it wants.

In most cases, the server exposes this business logic through a component API, such as the EJB component model found on J2EE application servers. Moreover, the application server manages its own resources. Such gate-keeping duties include security, transaction processing, resource pooling, and messaging. Like a Web server, an application server may also employ various scalability and fault-tolerance techniques."