Explore topic-wise InterviewSolutions in Current Affairs.

If you are starting from scratch, packages like Turbine and Espresso can be very helpful since they TRY to provide all of the basic services that your team is likely to need. Such services include things like data persistence and logging. 

If you are not starting from scratch, and need to hook up your web APPLICATION to an existing infrastructure, then "plain vanilla" Struts can be a better choice. The CORE Struts framework does not presuppose that you are using a given set of data persistence, presentation, or logging tools. Anything goes =:0) 

Compared to other offerings, Struts endeavors to be a minimalist framework. We try leverage existing TECHNOLOGIES whenever we can and provide only the missing pieces you need to combine disparate technologies into a COHERENT application. This is great when you want to select your own tools to use with Struts. But, if you prefer a more integrated infrastructure, then packages like Turbine or Espresso (which uses Struts) are perfectly good ways to go.

See also

* < http://www.mail-archive.com/struts-user@jakarta.apache.org/msg03206.html >
* < http://www.mail-archive.com/general@jakarta.apache.org/msg00495.html >
* < http://jakarta.apache.org/velocity/ymtd/ymtd.html >

If you are starting from scratch, packages like Turbine and Espresso can be very helpful since they try to provide all of the basic services that your team is likely to need. Such services include things like data persistence and logging. 

If you are not starting from scratch, and need to hook up your web application to an existing infrastructure, then "plain vanilla" Struts can be a better choice. The core Struts framework does not presuppose that you are using a given set of data persistence, presentation, or logging tools. Anything goes =:0) 

Compared to other offerings, Struts endeavors to be a minimalist framework. We try leverage existing technologies whenever we can and provide only the missing pieces you need to combine disparate technologies into a coherent application. This is great when you want to select your own tools to use with Struts. But, if you prefer a more integrated infrastructure, then packages like Turbine or Espresso (which uses Struts) are perfectly good ways to go.

See also

* < http://www.mail-archive.com/struts-user@jakarta.apache.org/msg03206.html >
* < http://www.mail-archive.com/general@jakarta.apache.org/msg00495.html >
* < http://jakarta.apache.org/velocity/ymtd/ymtd.html >

The Struts package comes complete with a Users Guide to introduce people to the framework and its underlying technologies. Various components also have their own in-depth Developers Guide, to cover more advanced topics. COMPREHENSIVE Javadocs are included along with the full source code. For your convenience, these are bundled together as a self-installing application. The struts-documentation.war is the same bundle that is deployed as the Struts Web SITE.

The STRUT's mailing list is also very active, and welcomes posts from new users. Before posting a new QUESTION, be sure to consult the MAILING LIST ARCHIVE and the very excellent How To Ask Questions The Smart Way by Eric Raymond. Please do be sure to turn off HTML in your email client before posting.

The Struts package comes complete with a Users Guide to introduce people to the framework and its underlying technologies. Various components also have their own in-depth Developers Guide, to cover more advanced topics. Comprehensive Javadocs are included along with the full source code. For your convenience, these are bundled together as a self-installing application. The struts-documentation.war is the same bundle that is deployed as the Struts Web site.

The Strut's mailing list is also very active, and welcomes posts from new users. Before posting a new question, be sure to consult the MAILING LIST ARCHIVE and the very excellent How To Ask Questions The Smart Way by Eric Raymond. Please do be sure to turn off HTML in your email client before posting.

First, it's important to remember that Struts is an all-volunteer project. We don't charge anyone anything to use Struts. Committers and other developers work on Struts because they need to use it with their own applications. If others can use it too, that's "icing on the cake". If you submit a patch for a FEATURE that a Committer finds useful, then that Committer may choose to volunteer his or her time to apply the patch. If you just submit an idea WITHOUT a patch, it is much less likely to be ADDED (since first someone else has to volunteer their time to write the patch). 

We are grateful for any patches, and we welcome new ideas, but the best WAY to see that something gets added to the framework is to do as much of the work as you can, rather than rely on the "kindness of strangers". WORST case, you can apply the patch to your copy of Struts and still use the feature in your own application. (Which is what open source is really all about.)

First, it's important to remember that Struts is an all-volunteer project. We don't charge anyone anything to use Struts. Committers and other developers work on Struts because they need to use it with their own applications. If others can use it too, that's "icing on the cake". If you submit a patch for a feature that a Committer finds useful, then that Committer may choose to volunteer his or her time to apply the patch. If you just submit an idea without a patch, it is much less likely to be added (since first someone else has to volunteer their time to write the patch). 

We are grateful for any patches, and we welcome new ideas, but the best way to see that something gets added to the framework is to do as much of the work as you can, rather than rely on the "kindness of strangers". Worst case, you can apply the patch to your copy of Struts and still use the feature in your own application. (Which is what open source is really all about.)

Struts currently has two testing environments, to reflect the fact that some things can be tested statically, and some really need to be done in the ENVIRONMENT of a running servlet container.

For static unit tests, we USE the JUnit FRAMEWORK. The sources for these tests are in the "src/test" HIERARCHY in the source repository, and are executed via the "test.junit" target in the top-level build.xml file. Such tests are focused on the low-level functionality of individual methods, are particularly suitable for the static methods in the org.apache.struts.util utility classes. In the test hierarchy, there are also some "mock object" classes (in the org.apache.struts.mock PACKAGE) so that you can package up things that look like servlet API and Struts API objects to pass in as arguments to such tests.

Another valuable tool is Struts TestCase which provides a useful harness for Action classes that can be used with JUnit or Cactus.

Struts currently has two testing environments, to reflect the fact that some things can be tested statically, and some really need to be done in the environment of a running servlet container.

For static unit tests, we use the JUnit framework. The sources for these tests are in the "src/test" hierarchy in the source repository, and are executed via the "test.junit" target in the top-level build.xml file. Such tests are focused on the low-level functionality of individual methods, are particularly suitable for the static methods in the org.apache.struts.util utility classes. In the test hierarchy, there are also some "mock object" classes (in the org.apache.struts.mock package) so that you can package up things that look like servlet API and Struts API objects to pass in as arguments to such tests.

Another valuable tool is Struts TestCase which provides a useful harness for Action classes that can be used with JUnit or Cactus.

When you are compiling an application that uses the Struts classes, you must have the "struts.jar" on the classpath your COMPILER sees -- it does not have to be on your CLASSPATH environment variable. 

Why is that an important distinction? Because if you are using a servlet container on your development machine to test your application, the "struts.jar" must not be on your CLASSPATH environment variable when running the container. (This is because each WEB application must also have their own copy of the Struts classes, and the container will become confused if it is on the environment path as well.) 

There are several general APPROACHES to this issue: 

* Use ANT for building your projects -- it can easily assemble classpaths for the compiler. (This is how Struts itself is BUILT, along with TOMCAT and most other Java-based projects).
* Use an IDE where you can configure the "class path" used for compilation independent of the CLASSPATH environment variable.
* Use a shell script that temporarily adds struts.jar to the classpath just for compilation, for example javac -classpath /path/to/struts.jar:$CLASSPATH $@

When you are compiling an application that uses the Struts classes, you must have the "struts.jar" on the classpath your compiler sees -- it does not have to be on your CLASSPATH environment variable. 

Why is that an important distinction? Because if you are using a servlet container on your development machine to test your application, the "struts.jar" must not be on your CLASSPATH environment variable when running the container. (This is because each Web application must also have their own copy of the Struts classes, and the container will become confused if it is on the environment path as well.) 

There are several general approaches to this issue: 

* Use ANT for building your projects -- it can easily assemble classpaths for the compiler. (This is how Struts itself is built, along with Tomcat and most other Java-based projects).
* Use an IDE where you can configure the "class path" used for compilation independent of the CLASSPATH environment variable.
* Use a shell script that temporarily adds struts.jar to the classpath just for compilation, for example javac -classpath /path/to/struts.jar:$CLASSPATH $@

To develop applications with Struts, you can usually just add the Struts JAR FILE to your Java development environment. You can then start using the Struts classes as part of your own application. A blank Struts application (in the webapps directory, open struts-blank.war) is provided, which you can just copy to GET a quick-start on your own brainchild. 

SINCE the full source code for Struts is available, we also PROVIDE complete INSTRUCTIONS for compiling your own Struts JAR from scratch. (This is actually easier than it looks!) 

Your Struts application can usually be deployed using a standard WAR file. In most cases, you simply deposit the WAR file on your application server, and it is installed automatically. If not, step-by-step installation instructions for various servlet containers are available.

To develop applications with Struts, you can usually just add the Struts JAR file to your Java development environment. You can then start using the Struts classes as part of your own application. A blank Struts application (in the webapps directory, open struts-blank.war) is provided, which you can just copy to get a quick-start on your own brainchild. 

Since the full source code for Struts is available, we also provide complete instructions for compiling your own Struts JAR from scratch. (This is actually easier than it looks!) 

Your Struts application can usually be deployed using a standard WAR file. In most cases, you simply deposit the WAR file on your application server, and it is installed automatically. If not, step-by-step installation instructions for various servlet containers are available.

The BEST place to download STRUTS is at struts.apache.org. The NIGHTLY builds are very STABLE, and recommended as the best place to start today.

The best place to download Struts is at struts.apache.org. The nightly builds are very stable, and recommended as the best place to start today.

You need to CREDIT Struts if you REDISTRIBUTE your own framework based on Struts for other people to USE. (See the Apache LICENSE for details.) But you do not need to credit Struts just because your web application utilizes the framework. It's the same situation as using the Apache HTTPD server or Tomcat. Not required if its just running your web site.

You need to credit Struts if you redistribute your own framework based on Struts for other people to use. (See the Apache License for details.) But you do not need to credit Struts just because your web application utilizes the framework. It's the same situation as using the Apache HTTPD server or Tomcat. Not required if its just running your web site.

It's a reference to struts in the architectural sense, a reminder of the NEARLY invisible PIECES that hold up BUILDINGS, houses, and bridges.

It's a reference to struts in the architectural sense, a reminder of the nearly invisible pieces that hold up buildings, houses, and bridges.

There are several active committers to the Struts project, working cooperatively from around the globe. Dozens of individual developers and committers contributed to the Struts 1.x codebase. All interested Java developers are invited to contribute to the project. Struts is a APACHE Software Foundation project, with the mission to "provide secure, enterprise-grade server solutions based on the Java Platform that are developed in an open and cooperative fashion". 

Struts was created by CRAIG R. McClanahan and donated to The Apache Software Foundation in May 2000. Craig was the primary developer of both Struts 1.x and Tomcat 4. Tomcat 4 was the basis for the official reference implementation for a servlet 2.3 and JSP 1.2 container. 

Craig's current FOCUS is as architect of the Sun Java Studio Creator (formerly Project Rave). Craig also serves as the Specification Lead for JavaServer Faces (JSR-127), and is the Web Layer Architect for the Java2 Enterprise Edition (J2EE) platform as a whole. 

There are several active committers to the Struts project, working cooperatively from around the globe. Dozens of individual developers and committers contributed to the Struts 1.x codebase. All interested Java developers are invited to contribute to the project. Struts is a Apache Software Foundation project, with the mission to "provide secure, enterprise-grade server solutions based on the Java Platform that are developed in an open and cooperative fashion". 

Struts was created by Craig R. McClanahan and donated to The Apache Software Foundation in May 2000. Craig was the primary developer of both Struts 1.x and Tomcat 4. Tomcat 4 was the basis for the official reference implementation for a servlet 2.3 and JSP 1.2 container. 

Craig's current focus is as architect of the Sun Java Studio Creator (formerly Project Rave). Craig also serves as the Specification Lead for JavaServer Faces (JSR-127), and is the Web Layer Architect for the Java2 Enterprise Edition (J2EE) platform as a whole. 

YES. STRUTS is COMMITTED to supporting INDUSTRY standards. Struts acts as an INTEGRATOR of Java technologies so that they can be used in the "real world".

Yes. Struts is committed to supporting industry standards. Struts acts as an integrator of Java technologies so that they can be used in the "real world".

Java Servlets are designed to handle requests made by Web browsers. Java ServerPages are designed to CREATE dynamic Web pages that can turn billboard SITES into LIVE APPLICATIONS. Struts uses a special Servlet as a switchboard to route requests from Web browsers to the appropriate ServerPage. This makes Web applications much easier to design, create, and maintain.

Java Servlets are designed to handle requests made by Web browsers. Java ServerPages are designed to create dynamic Web pages that can turn billboard sites into live applications. Struts uses a special Servlet as a switchboard to route requests from Web browsers to the appropriate ServerPage. This makes Web applications much easier to design, create, and maintain.

Java technologies give developers a serious boost when creating and maintaining applications to meet the demands of today's public Web SITES and ENTERPRISE intranets. Struts combines Java Servlets, Java ServerPages, custom tags, and message resources into a UNIFIED framework. The end result is a cooperative, synergistic platform, suitable for development TEAMS, independent developers, and everyone in between.

Java technologies give developers a serious boost when creating and maintaining applications to meet the demands of today's public Web sites and enterprise intranets. Struts combines Java Servlets, Java ServerPages, custom tags, and message resources into a unified framework. The end result is a cooperative, synergistic platform, suitable for development teams, independent developers, and everyone in between.

The Validator FRAMEWORK uses two XML configuration files validator-rules.xml and validation.xml. The validator-rules.xml DEFINES the standard validation routines, these are reusable and used in validation.xml. to define the FORM specific validations. The validation.xml defines the validations applied to a form bean. How you will display validation FAIL errors on jsp page? - The following tag displays all the errors: < html:errors/ >

The Validator Framework uses two XML configuration files validator-rules.xml and validation.xml. The validator-rules.xml defines the standard validation routines, these are reusable and used in validation.xml. to define the form specific validations. The validation.xml defines the validations applied to a form bean. How you will display validation fail errors on jsp page? - The following tag displays all the errors: < html:errors/ >

STRUTS Framework provides the functionality to validate the form data. It can be USE to validate the data on the users browser as well as on the server side. Struts Framework emits the java scripts and it can be used validate the form data on the CLIENT browser. Server side validation of form can be ACCOMPLISHED by sub classing your From BEAN with DynaValidatorForm class. The Validator framework was developed by David Winterfeldt as third-party add-on to Struts. Now the Validator framework is a part of Jakarta Commons project and it can be used with or without Struts. The Validator framework comes integrated with the Struts Framework and can be used without doing any extra settings.

Struts Framework provides the functionality to validate the form data. It can be use to validate the data on the users browser as well as on the server side. Struts Framework emits the java scripts and it can be used validate the form data on the client browser. Server side validation of form can be accomplished by sub classing your From Bean with DynaValidatorForm class. The Validator framework was developed by David Winterfeldt as third-party add-on to Struts. Now the Validator framework is a part of Jakarta Commons project and it can be used with or without Struts. The Validator framework comes integrated with the Struts Framework and can be used without doing any extra settings.

An ActionForm is a JavaBean that EXTENDS org.apache.struts.action.ActionForm. ActionForm maintains the session state for web application and the ActionForm object is AUTOMATICALLY populated on the server SIDE with data ENTERED from a form on the client side.

An ActionForm is a JavaBean that extends org.apache.struts.action.ActionForm. ActionForm maintains the session state for web application and the ActionForm object is automatically populated on the server side with data entered from a form on the client side.

Here is the CODE of Action CLASS that returns the ActionForward object. 
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.apache.struts.action.Action;
import org.apache.struts.action.ActionForm;
import org.apache.struts.action.ActionForward;
import org.apache.struts.action.ACTIONMAPPING; 
public class TestAction extends Action
{
public ActionForward execute(
ActionMapping mapping,
ActionForm form,
HttpServletRequest REQUEST,
HttpServletResponse RESPONSE) throws Exception
{
return mapping.findForward(\"testAction\");
}
}

Here is the code of Action Class that returns the ActionForward object. 
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.apache.struts.action.Action;
import org.apache.struts.action.ActionForm;
import org.apache.struts.action.ActionForward;
import org.apache.struts.action.ActionMapping; 
public class TestAction extends Action
{
public ActionForward execute(
ActionMapping mapping,
ActionForm form,
HttpServletRequest request,
HttpServletResponse response) throws Exception
{
return mapping.findForward(\"testAction\");
}
}

The Action Class is part of the Model and is a wrapper around the business logic. The PURPOSE of Action Class is to translate the HttpServletRequest to the business logic. To use the Action, we need to Subclass and overwrite the execute() method. In the Action Class all the DATABASE/business processing are done. It is advisable to perform all the database RELATED stuffs in the Action Class. The ActionServlet (commad) passes the parameterized class to Action Form using the execute() method. The return type of the execute method is ActionForward which is used by the Struts Framework to forward the request to the file as PER the value of the returned ActionForward OBJECT.

The Action Class is part of the Model and is a wrapper around the business logic. The purpose of Action Class is to translate the HttpServletRequest to the business logic. To use the Action, we need to Subclass and overwrite the execute() method. In the Action Class all the database/business processing are done. It is advisable to perform all the database related stuffs in the Action Class. The ActionServlet (commad) passes the parameterized class to Action Form using the execute() method. The return type of the execute method is ActionForward which is used by the Struts Framework to forward the request to the file as per the value of the returned ActionForward object.

MESSAGE Resources Definitions file are simple .properties FILES and these files contains the messages that can be used in the struts project. Message Resources Definitions files can be added to the struts-config.xml file through < message-resources / > TAG. Example: < message-resources PARAMETER= MessageResources / >

Message Resources Definitions file are simple .properties files and these files contains the messages that can be used in the struts project. Message Resources Definitions files can be added to the struts-config.xml file through < message-resources / > tag. Example: < message-resources parameter= MessageResources / >

The CLASS org.apache.STRUTS.action.ActionServlet is the called the ActionServlet. In the the Jakarta Struts Framework this class PLAYS the role of controller. All the REQUESTS to the server goes through the controller. Controller is responsible for HANDLING all the requests.

The class org.apache.struts.action.ActionServlet is the called the ActionServlet. In the the Jakarta Struts Framework this class plays the role of controller. All the requests to the server goes through the controller. Controller is responsible for handling all the requests.

The < HTML:javascript &GT; tag to allow front-end validation based on the xml in validation.xml. For example the CODE: < html:javascript formName=logonForm dynamicJavascript=true staticJavascript=true / > generates the client side java script for the form logonForm as defined in the validation.xml file. The < html:javascript > when added in the jsp file generates the client SITE validation script.

The < html:javascript > tag to allow front-end validation based on the xml in validation.xml. For example the code: < html:javascript formName=logonForm dynamicJavascript=true staticJavascript=true / > generates the client side java script for the form logonForm as defined in the validation.xml file. The < html:javascript > when added in the jsp file generates the client site validation script.

The Struts is not only thread-safe but thread-dependent(instantiates each Action once and allows other requests to be threaded through the original object.
ActionForm beans minimize subclass code and shorten subclass hierarchies.
The Struts tag libraries provide general-purpose functionality.
The Struts components are reusable by the application.
The Struts localization strategies reduce the need for redundant JSPS.
The Struts is designed with an OPEN architecture--subclass AVAILABLE.
The Struts is LIGHTWEIGHT (5 core PACKAGES, 5 tag libraries).
The Struts is open source and well documented (code to be examined easily).
The Struts is model neutral.

The Struts is not only thread-safe but thread-dependent(instantiates each Action once and allows other requests to be threaded through the original object.
ActionForm beans minimize subclass code and shorten subclass hierarchies.
The Struts tag libraries provide general-purpose functionality.
The Struts components are reusable by the application.
The Struts localization strategies reduce the need for redundant JSPs.
The Struts is designed with an open architecture--subclass available.
The Struts is lightweight (5 core packages, 5 tag libraries).
The Struts is open source and well documented (code to be examined easily).
The Struts is model neutral.

--struts-html.tld
--struts-bean.tld
--struts-logic.tld

--struts-html.tld
--struts-bean.tld
--struts-logic.tld

ApplicationResources.properties
struts-config.xml
These TWO files are USED to BRIDGE the GAP between the Controller and the MODEL.

ApplicationResources.properties
struts-config.xml
These two files are used to bridge the gap between the Controller and the Model.

STRUTS implements the MVC/Layers pattern through the USE of ActionForwards and ActionMappings to KEEP control-flow DECISIONS out of presentation layer.

Struts implements the MVC/Layers pattern through the use of ActionForwards and ActionMappings to keep control-flow decisions out of presentation layer.

The role played by Structs is controller in Model/View/Controller(MVC) style. The View is played by JSP and Model is played by JDBC or generic data source classes. The Struts controller is a set of programmable components that ALLOW developers to DEFINE exactly how the application interacts with the user.

The role played by Structs is controller in Model/View/Controller(MVC) style. The View is played by JSP and Model is played by JDBC or generic data source classes. The Struts controller is a set of programmable components that allow developers to define exactly how the application interacts with the user.

Action, ACTIONFORM, ACTIONSERVLET, ACTIONMAPPING, ActionForward are BASIC classes of Structs.

Action, ActionForm, ActionServlet, ActionMapping, ActionForward are basic classes of Structs.

No. STRUTS is AVAILABLE for commercial use at no charge under the APACHE Software License. You can also integrate the Struts components into your own framework just as if they were WRITTEN in house without any RED tape, fees, or other hassles.

No. Struts is available for commercial use at no charge under the Apache Software License. You can also integrate the Struts components into your own framework just as if they were written in house without any red tape, fees, or other hassles.

Because the designers want to remind US of the invisible UNDERPINNINGS that hold up our houses, buildings, BRIDGES, and ourselves when we are on stilts. This excellent description of Struts REFLECT the role the Struts plays in DEVELOPING web applications.

Because the designers want to remind us of the invisible underpinnings that hold up our houses, buildings, bridges, and ourselves when we are on stilts. This excellent description of Struts reflect the role the Struts plays in developing web applications.

Struts is HOSTED by the Apache SOFTWARE Foundation(ASF) as part of its Jakarta project, like Tomcat, Ant and Velocity.

Struts is hosted by the Apache Software Foundation(ASF) as part of its Jakarta project, like Tomcat, Ant and Velocity.

In the MVC design pattern, APPLICATION flow is mediated by a central Controller. The Controller delegates requests to an APPROPRIATE handler. The handlers are tied to a Model, and each handler acts as an adapter between the request and the Model. The Model represents, or encapsulates, an application's business logic or state. Control is usually then forwarded back through the Controller to the appropriate View. The forwarding can be determined by consulting a set of mappings, usually loaded from a database or configuration file. This provides a loose coupling between the View and Model, which can make an application significantly easier to create and MAINTAIN. Controller--Servlet controller which supplied by Struts itself; View --- what you can see on the screen, a JSP page and presentation COMPONENTS; Model --- System state and a business logic JavaBeans.

In the MVC design pattern, application flow is mediated by a central Controller. The Controller delegates requests to an appropriate handler. The handlers are tied to a Model, and each handler acts as an adapter between the request and the Model. The Model represents, or encapsulates, an application's business logic or state. Control is usually then forwarded back through the Controller to the appropriate View. The forwarding can be determined by consulting a set of mappings, usually loaded from a database or configuration file. This provides a loose coupling between the View and Model, which can make an application significantly easier to create and maintain. Controller--Servlet controller which supplied by Struts itself; View --- what you can see on the screen, a JSP page and presentation components; Model --- System state and a business logic JavaBeans.

Struts is a WEB page development framework and an open source software that helps developers build web applications quickly and easily. Struts combines Java Servlets, Java Server Pages, custom TAGS, and message RESOURCES into a UNIFIED framework. It is a cooperative, synergistic platform, suitable for development teams, independent developers, and EVERYONE between.

Struts is a web page development framework and an open source software that helps developers build web applications quickly and easily. Struts combines Java Servlets, Java Server Pages, custom tags, and message resources into a unified framework. It is a cooperative, synergistic platform, suitable for development teams, independent developers, and everyone between.

JFC supports robust and portable user interfaces. The Swing classes are robust, compatible with AWT, and provide you with a great deal of CONTROL over a user interface. Since source code is available, it is relatively easy to extend the JFC to do exactly what you need it to do. But the number of third-party controls WRITTEN for Swing is still relatively small.
WFC RUNS only on the Windows (32-bit) user interface, and uses Microsoft extensions to Java for event handling and ActiveX integration. Because ActiveX components are available to WFC programs, there are theoretically more controls available for WFC than for JFC. In practice, however, most ActiveX vendors do not actively SUPPORT WFC, so the number of controls available for WFC is probably smaller than for JFC. The WFC programming model is closely aligned with the Windows platform.

JFC supports robust and portable user interfaces. The Swing classes are robust, compatible with AWT, and provide you with a great deal of control over a user interface. Since source code is available, it is relatively easy to extend the JFC to do exactly what you need it to do. But the number of third-party controls written for Swing is still relatively small.
WFC runs only on the Windows (32-bit) user interface, and uses Microsoft extensions to Java for event handling and ActiveX integration. Because ActiveX components are available to WFC programs, there are theoretically more controls available for WFC than for JFC. In practice, however, most ActiveX vendors do not actively support WFC, so the number of controls available for WFC is probably smaller than for JFC. The WFC programming model is closely aligned with the Windows platform.

Converter is bassically an application that converts DISTANCE MEASUREMENTS between METRIC and U.S units.

Converter is bassically an application that converts distance measurements between metric and U.S units.

This METHOD is USED to ENSURE that Swing components are updated through the event-dispatching THREAD.

This method is used to ensure that Swing components are updated through the event-dispatching thread.

A CANVAS object provides ACCESS to a graphics object VIA its paint() METHOD.

A Canvas object provides access to a graphics object via its paint() method.

The Key point is that the paint() method invokes three methods in the following order :
&GT; PAINTCOMPONENT()
> paintBorder()
> paintChildren()
As a GENERAL rule, in Swing, we should be overriding the paintComponent method unless we know what we are doing paintComponent() PAINTS only component (panel) but paint() paints component and all its children.

The Key point is that the paint() method invokes three methods in the following order :
> PaintComponent()
> paintBorder()
> paintChildren()
As a general rule, in Swing, we should be overriding the paintComponent method unless we know what we are doing paintComponent() paints only component (panel) but paint() paints component and all its children.

LIST is here :
> FLOW Layout MANAGER
> Grid Layout Manager
> Box Layout Manager
> BORDER Layout Manager
> CARD Layout Manager
> GridBag Layout Manager.

List is here :
> Flow Layout Manager
> Grid Layout Manager
> Box Layout Manager
> Border Layout Manager
> Card Layout Manager
> GridBag Layout Manager.

An Event handler is bassically a part of a COMPUTER PROGRAM created to TELL the program how to act in response to a SPECIFIC event.

An Event handler is bassically a part of a computer program created to tell the program how to act in response to a specific event.

EVENT is basscially as CHANGING the STATE of an OBJECT is CALLED an event.

Event is basscially as Changing the state of an object is called an event.

Double buffering is bassically the process of use of two buffers rather than one to TEMPORARILY hold data being moved to and from an I/O device. Double buffering INCREASES data transfer SPEED because one buffer can be FILLED while the other is being emptied.

Double buffering is bassically the process of use of two buffers rather than one to temporarily hold data being moved to and from an I/O device. Double buffering increases data transfer speed because one buffer can be filled while the other is being emptied.

A Lightweight component is the bassically one that "borrows" the SCREEN RESOURCE of an ancestor , which means it has no NATIVE resource of its own -- so it's "LIGHTER".

A Lightweight component is the bassically one that "borrows" the screen resource of an ancestor , which means it has no native resource of its own -- so it's "lighter".

A Heavyweight component is bassically ASSOCIATED with its own native SCREEN RESOURCE which is GENERALLY known as a peer.

A Heavyweight component is bassically associated with its own native screen resource which is generally known as a peer.

Many diff are there :
> AWT is heavy-weight components, but Swing is light-weight components.
> AWT is OS dependent because it uses NATIVE components, But Swing components are OS independent.
> We can CHANGE the look and feel in Swing which is not POSSIBLE in AWT.
> Swing TAKES less memory compared to AWT.
> For drawing AWT uses screen rendering where Swing uses double buffering.

Many diff are there :
> AWT is heavy-weight components, but Swing is light-weight components.
> AWT is OS dependent because it uses native components, But Swing components are OS independent.
> We can change the look and feel in Swing which is not possible in AWT.
> Swing takes less memory compared to AWT.
> For drawing AWT uses screen rendering where Swing uses double buffering.

AWT is bassically stands for Abstract Window Toolkit. AWT enables PROGRAMMERS to develop Java applications with GUI COMPONENTS, such as windows, and buttons. The Java Virtual MACHINE (JVM) is responsible for translating the AWT calls into the appropriate calls to the host OPERATING system.

AWT is bassically stands for Abstract Window Toolkit. AWT enables programmers to develop Java applications with GUI components, such as windows, and buttons. The Java Virtual Machine (JVM) is responsible for translating the AWT calls into the appropriate calls to the host operating system.

JFC stands for Java Foundation CLASSES. The Java Foundation Classes (JFC) are a set of Java class LIBRARIES provided as part of Java 2 Platform, Standard Edition (J2SE) to support BUILDING graphics USER interface (GUI) and graphics functionality for CLIENT applications that will run on popular platforms such as Microsoft Windows, Linux, and Mac OSX

JFC stands for Java Foundation Classes. The Java Foundation Classes (JFC) are a set of Java class libraries provided as part of Java 2 Platform, Standard Edition (J2SE) to support building graphics user interface (GUI) and graphics functionality for client applications that will run on popular platforms such as Microsoft Windows, Linux, and Mac OSX

Swing is basscially a type of Toolkit which is GUI toolkit for JAVA. It is one PART of the Java Foundation Classes (JFC). Swing includes graphical user interface (GUI) widgets such as text boxes, buttons, split-panes, and tables.
Swing widgets PROVIDE more sophisticated GUI components than the earlier Abstract Window Toolkit. Since they are written in pure Java, they run the same on all platforms, unlike the AWT which is tied to the underlying platform's windowing system. Swing supports pluggable look and FEEL � not by using the native platform's facilities, but by roughly emulating them. This means you can get any supported look and feel on any platform. The disadvantage of lightweight components is slower EXECUTION. The advantage is uniform behavior on all platforms.

Swing is basscially a type of Toolkit which is GUI toolkit for Java. It is one part of the Java Foundation Classes (JFC). Swing includes graphical user interface (GUI) widgets such as text boxes, buttons, split-panes, and tables.
Swing widgets provide more sophisticated GUI components than the earlier Abstract Window Toolkit. Since they are written in pure Java, they run the same on all platforms, unlike the AWT which is tied to the underlying platform's windowing system. Swing supports pluggable look and feel � not by using the native platform's facilities, but by roughly emulating them. This means you can get any supported look and feel on any platform. The disadvantage of lightweight components is slower execution. The advantage is uniform behavior on all platforms.

Without LAYOUT MANAGERS, Java programmers are FACED with determining how their GUI will be displayed across multiple windowing systems and finding a common sizing and POSITIONING that will WORK within the constraints imposed by each windowing system.

Without layout managers, Java programmers are faced with determining how their GUI will be displayed across multiple windowing systems and finding a common sizing and positioning that will work within the constraints imposed by each windowing system.

A THREAD class MAY be declared as a subclass of Thread, or it may implement the RUNNABLE interface.

A thread class may be declared as a subclass of Thread, or it may implement the Runnable interface.

Synchronized methods are methods that are used to control access to an OBJECT. A thread only executes a synchronized method after it has acquired the lock for the method's object or CLASS.

Synchronized statements are similar to synchronized methods. A synchronized statement can only be EXECUTED after a thread has acquired the lock for the object or class referenced in the synchronized statement.

Synchronized methods are methods that are used to control access to an object. A thread only executes a synchronized method after it has acquired the lock for the method's object or class.

Synchronized statements are similar to synchronized methods. A synchronized statement can only be executed after a thread has acquired the lock for the object or class referenced in the synchronized statement.