Online Books:
java.net on MarkMail:
 |
Search |
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Blogs by topic: Patterns
Patterns
I took last week off to work on some Wicket web programming - seeing as my day-job is desktop programming. I've done a lot of talks on API design, focusing on how to not "paint yourself into a corner" in terms of backward compatibility. There is a complementary subject - API usability, that deserves equal consideration. But reconciling the two is a hard problem.
I am using a pattern to provide the basic CRUD operations to all @Entity types in my Java EE projects. This blog introduces the idea and give you a sample code to play.
The spirited debate following my last post on messaging being degenerate RPC got me thinking; is there some way to combine these two somewhat orthogonal methodologies, to create a unique hybrid approach? A bit of insight led me back to update the original cajo Queue messaging class, and the results were indeed most satisfying.
How should abstract classes be named? AbstractClass, ClassAbstract, or something else?
A code sample on how to use Dependency Injection to modify the format and/or the way Footprint publishes PDF documents.
As a client, ever need to only use a portion of a service object's interface? How about small pieces from several of its interfaces? It could really simplify things to use a custom interface, containing only the methods needed. This is Dynamic Client Subtyping; let me show you how it's done.
In which we discuss the design of a good domain object.
Steve Metsker's and my recent book, Design Patterns in Java, has had a sample chapter posted at InformIT: Adapter.
If you're not familiar with Adapters, or need to brush up on them, you might find this chapter helpful. (The extract didn't include our solutions; let me know if you need help.)
Steve Metsker and I have co-written Design Patterns in Java, available from Addison-Wesley. This is a workbook-style book, updating Steve's earlier Design Patterns Java Workbook and Design Patterns in C#. It covers the same 23 patterns as Design Patterns, but adds some different perspective and a number of challenges to help you make sure you understand the patterns.
It's targeted to...
With complex enterprise systems, we often times find ourselves with lots of 'flags' or 'types' within our database tables. Utilizing Hibernate's UserType facility, we can handle these types in such a way that will carry extra behavior and information within your domain models.
The relationship between the visitor pattern and XSLT is discussed with respect to GeoAPI and Geotools.
Notes from Gergor's SOA talk.
As a followup to my initial post I have included generics within Predicate(s) to make them virtually resistent to ClassCastException(s).
After reading CrazyBob's article
about sudo closures in java some time ago I made it a point to familiarize myself
with this particular idiom as well as others that are often talked about but rarely
used within the java community. Unfortunately some time passed and as most things
this todo slipped my mind until I stumbled upon this article.
In my current project, there are several new solutions to some old patterns and there are also several new patterns, which were created to provide better performance and efficiency for the system. In this blog, I will attempt to provide you with information regarding each of the following patterns. Later blogs may include the details of why they were chosen, how they were put together, any problems that were encountered, and how those problems were solved.
The best book I readed concerning Patterns.
Component Frameworks have a lot to offer, but they need to encourage simple mapping between user requirements and the implementation of the requirements. Business Form oriented input validation can help.
I had an impressive Swiss Army knife when I was a kid, but I never did use all the blades.
How does the situation affect the nature of the software you build?
Architecture, reuse, declarative programming, etc. -- it's all about the language.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
