Apache Wicket 9 news

 With emerging of ReactJS and  Angular and Microservices, Apache Wicket framework seems darkly because many people think that only ReactJS, Angular, VueJS can work with Microservices. But apache wicket is also a FrontEnd framework and can communicate with Microservices over internet by JSON format data exchange and It is still safely, more stronger. Following is the news from https://wicket.apache.org site:

Read More

Devstack download: migrating from JSF to ReactJS

At Bandwidth, our UI front end was originally written using JSF (java server faces). This made sense at the time because we had a lot of Java developers and it was easier for them to work with. As time moved on and we expanded our team we got more front-end developers on board. They were pushing for a more modern front end stack that will help improve efficiency for front-end development. That is how we ended up deciding to use ReactJs.
I think one of the trickiest parts of the change was deciding how to go about it. It takes a lot of time and effort to make the change and we had to convince everyone that it would be worth it. Since there was already a movement to revamp our signup process, it seemed like a perfect opportunity to write that using ReactJs and Redux. It also had the plus side of not needing to be authenticated so you really couldn’t pick a better piece to migrate first. You can click the link below to check out our new signup page and see the results!

Read More

Jakarta EE and JSF 2.x

Jakarta EE

In September 2017, Oracle announced its intention to transition Java EE to the Eclipse Foundation. Java EE has since been rebranded to Jakarta EE, and JSF 2.3 (Eclipse Mojarra) has been adopted for continuation. The next major release of the JSF specification will be Eclipse Mojarra 3.0. (source from JavaWorld).

Read More

JSTL 1.2

1-JSTL Check Equals, not equals

JSTL Check Equals(==), not equals(!=) explains about how to use logical conditions(equals, not equals etc) with JSTL tag

Consider a JSP Page where you need to check a value whether it is equals or not equals and process accordingly, in that scenario,  you can follow this example.

On the following table, I am showing 2 different ways (Method 1 & Method 2), you can achieve equals & not equals in JSTL 

Logical operation	JSTL Method 1	JSTL Method 2
Equals	Eq	==
Not Equals	Ne	!=

Required Libraries

You need to download

1. Tomcat 7
2. JSTL 1.2

Following jar must be in classpath

1. jstl-1.2.jar

Read More

Struts2 AngularJS integration

Posted by Mohaideen Jamil on May 2, 2015 in Ajax, AngularJS, Struts-2 | 5 comments

In this post, we will learn to implement AJAX calls from a JSP page to a Struts 2 Action class using AngularJS and update the same JSP page back with the Json response from the Struts 2.

Library Required

Since Angular can send and receive only in json format, to handle it you need struts2-json-plugin-2.x.x.jar. This plugin allows you to serialize the Action class attribute which has getter and setter into a JSON object.

Read More

Struts2 AngularJS Insert Operation

LINK

As for the user interface, rather than Bootstrap, we'll use materialize CSS – a modern responsive front-end framework based mostly additionally on Google’s Material design.

FILE STRUCTURE

Knowing the file structure can offer us an outline of what Struts2 files can we need to create and wherever the assets should be placed.

Struts2 AngularJS CRUD Example - Read Operation

Read More

Comparsion: Struts 2 vs Spring 3 MVC

Apache Struts 2 and Spring MVC are two of the most popular Java web frameworks today. I’ve used both APIs extensively and wanted to share a quick comparison.

In Struts, the object that handles a request and routes it for processing is called an Action. In Spring MVC, that object is referred to as a Controller. Actions and Controllers are pretty much the same thing – they take input, process it, and return some sort of response.

The one major design difference is that by default, Struts 2 Actions are newly instantiated every time a request is made, whereas in Spring MVC the default behavior is to act as a Singleton. Spring MVC Controllers are created once and held in memory/shared across all requests. Note, you can change this behavior (scope) to request or session but we’ll talk about that later. This is a major difference to keep in mind when designing applications that need to be thread-safe, database oriented, or other share-able transactions.

Read More

Apache Wicket

Wicket framework

The Wicket framework component oriented, serverside, Java web application framework.

• Wicket summary in wikipedia
• 5 days of Wicket!
• Introduction to the Wicket Web Framework
• How to setup Wicket Examples in Eclipse
• Wicket 1.5.3 in NetBeans IDE 7.1
• JavaOne: Wicket open-source framework to debut

Read More

5 days of Wicket!

• Day 1 – Setting up the Project
• Day 2 – Writing the Tests
• Day 3 – Designing the backend
• Day 4 – Designing the Wicket components
• Day 5 – Putting it all together

1-Setting up the project (Ngày 1) :

Wicket is a Java web application framework which allows “Designers” (people good with Dreamweaver) and “Developers” (people good with Java and Databases) to collaborate on a project with minimal chances of stepping on each other’s toes or wearing each other’s hats.

The beauty of Wicket is that it uses plain xhtml pages as it’s templating markup.  This means that html pages can be loaded into Dreamweaver (or whatever tool the Designer is comfortable with) and they will look very close to the same as they would when rendered on the deployment web server.

Read More

Introduction to the Wicket Web Framework

This document takes you through the basics of creating reusable components and assembling them into a web application. Each component consists of a Java class and an HTML file. The framework that allows you to develop your application in this way is called Wicket. In addition to its component-based approach, a distinguishing feature of Wicket is the absence of XML configuration files. Instead of an XML configuration file, you use a Java class for application-wide settings, such as the identification of a home page.
Each widget in your web application is created in a Java class and rendered in an HTML page. The Java class and HTML page must have the same name and exist in the same source structure. They are linked to each other via a Wicket identifier. You will be shown how the IDE supports the development of component based applications so that you can quickly and efficiently create reusable components that can give your web application a consistent look and feel without very much work on your part.

Read More

How to setup Wicket Examples in Eclipse

Wicket examples is a good place to learn Apache Wicket by examples, and a must reference site for new or experienced Wicket’s developers. In this Wicket examples site, it almost contains all of the usage of the common wicket’s components.

In this guide, we show you how to setup the above Apache Wicket example site in your local development environment (Eclipse IDE).

Tools used :

1. Apache Wicket 1.4.17
2. Eclipse 3.6
3. Maven 3

Read More

JavaOne: Wicket open-source framework to debut

A new open-source framework aimed at simplifying the development of Java-based Web applications will debut at JavaOne Monday with support from a former Sun Microsystems Java evangelist.

Wicket, an open-source project founded in spring 2004 by Jonathan Locke, a member of the team that developed the JFC (Java Foundation Classes)/Swing framework, will introduce Wicket 1.0 next week at the annual Java developer confab, according to a press statement from the Wicket project.

Miko Matsumura, former Java evangelist at Sun and currently vice president for Infravio, will host a session about Wicket 1.0 Tuesday at JavaOne with one of the members of the project's development team, Martijn Dashorst, senior staff engineer at Topicus.

Wicket 1.0, which will be released under the Apache Software License, simplifies developers' ability to create and package reusable Web components by separating the creation of dynamic Web pages into two separate domains for designing and coding, according to the Wicket team. This allows the design and code teams to work independently without interfering with the other's process.

Read More

Wicket 1.5.3 in NetBeans IDE 7.1

Register this URL in your Plugin Manager: http://blogs.oracle.com/geertjan/resource/NetBeans4Wicket.xml OR http://java.net/projects/nbwicketsupport/sources/nbwicketsupport/show/WicketSuite/updates?rev=56.

(Note: The sources and binaries are at http://java.net/projects/nbwicketsupport, but for some reason you can't access NetBeans update centers if they're on java.net, hence I uploaded it into this blog.)

Then you'll be able to create Wicket applications in NetBeans IDE 7.1, in the final step of the New Web Application wizard:

Read More

HOWTO:Dynamically building components using NetAdvantage for JSF

Summary This article will show you how to build components at run time as the component is rendered, using NetAdvantage for JSF dynamically. The components will be created in the Java server-side code of the backing bean, instead of using tags to create the components in the JSP page. This is useful if either the contents or the format of the component is not known until run time.

Additional Information For this example, we are going to create a Sidebar and dynamically add Sidebar groups and links to the Sidebar. Although the example shows how to dynamically create Sidebar groups in a Sidebar component, the same technique should work for any JSF component.

Read More

JavaServer Faces (JSF) vs Struts

A brief comparison

September 28, 2004 - by Roland Barcia 

Summary
My JSF article series and Meet the Experts appearance on IBM developerWorks received a lot of feedback. I would have to say, the most common question or feedback came along the lines of comparing Struts to JSF.

My JSF article series and Meet the Experts appearance on IBM developerWorks received a lot of feedback.

I would have to say, the most common question or feedback came along the lines of comparing Struts to JSF. I thought it would be a good idea to compare JSF to Struts by evaluating various features that an application architect would look for in a Web application framework. This article will compare specific features. Those on which I will focus include:

• Maturity
• Controller Flexibility/Event Handling
• Navigation
• Page development
• Integration
• Extensibility

Read More

Designing Enterprise Applications with the J2EE Platform - Sample Design and Implementation

• Introduction
• J2EE Platform Technologies
• The Client Tier
• The Web Tier
• The Enterprise JavaBeans Tier
• Integrating with the Enterprise Information Systems Tier
• Packaging and Deployment
• Transaction Management
• Security
• J2EE Internationalization and Localization
• Architecture of the Sample Application

Additional Online Content:

• Sample Application Design and Implementation [PDF]

Sample Application Design and Implementation

---

The Java™ Pet Store sample application is a working demonstration of how to use Java™ BluePrints principles in a real application design. This document is an online guide to the design and the implementation of the sample application version 1.3.1. It supplements the book Designing Enterprise Applications with the Java™ 2, Enterprise Edition, Second Edition. This document assumes that the reader understands the topics explained in Chapter 11 of the book, Architecture of the Sample Application.

Read More

Từ struts1 đến struts2

History of Struts 2

Struts 2: trying to combine the stability and accessibility of Struts 1 with the elegant architecture of WebWork 2. Since the initial incubation, the Struts 2 code has added major features including a plugin framework, a new API, and better Ajax tags..

  

Comparing Struts 1 and 2

Feature	Struts 1	Struts 2
Action classes	Struts 1 requires Action classes to extend an abstract base class. A common problem in Struts 1 is programming to abstract classes instead of interfaces.	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	Struts 1 Actions are singletons and must be thread-safe since there will only be one instance of a class to handle all requests for that Action. The singleton strategy places restrictions on what can be done with Struts 1 Actions and requires extra care to develop. Action resources must be thread-safe or synchronized.	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.)
Servlet Dependency	Struts 1 Actions have dependencies on the servlet API since the HttpServletRequest and HttpServletResponse is passed to the execute method when an Action is invoked.	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.
Testability	A major hurdle to testing Struts 1 Actions is that the execute method exposes the Servlet API. A third-party extension, Struts TestCase, offers a set of mock object for Struts 1.	Struts 2 Actions can be tested by instantiating the Action, setting properties, and invoking methods. Dependency Injection support also makes testing simpler.
Harvesting Input	Struts 1 uses an ActionForm object to capture input. Like Actions, all ActionForms must extend a base class. Since  other JavaBeans cannot be used as ActionForms, developers often create redundant classes to capture input. DynaBeans can used as an alternative to creating conventional ActionForm classes, but, here too, developers may be redescribing existing JavaBeans.	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 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	Struts 1 integrates with JSTL, so it uses the JSTL EL. The EL has basic object graph traversal, but relatively weak collection and indexed property support.	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	Struts 1 uses the standard JSP mechanism for binding objects into the page context for access.	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	Struts 1 ActionForm properties are usually all Strings. Struts 1 uses Commons-Beanutils for type conversion. Converters are per-class, and not configurable per instance.	Struts 2 uses OGNL for type conversion. The framework includes converters for basic and common object types and primitives.
Validation	Struts 1 supports manual validation via a validate method on the ActionForm, or through an extension to the Commons Validator. Classes can have different validation contexts for the same class, but cannot chain to validations on sub-objects.	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	Struts 1 supports separate Request Processors (lifecycles) for each module, but all the Actions in the module must share the same lifecycle.	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.

Migration Strategies
The migration strategy of Struts 1 developers moving to Struts 2 involves four non-exclusive paths:

1.     Dual processor, shared resources - Add the Struts 2.0 JARs to your exisitng Struts 1.3 application. Configure S2 to handle *.action requests s and
let S1 handle *.do requests.
S1 and S2 can run side by side, within the same web application. Teams can implement new features in the latest version, and migrate older pieces as needed. Optionally, some common resources may be shared between S1 and S2, like messages, validation rules, and Tiles configurations, making for an even smoother migration.

2. Study known Struts 1 applications, rewritten for Struts 2 - Familiar applications such as the Struts Mailreader are being rewritten to demonstrate best practices for Struts 2.
3. Use a conversion wizard - It may be possible to create a tool that reads the web.xml and S1 configuration files, and generates the corresponding S2 classes, pages, and configuration files. While 100% compatibility is unlikely, we could make a strong effort to convert the application, marking areas that need attention. Comparing the converted files with the originals could also serve as a training tool.

Key Changes From WebWork 2
The upgrade path from WebWork 2 to Struts 2 is smooth glide. Here's the roadmap.

System Platform

• Struts 2 is dependant on XWork 2 (beta-1).
• Java 1.5 is required to build Struts 2.
• For Java 1.4 deployments, RetroTranslater JARS are available with the distribution.

For other changes from WebWork 2, see the "Members to rename", "New property settings", "New features or feature changes", and "Removed or deprecated" sections.

Members to rename

WebWork 2	Struts 2
com.opensymphony.xwork.*	com.opensymphony.xwork2.*
com.opensymphony.webwork.*	org.apache.struts2.*
xwork.xml	struts.xml
webwork.properties	struts.properties
DispatcherUtil	Dispatcher
com.opensymphony.webwork.config.Configuration	org.apache.struts2.config.Settings

The tag prefix conventions in the example applications have changed.

JSP	s:	<s:form ...>
Freemarker	s.	<@s.form ...>
Velocity	s	#sform ( ... )

New property settings

struts.enable.DynamicMethodInvocation		Enable support for the hardwired action!alias syntax (Default is TRUE). It is recommended that all applications specify the DynamicMethodInvocation setting for now, since the default may change. The recommended approach to action aliasing is to use wildcard aliases instead of the hardwired bang.

New features and feature changes

·                     Various changes to ConfigurationManager

o    ConfigurationManager is no longer a static factory. It is now an instance created through Dispatcher. Custom configuration could be done through DispatcherListener.

o    Custom configuration to ConfigurationManager and Configuration cannot be done statically anymore, instead use Dispatcher's DispatcherListener to achieve the same effect.

o    The prepare interceptor now uses reflection to call prepare_Method_ where method is the action method configured for the particular action in struts.xml.

// with the above configuration, and PrepareInterceptor in play, callsequence will be

1] prepareInsert() (If it exists)

2] prepare() (Unless Interceptor's alwaysInvokePrepare parameter

   is set to false)

3] insert()

o    DefaultWorkflowInterceptor (named workflow in struts-default.xml) now uses reflection to call validateMethod on the action class that implements Validateable interface where method is the action method configured for the particular action in struts.xml.

·         <action name="myAction" method="insert" ...>

·                ...

    </action>

// with the above configuration, and DefaultWorkflowInterceptor in play, 

//call sequence for action that implements Validateable interface will be

1] validateInsert()

2] validate() (unless Interceptor's alwaysInvokeValidate parameter

   is set to false)

3] insert()

• The tooltip library used by the xhtml theme was replaced by Dojo's tooltip component.
• Datepicker tag has been renamed to datetimepicker and is now using dojo (limited in terms functionality and internationalization)
• Tiles integration plugin is available.
• Wildcards can be specified in action mappings.
• MessageStoreInterceptor is introduced to allow field errors / action errors and messages to be store and retrieve through session, resulting them to be preservable across request.

Removed or deprecated

AroundInterceptor	The AroundInterceptor has been removed. If your application extends the AroundInterceptor, either import the class into your source code form WebWork 2 (pursuant to the Open Symphony License) and modify it to server as your own base class, or rewrite your interceptor.
oldSyntax	Support for the "oldSyntax" is removed.
Rich text editor tag	Rich text editor tag is removed and replaced by Dojo's rich text editor
doActionMethod	The convention of trying a "do" form of an action method is not supported. <action name="..." method="submit">     ...   </action> In WebWork, try to execute submit method in the action, fail try to execute doSubmit method in the action if Step 1, fail fail In Struts, try to execute submit method in the action, fail fail
default method	Calling the "default" method via "doDefault" is not supported.
IOC framework	Deprecated in WebWork 2.2, the internal IOC framework is removed in Struts 2. Spring is the ObjectFactory default.

Ref: 

http://struts.apache.org/2.x/docs/struts-1-solutions.html

http://struts.apache.org/roadmap.html

http://www.ibm.com/developerworks/web/library/wa-dynamicstruts/?ca=drs-

Read More