The LengthValidator is one of the standard validators that is specified by the JavaServerFaces specification. It allows you to verify (validate) if the proposed input (submitted value) on a given component is valid.
Say you want to make sure the minimum length of a password is 6 characters and up to 12 characters. The example below describe how you would put this into a JSF page to make that...
on Sep 4, 2012
During the JSF lifecycle each input value can be validated. As such the JSF runtime allows you to write validators that will take care of that during request processing.
Several standard validators are part of the standard JSF runtime. Note that the specification has been written with extension in mind so it is also possible to write your own validator and hook it up for request processing...
on Sep 1, 2012
JSR 359 has been accepted by Java SE/EE executive committee a month back. Please see the specification request for the content of this revision of SIP Servlet 2.0 specification. We have established a java.net project for cordinating and communicating the progress of the specification. The work is about to get started. At the moment, the expert group is being formed and some of the leading...
on Sep 3, 2012
Welcome to the 198th issue of The Java(tm) Specialists' Newsletter sent to you from Chania in Greece. My readers in colder climates frequently get annoyed when I tell them that "life's a beach". They imagine us having constant sun here. It's not true. We do sometimes have torrential rains and cold weather. It even snows here occasionally. In fact, the delivery...
on Feb 14, 2012
The definition of a Validator according to the Validator interface:
void validate(FacesContext context, UIComponent component, Object value) throws ValidatorException
The Faces Context is passed in so the validator can introspect various aspects of the request and response.
The UI component is passed in because the actual value will be stored in that UI component after it has been...
on Sep 3, 2012
10 years ago, we began our journey into the world of Java and "J2EE".
It was a big risk for my company, Amway Corp, to do this.
We had no in-house expertise and we had critical applications to migrate to the new technology.
From the beginning, we were determined to succeed.
Today, 10 years after; I can say our Java adventure has been very successful.
We have created two complex applications and...
on Aug 17, 2012
When my company, Amway Corp, makes a sale; somewhere, somehow a computerized transaction of that sale is created.
This transaction is sent to a number of applications at Amway for processing.
One such destination is our Java application.
We created a capability, called the Transaction Monitor (or TM) to deliver transactions to our app.
Our initial version of the TM worked well, but it was still...
on Aug 10, 2012
As we began our Java adventure at Amway Corp 10 years ago,
one of the most important tasks we had to do was to create our Object Model.
We had a variety of Java objects that we were planning to use in our application.
How were they going to be "wired" together inside of the application?
After 4 weeks of Object-Oriented, J2SE, J2EE training; we set out to define our Object Model.
This model was...
on Jul 16, 2012
As we began to learn about Java technologies at Amway Corp, we were introduced to UML (Unified Modeling Language).
We became interested in the modeling aspect of UML to assist in the analysis and design phases of our Java project.
So we decided to try our hand at modeling with UML.
It began with 2 week-long training classes.
1) Object-Oriented Analysis with UML
2) Object-Oriented Design with UML...
on Jul 9, 2012
In order to successfully migrate our mainframe application to a Java/application server based solution,
we had to figure out how to migrate our batch processes.
We had a very good start, in achieving this, by utilizing the LaunchClient command and J2EE Client programs.
It was just a matter of putting the remaining pieces together into a working solution.
But we were running into a lot of trouble...
on Jul 2, 2012
For us at Amway Corp, a key part of creating batch processes, with Java, was using the LaunchClient command and
J2EE Client applications. We felt we were very close to being able to run our Java batch processes on the
application server. But more trials and tribulations were ahead of us.
We created a J2EE Client application\program that would call a "hello world" EJB.
After deploying the code to...
on Jun 29, 2012
Our first Java application (10 years ago) was a migration of a legacy application.
The legacy application consisted of a number of screens and a number of batch processes.
Migrating the screens to Java technology seemed straight forward.
In theory, they would be a direct use of the MVC pattern (EJB, JSP, Servlet). Easy.
But what about the batch processes? They didn't seem to fit the MVC pattern....
on Jun 24, 2012
During the initial architecture and analysis of our J2EE-based application,
one Java issue generated a lot of attention on our team : Enterprise Java Beans or EJBs.
Should we use EJBs?
What flavor of EJBs should we use?
At the time, we received no practical advice on EJB usage.
We got a lot of general advice. "Use what is best for you, etc."
Quite often, we were referred to a diagram with a lot...
on Jun 4, 2012
In the beginning, our development team had no Java experience at all.
Most of us were mainframe developers with a decade or so of IT experience.
We realized that not only did we need Java training, but we needed training
on object-oriented concepts as well. It seemed like a very challenging goal to achieve.
One of the reasons we chose our particular Java software tools vendor
is because their...
on May 28, 2012
Release the newest version of the framework to persist objects in Apache Cassandra in easy way. Among improvement is the JPA annotations, also JPQL.
JCassandra jCassandra=persistence.createJCassandra("select * from Person"); List<Person> persons=jCassandra.getResultList();
table 1: sample using JPQL in Easy-Cassandra
This version has the improvements below:
on May 26, 2012
When we starting planning how we were going to use Java technology at Amway (10 years ago);
we realized we had many decisions to make about standards to adopt, practices to learn,
architectures to use, patterns to follow, etc.
Fortunately for us, there were many sources of information to help us figure all of this out.
Unfortunately for us, there were many sources of information to help us figure...
on May 21, 2012
10 years ago, when we were decided to use Java technology to create a new application,
for use at Amway Corp; we thought it was sufficient to say, "We are using Java!".
We were wrong...
We quickly realized that there was Java 2 Standard Edition and there was Java 2 Enterprise Edition.
Since we were architecting our application to run in an application server-based environment,
we concluded that...
on May 14, 2012
Hello all. My name is Larry Fernandez and I am a Principal Software Developer in IT.
I work for Amway Corp in Grand Rapids, Michigan.
March 2012 was my company's 10-year anniversary using Java. We have over 1 million lines of J2EE code in production,
with more on the way. I have been here since our "Java" beginnings and I have played many roles
(developer, architect, project manager, etc.).
on May 9, 2012
We began creating our second Java application five years after we began the first app.
We were hoping the second application would give us a chance to use additional Java technologies.
We began by gathering all of the known functional requirements and matched them to the various
Java-related technologies we knew of.
The result was a high-level technical architecture of the application.
on Aug 3, 2012
Easy-Cassandra is a framework ORM API and a high client for Apache Cassandra in java, with this is possible persist information from the Java Object in easy way. For this is only necessary add some annotations in some fields and your class. It works like an abstraction's tier in the Thrift, doing call for Cassandra.
on Feb 21, 2012