As part of our Java Tutorials program, we will list a number of interview questions to aid in a better understaing of Java and J2EE and, hopefully, provide a greater likelihood of getting a job.  Let us begin with the basics:

1. What is meant by J2EE?

J2EE is an abreviation for Java 2 Platform Enterprise Edition

2.  What is the purpose of J2EE?

The purpose of J2EE is to provide a component based platform in a multitier application model with transaction management, web services and reusable component support.

3.  What is the tier structure of the typical J2EE application?

A typical J2EE application consists of the following tiers/machines:  the client machine (browser/non-browser application), the J2EE server (an application server such as Oracle, JBoss, GlassFish, Tomcat) and a database.

 Unlike traditional online courses that charge a fee, limit enrollment and provide credit or certification, Moocs (massive open online courses) are usually free or low cost and can host hundreds of  thousands global participants.  Although MOOC have been around for years in the form of collective techie learning gatherings, participation in 2012 has ballooned at a rapid pace likened to FaceBook in its heyday.  According to The Year of the MOOCarticle in the New YorkTimes, edX, a nonprofit start-up backed by Harvard and MIT, had 370,000 registrants in the fall of its first official courses. This paled in comparison to the amount of students that Courseraattained in its first year of online learning opportunities, 1.7 million!

Will MOOCs Replace education as we know it?

Like any new trend, massive participation in online classes has its challenges. Lynda Weinman has ample experience when pointing out that they are by no means a replacement for formal education.  As a former digital animator, special effects designer and classroom college teacher, Linda paved the path for an earlier version of MOOC education in the mid 90’s when she founded Lynda.comas an aide to her own students. Over four million students and 2,200 courses later she’s confident when clarifying that many of the collegespartnered with Lynda.com use the tutorials as added features to their existing courses.  When asked in an interview with ReadWriteBuilders, if high technical companies look at online programs in terms of advancement as a supplement to traditional education or as a way for people to further their careers, Lynda feels that “it’sjust one example of something that you can do to enhance your attractiveness to potential employers. But [it’s also important to have] a portfolio and body of work, references that actually work out, showing that you had success in the past.”

MOOC Benefits:

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

Python and Ruby, each with roots going back into the 1990s, are two of the most popular interpreted programming languages today. Ruby is most widely known as the language in which the ubiquitous Ruby on Rails web application framework is written, but it also has legions of fans that use it for things that have nothing to do with the web. Python is a big hit in the numerical and scientific computing communities at the present time, rapidly displacing such longtime stalwarts as R when it comes to these applications. It too, however, is also put to a myriad of other uses, and the two languages probably vie for the title when it comes to how flexible their users find them.

A Matter of Personality...

That isn't to say that there aren't some major, immediately noticeable, differences between the two programming tongues. Ruby is famous for its flexibility and eagerness to please; it is seen by many as a cleaned-up continuation of Perl's "Do What I Mean" philosophy, whereby the interpreter does its best to figure out the meaning of evening non-canonical syntactic constructs. In fact, the language's creator, Yukihiro Matsumoto, chose his brainchild's name in homage to that earlier language's gemstone-inspired moniker.

Python, on the other hand, takes a very different tact. In a famous Python Enhancement Proposal called "The Zen of Python," longtime Pythonista Tim Peters declared it to be preferable that there should only be a single obvious way to do anything. Python enthusiasts and programmers, then, generally prize unanimity of style over syntactic flexibility compared to those who choose Ruby, and this shows in the code they create. Even Python's whitespace-sensitive parsing has a feel of lending clarity through syntactical enforcement that is very much at odds with the much fuzzier style of typical Ruby code.

For example, Python's much-admired list comprehension feature serves as the most obvious way to build up certain kinds of lists according to initial conditions:

a = [x**3 for x in range(10,20)]
b = [y for y in a if y % 2 == 0]

first builds up a list of the cubes of all of the numbers between 10 and 19 (yes, 19), assigning the result to 'a'. A second list of those elements in 'a' which are even is then stored in 'b'. One natural way to do this in Ruby is probably:

a = (10..19).map {|x| x ** 3}
b = a.select {|y| y.even?}

but there are a number of obvious alternatives, such as:

a = (10..19).collect do |x|
x ** 3
end

b = a.find_all do |y|
y % 2 == 0
end

It tends to be a little easier to come up with equally viable, but syntactically distinct, solutions in Ruby compared to Python, even for relatively simple tasks like the above. That is not to say that Ruby is a messy language, either; it is merely that it is somewhat freer and more forgiving than Python is, and many consider Python's relative purity in this regard a real advantage when it comes to writing clear, easily understandable code.

And Somewhat One of Performance