Does this sound a familiar question! You too may have a similar question in your mind. Don’t worry, This article explains what are all the skills that you will need to be a Java web developer, and what are the skills that you are expected to have when you appear for an interview for a Java/J2EE web developer.

Read the full article I want to be a java developer

1. Web framework pluggability
2. Annotation
3. Built in File upload support
4. Modularization of of deployment descriptor web.xml
5. Asynchronous servlets and comet support

See Introduction to Servlet 3.0 new features

I feel that this post deservers some diggs, However  it’s a russian domain, I can not post it to digg, So I wrote this post. All the credit goes to the author.

Post your comments here.

That’s it !. All the files and subdirectories are excluded from resource list.

Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way.

As the first web framework dedicated to JSR-170 Java Content Repositories, Sling makes it very simple to implement simple applications, while providing an enterprise-level framework for more complex applications.

Bertrand Delacretaz and David Nuescheler created a sample site like TSS in Sling in 10 minutes, live on stage at the Jazoon conference. You See the sample here

Bertrand Delacretaz has written a tutorial which helps in getting started with the sling launchpad. the tutorial explains how to:

1. get the launchpad
2. build the launchpad
3. start the launchpad
4. create some content
5. Render content using server-side java script

And some addition examples of how to create the node with uniqueue path,  add page header with sling.include

there are good tutorials on dev.day.com also

I have heard an employee of day software saying that dev.day.com is built on sling

Sling presentation

If you use paint, than you may know, how frustrating it is, like capture the screen with Print Screen, go to paint and paste, remove the unwanted portions, the list goes on…..

Why SnagIt?

• Easily capture the regions of the screen.
• Capture a window.
• Capture a scrolling window or webpage (How will you do this with paint?)
• Record the screen video.
• Easily outline interested area with various shapes like circles, elipse, square etc.
• Use callouts like arrows, ballons.
• Easy to learn and use.

There are lots of other cool features that I don’t know yet. You can see some of the example screen shots here.

If you need to take screen shots frequently and you use paint for it than I will strongly recommend SnagIt. You can download a trial version of the software from here

Samples

But if you are impatience go here

The intention is to deliver this JSR as a component of Java SE 7.

JSR 294 plan to extend the Java programming language with new constructs called “superpackages” that allow hierarchical modular organizatio.

Each superpackage is a collection of one or more packages or superpackages, which helps to organize large programs consisting of many packages. Related packages that are grouped into a superpackage can access each others’ public
types, while unrelated packages outside the superpackage cannot access those types, unless the types are exported

Example declaration

superpackage A {
member package P;
member superpackage B;
}
superpackage B member A {
member superpackage C;
export superpackage C;
}
superpackage C member B {
member package Q;
export Q.X;
}

Find out more about JSR 294 Here and Here

JSR 308 proposes an extension to Java’s annotation system that permits annotations to appear on any use of a type. (By contrast, Java SE 6 permits annotations to appear only on class/method/field/variable declarations; JSR 308 is backward-compatible and continues to permit those annotations.) Such a generalization removes arbitrary limitations of Java’s annotation system, and it enables new uses of annotations. This proposal also notes a few other possible extensions to annotations

Example

@NonNullDefault
class DAG {
Set<Edge> edges;
List<Vertex> getNeighbors(@Interned @Readonly Vertex v) @Readonly {
List<Vertex> neighbors = new LinkedList<Vertex>();
for (Edge e : edges)
if (e.from() == v)
neighbors.add(e.to());
return neighbors;
}
}

Find out more about JSR 308 here

1) create a folder ‘links’ under eclipse home folder.
2) create a file plugins.link under this folder.
This file can have any name as far as extension is .link, you can create multiple link file for different plugins.
3) edit the link file and put the path of custom plugins folder
example path=D:/customplugins ( use forward slash only).
This custom plugin folder should reflect eclipse plugins directory structure.
create a ecliplse folder within customplugin folder.
create two folders features, and plugins under eclipse folder.

Now you are ready to install plugins in that custom location.
You can repeat this steps to install different plugins in different folders. it will help you when you want to remove/reinstall a particular plugin.