This is a short info on JSR 359, which just got started.
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...
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...
New JVM 7.0 flags to enable and configure GC log file rotation
hamcrest-reflection provides fluent assertions for reflection-based assertions. I uploaded it to Maven Central this week, so using it got even simpler now.
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...
A few years ago, we met with our business analysts to discuss security for our application.
Our goal was to implement our own authentication mechanism for the web-based or user-interface
portion of the application.
We defined authentication security as "access rights to resources of the application".
After some initial discussion, one of our business analysts suggested we look for an
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...
During our 10 years of using Java at Amway Corp., some of our solutions
required us to think a little "outside of the box".
Our application had a reporting requirement.
It had to generate reports from the application's various batch processes as they were running.
These batch processes performed transaction processing, data purging and data exporting functions.
The reports would not be used by...
It never ceases to amaze me where some solutions in application development come from.
We had a requirement for our application to allow a user to print pages of text.
The user would bring up a web page, from our app, and then create & print a list of customer names.
The list of names would be created by executing a SQL query against the database, using a variety of search criteria.
I’m someone who came to this field from a management, as opposed to technical, background. In an effort to understand this website and its users more fully, I am (slowly and painfully) teaching myself basic Java, reading every book handed to me, and jumping at the chance to attend any conference the Oracle Powers That Be will allow. One of my biggest hurdles has been the special technical...
Greenlight for Girls! Metaprogramming in Java! Great ideas for growing your JUG!
Where's Ed at JavaOne 2012
Samplr is an open source, smart sampling profiler that can be embedded into any Java application for automatic identification of performance bottlenecks
In a previous post I outlined some of the problems one has dealing with real-time, asynchronous data. Since I have been working on a library to handle those issues, I'll start to go through some of the design.
The library is open source, and available at http://pvmanager.sourceforge.net. It's being developed and used in the EPICS accelerator control community, which comprises various...
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.
Release announcement for SwingX 1.6.4.
My notes from Friday at OSCON 2012 in Portland, Oregon.