The Struts 2.0 Architecture

Struts 2.0 ... is it the Holy Grail of Frameworks???

A sneak peek into whats new in Struts 2.0 will show what new this has to offer.....

Action classes ( So ure a man of Action eh? )

An Struts 2 Action may implement an Action interface, along with other interfaces to enable optional and custom services. Struts 2 provides a base ActionSupport class to implement commonly used interfaces. Albeit, the Action interface is not required. Any POJO object with a execute signature can be used as an Struts 2 Action object.

Threading Model ( Who said it was meant only for the ladies?)

Struts 2 Action objects are instantiated for each request, so there are no thread-safety issues. (In practice, servlet containers generate many throw-away objects per request, and one more object does not impose a performance penalty or impact garbage collection.)

Testability ( Here's where we all fail , don't we )

Struts 2 Actions can be tested by instantiating the Action, setting properties, and invoking methods. Dependency Injection support also makes testing simpler.

Servlet Dependency ( what dependency ??!! )

Struts 2 Actions are not coupled to a container. Most often the servlet contexts are represented as simple Maps, allowing Actions to be tested in isolation. Struts 2 Actions can still access the original request and response, if required. However, other architectural elements reduce or eliminate the need to access the HttpServetRequest or HttpServletResponse directly.

Harvesting Input ( Ahh reap time to reap the rewards )

Struts 2 uses Action properties as input properties, eliminating the need for a second input object. Input properties may be rich object types which may have their own properties. The Action properties can can be accessed from the web page via the taglibs. Struts 2 also supports the ActionForm pattern, as well as POJO form objects and POJO Actions. Rich object types, including business or domain objects, can be used as input/output objects. The ModelDriven feature simplifies taglb references to POJO input objects.

Expression Language ( Wannabe Lovers , take note )

Struts 2 can use JSTL, but the framework also supports a more powerful and flexible expression language called "Object Graph Notation Language" (OGNL).

Binding values into views ( Did somebody complain of degrading values )

Struts 2 uses a "ValueStack" technology so that the taglibs can access values without coupling your view to the object type it is rendering. The ValueStack strategy allows reuse of views across a range of types which may have the same property name but different property types.

Type Conversion ( "You're not my type !!")

Struts 2 uses OGNL for type conversion. The framework includes converters for basic and common object types and primitives.

Validation ( So you think you're smart eh? Pass this )

Struts 2 supports manual validation via the validate method and the XWork Validation framework. The Xwork Validation Framework supports chaining validation into sub-properties using the validations defined for the properties class type and the validation context.

Control Of Action Execution ( Phew! Finally somebody's in charge )

Struts 2 supports creating different lifecycles on a per Action basis via Interceptor Stacks. Custom stacks can be created and used with different Actions, as needed.

Gung ho with AJAX!!!

Okay lets get down to the nuts and bolts of it..... lets start by creating an AJAX application rightaway. Well what does it require ....some Javascript and XML.

Okay lets pick a piece of code from the W3 site.
http://www.w3schools.com/ajax/ajax_browsers.asp

What we clearly see is javascript in action . So before we delve into the script lets understand
some tech specs :)

Browser specs:

The Internet Explorer uses an ActiveX object while all other browsers use
XMLHttpRequest which is in built in the javascript object.

Alright !!! I have a Legacy.

Alright guys ..have u had enuf of obscure literature in the garb of tutorials. This is the place to be. Here i will upload cutting edge Java tutorials. Publishers please excuse.Although no attempt has been made to plagiarise , proper reference will be given wherever relevant.

So without any waste of time lets start from the basics .What better way to start than the fundamentals of web. I know this can be viewed by many as upsetting the applecart. Many developers like to skip this section , but from my experience one can only ignore this to his peril. Right now is good time to get started.

World Wide Web

Well to cut a long story short HTTP and HTML is what is the holy grail of the internet. Once real buzz words these words have now become almost a regular in every web developers dictionary.Simply put HTML is the language and HTTP is the protocol through which this information travels.Lets leave it at that right now . We will get back to it if time permits.Right now we have a bigger fish to fry ;)

For HTTP primer u can check out this link:
http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/HTTP.html/