Design patterns implemented in java API

Hi,
I have some questions on design patterns implemented in core java class or in general in java API.
1)Whether
java.util.Collections, the checkedXXX(), synchronizedXXX() and unmodifiableXXX() methods.
can be considered as a decorator pattern?
2) Whether
LinkedHashMap(LinkedHashSet<K>, List<V>) which returns an unmodifiable linked map which doesn't clone the items, but uses them
can be considered as a Bridge pattern?
3) Whether Facade pattern is implemented in java ? If so which API uses it?
4) Whether
•     All non-abstract methods of java.io.InputStream, java.io.OutputStream, java.io.Reader and java.io.Writer.
•     All non-abstract methods of java.util.AbstractList, java.util.AbstractSet and java.util.AbstractMap
can be considered as a Template method pattern?
5) Whether
•     java.util.Comparator#compare(), executed by among others Collections#sort()
can be considered as a Stratergy pattern?
6)
Whether State pattern is implemented in java ? If so which API uses it?
7)
All implementations of java.lang.Runnable are considered as a Command pattern.
8)
Whether
•     java.io.InputStreamReader(InputStream) (returns a Reader)
•     java.io.OutputStreamWriter(OutputStream) (returns a Writer)
can be considered as an Adapter pattern?
Please clarify.
Thanks.

What do you think, and why?

Similar Messages

Deployment Issue with MDM Java API exposed as Webservice using EJBS

Hi Experts,
I am implementing MDM Java APIS in Stateless session bean.Exposed that bean as Webservice and using that webservice in
Webdynpro through Adaptive Webservice Model.
I am facing following issue:
Webservice works fine after deployment,after some number of execution webservice stops working and gives exception.After
Redeployment of the Webservice, it starts working again works fine some number of execution.
I am Using new MDMJava API.
MDM Server Details: MDM 5.5 SP06
I am using following code for connetion
//////////////*************Getting Connection************///////
          ConnectionPool pool = null;
          String sessionId = null;
          try {
               pool = ConnectionPoolFactory.getInstance("Server Ip");
          } catch (ConnectionException e1) {
               System.out.println(e1.getMessage());
//////////////*************Repository Session************///////
CreateRepositorySessionCommand repSeession =
               new CreateRepositorySessionCommand(p_pool);
          repSeession.setRepositoryIdentifier(p_repId);
          try {
               repSeession.execute();
          } catch (CommandException e2) {
               System.out.println(e2.getMessage().toString());
          String repIID = repSeession.getRepositorySession();
          //     Authenticate Repository
          AuthenticateRepositorySessionCommand autRepSeesion =
               new AuthenticateRepositorySessionCommand(p_pool);
          try {
               autRepSeesion.setSession(repSeession.getRepositorySession());
               autRepSeesion.setUserName(p_user);
               autRepSeesion.setUserPassword(p_Password);
               autRepSeesion.execute();
          } catch (CommandException e3) {
               System.out.println(
                    "RepSession Seesion" + e3.getMessage().toString());
          return autRepSeesion.getSession();
//////////////*************user Session************///////
GetRepositoryRegionListCommand regionListCommand =
               new GetRepositoryRegionListCommand(p_pool);
          regionListCommand.setRepositoryIdentifier(p_repId);
          try {
               regionListCommand.execute();
          } catch (CommandException e) {
               System.out.println(e.getMessage().toString());
          RegionProperties[] regions = regionListCommand.getRegions();
          //                                 create a user session
          CreateUserSessionCommand UsersessionCommand =
               new CreateUserSessionCommand(p_pool);
          UsersessionCommand.setRepositoryIdentifier(p_repId);
          UsersessionCommand.setDataRegion(regions[0]);
          // use the first region
          try {
               UsersessionCommand.execute();
          } catch (CommandException e) {
               System.out.println("UserSession" + e.getMessage().toString());
          String UsersessionId2 = UsersessionCommand.getUserSession();
AuthenticateUserSessionCommand authUserCommand =
               new AuthenticateUserSessionCommand(p_pool);
          authUserCommand.setSession(UsersessionCommand.getUserSession());
          authUserCommand.setUserName(p_userId);
          authUserCommand.setUserPassword(p_password);
          try {
               authUserCommand.execute();
          } catch (CommandException e) {
               System.out.println("User Seesion" + e.getMessage().toString());
          return authUserCommand.getSession();
//////////////*************Destroy Session************///////
     DestroySessionCommand destroySessionCommand =
               new DestroySessionCommand(p_pool);
          destroySessionCommand.setSession(p_repsession);
          try {
               destroySessionCommand.execute();
          } catch (CommandException e) {
               e.printStackTrace();
          destroySessionCommand.setSession(p_Uesrsession);
               try {
                    destroySessionCommand.execute();
               } catch (CommandException e) {
                    e.printStackTrace();
Do we need to relase the connection pool object also?
Can anyone help me with the code how that can be achived?
Please Reply if anyone has come accross similar issue or know what can be the solution.
Thanks in Advance.
Regards Shruti
Edited by: Shruti Shah on Dec 18, 2008 12:52 PM

Hi Nitin,
Thanks for the prompt Response.
Even I am guessing that its becose of Connection pool.
I am destroying session as follows
               DestroySessionCommand destroySessionCommand =
               new DestroySessionCommand(p_pool);
          destroySessionCommand.setSession(p_repsession);
          try {
               destroySessionCommand.execute();
          } catch (CommandException e) {
               e.printStackTrace();
          destroySessionCommand.setSession(p_Uesrsession);
               try {
                    destroySessionCommand.execute();
               } catch (CommandException e) {
                    e.printStackTrace();
But I didnot find any method by which i can close realsse connection from connection pool.
It would be great if you can help me how close or realese those connection.In MDM Console i am able to see those sessions even after destroying them.
Regards Shruti.

ABAP objects design patterns

hi all,
    can any one send me the Design patterns used for ABAP objects programming in ABAP. eg mvc and sample code which uses the design patterns
cheers
senthil

Of course that program is not an object design pattern
(Its just a little ABAP Objects syntax demo that I wrote years ago
I don't know about a list of OO design patterns implemented in ABAP Objects.
A very simple one, a Singleton might look like this:
<b>* cl_singleton: Eager Variant
CLASS cl_singleton DEFINITION FINAL
                              CREATE PRIVATE.
PUBLIC SECTION.
    CLASS-METHODS: class_constructor,
                   get_singleton RETURNING VALUE(singleton)
                                           TYPE REF TO cl_singleton.
PRIVATE SECTION.
    CLASS-DATA singleton TYPE REF TO cl_singleton.
ENDCLASS.
CLASS cl_singleton IMPLEMENTATION.
METHOD class_constructor.
    CREATE OBJECT singleton.
ENDMETHOD.
METHOD get_singleton.
    singleton = cl_singleton=>singleton.
ENDMETHOD.
ENDCLASS.
cl_singleton: Lazy Variant
CLASS cl_singleton DEFINITION FINAL
                              CREATE PRIVATE.
PUBLIC SECTION.
    CLASS-METHODS get_singleton RETURNING VALUE(singleton)
                                          TYPE REF TO cl_singleton.
PRIVATE SECTION.
    CLASS-DATA singleton TYPE REF TO cl_singleton.
ENDCLASS.
CLASS cl_singleton IMPLEMENTATION.
METHOD get_singleton.
    IF cl_singleton=>singleton IS INITIAL.
      CREATE OBJECT cl_singleton=>singleton.
    ENDIF.
    singleton = cl_singleton=>singleton.
ENDMETHOD.
ENDCLASS.</b>

CairnGorm Design Patterns

Can any one let me know the design patterns
implemented in Cairngorm?

Are you talking about Cairngorm 2 or 3 ?
Cairngorm 2:
Model View Controller
Command
Responder
Delegate
Singleton
Cairngorm 3 (on top of Parsley):
Dependency Injection
Presentation Model

Java API that implements the SSH, SFTP and Telnet protocols

Hi,
I'm looking for a Java API that implements the SSH, SFTP and Telnet protocols. Does anyone have a suggestion?
Any Suggestions are really appreciated ?
Thanks,
Avin

I believe SSH and telnet are used for interactive command line sessions, don't know how you want to use them in a program.

Software reuse with Java design patterns

Anyone have any suggestions on how software can be reused with Java design patterns? Any concrete examples?

Buy the GoF book. Lot's of examples there.

Core Java Design Patterns

Hi folks,
I wanna know about design pattern to implement my current project, I need some reference book. if you know the book. please mail me
[email protected]
Thanks and regards
SK,India

[The GoF book|http://www.amazon.co.uk/gp/product/0201633612/ref=s9sims_c3_at1-rfc_g1?pf_rd_m=A3P5ROKL5A1OLE&pf_rd_s=center-1&pf_rd_r=1JQJWT69HDE1GTFS4EXH&pf_rd_t=101&pf_rd_p=139045791&pf_rd_i=468294]
[Head First Design Patterns|http://www.amazon.co.uk/Head-First-Design-Patterns/dp/0596007124/ref=pd_sim_b_2]
[Refactoring to Patterns|http://www.amazon.co.uk/Refactoring-Patterns-Addison-Wesley-Signature-Kerievsky/dp/0321213351/ref=sr_1_1?ie=UTF8&s=books&qid=1216992456&sr=1-1]
Enjoy

Design Pattern for Building Trees (Java)

I'm wondering if there is a design pattern suited to build trees from a given domain object.
public interface DomainObject {
public long getId();
public abstract class Displayable {
private DomainObject domainObject;
private Displayable parent;
private Vector children;
public Displayable(DomainObject domainObject, Displayable parent) {
this.domainObject = domainObject;
this.parent = parent;
this.children = new Vector();
public Displayable(DomainObject domainObject) {
this(domainObject, null);
public Displayable getParent() {
return parent;
public DomainObject getDomainObject() {
return domainObject;
public Displayable[] getChildren() {
return (Displayable[])children.toArray(new Displayable[children.size()]);
public void addChild(Displayable d) {
children.add(d);
Example:
DomainObject O
Displayable D (contains O)
D's parent is C
C's parent is B
B's parent is A
A does not have a parent
A --> B --> C --> D(O)
Method signature
public Displayable buildDisplayable(DomainObject domainObject);
So basically pass in a DomainObject (O) and spit out the Displayable (D), with the tree built up to the root (A).

No I graduated last year from college. I'm trying to improve our SWT/JFace GUI framework. That method signature is just something I thought about. I'm thinking using Factory Pattern will have to do considering I know ahead of time which subclasses of Displayable have parents and children.

Design Patterns Support in Jdev 10.1.3?

Is Design Patterns Support included as part of JDev 10.1.3. I have seen this support in SAP NetWeaver Developer Studio where you have the option of converting existing classes to implement a certain J2EE/J2SE Design Pattern or create a new class(es) to implement a Design Pattern. I believe TogetherSoft has this support.
Any chances this request is consider in the next major release of JDev 10.1.3?

Dear Shmeltzer,
My company just begins the migration from Oracle Form-based application to pure Java EE one. We will be using JDeveloper v10.1.3, persuaded by it fast GUI building, data-binding features. Before that, we have been trying out Eclipse & JBoss.
We are going to use Swing & JSF for client, and JavaEE 5 for midtier. Persistence layer, will be JPA (EJB3 entity bean persistence) and Spring Framework DAO support. Spring DAO is interesting bcos it gives a consistent style of API (we want to support both JDBC & JPA) and consistent Exception hierarchy too. So our midtier will be partitioned (roughly according to Fowler's patterns) into 3 layers: Service, Domain/Biz Object, Data Access. Thus far is pretty standard.
We are still pretty new to this ADF, and are still exploring.
Now, my initial impression with ADF is that it seems to interfere too much with the kind of pattern we had in mind. The fact that ADF hides too much details from us programmers scares me -- it becomes restrictive and we are helpless as to what are going on inside (with those xml, dcx, etc). For e.g. talk about Service Locator pattern, and we cannot seem to figure out how/where it is implemented. Using ADF Data Control and Biz Components will make all the design patterns "disappear" -- we dont see DAO classes anymore bcos it has been automated. It looks more like 2-tier client-server pattern to me. :-)
We are interested to use ADF data-binding features, so
1) Is it still advisable to use Spring DAO layer?
2) Is it possible to just use ADF in the Client / web tier, while the EJB container remains free of ADF technologies?
Regards.

Chain of Responsibility Design Pattern

Is there any java api which helps in implementing Chain of Responsibility Design pattern by parsing a XML file?. Can I use XML file to do this in Apache Commons Chain API?

A quick look at the javadocs for that project suggest that, yes, indeed they do provide a way to specify a chain of command using XML.
In fact I'm kind of confused why you even asked this question, since you already seem to know the answer.
I've never heard of such a thing in the standard API, if that's what you're asking, probably because it's a simple pattern to implement, and most of the pain of any implementation is likely to be due to details specific to the problem domain, not the pattern.
If you're really eager to use XML, you might want to check out Spring. You could configure a bunch of beans in a chain, if you like.

Java API's supported in the Jdeveloper, IAS, and RDBMS product components

If there are any technical errors or "mistatement of the facts" in this posting, please let me know about them ..
This article is being delivered in Draft form and may contain
errors. Please use the MetaLink "Feedback" button to advise
Oracle of any issues related to this article.
PURPOSE
This article describes the "Enterprise Java Beans" (EJB), "Java Server Pages"
(JSP) and servlets Application Programming Interfaces (API) supported by the
Oracle products, Jdeveloper, Internet Application Server (IAS) and the Oracle
RDBMS release 2 and release 3, also known as Version 8.1.6 and 8.1.7,
respectively.
SCOPE & APPLICATION
All parties interested in the Java API's supported by these products.
Java API's supported in the Jdeveloper, IAS, and RDBMS product components
JDEVELOPER
JDEVELOPER is Oracle's Java development tool designed for coding / development,
testing / debugging, and deployment of Java Applications to the IAS and
RDBMS platforms.
With the java software api's being in a constant state of evolution, each new
release of Jdeveloper adds support for the "then current" version of the java
software api's, if it does not already have it implemented.
JDEVELOPER SERVLET API JSP API EJB API
VERSION VERSION VERSION VERSION
3.2.X.X 2.2 1.1 1.1
3.1.X.X 2.1 1.0 1.0
NOTE :
Sun Microsystems and their advisory teams (Oracle is on it) is working on
"draft" specifications for the next version of all of these API's
EJB -------> http://java.sun.com/products/ejb/index.html
JSP -------> http://java.sun.com/products/jsp/index.html
Servlets --> http://java.sun.com/products/servlet/?frontpage-javaplatform
It is anticipated that future releases of Jdeveloper will continue to be
upgraded to include support for the next version of each api.
To obtain the latest information on Oracle's Internet Development Suite (IDS)
of tools, please review the "Internet Developer Suite" information located
on Oracle's technet web site at :
http://technet.oracle.com/products/index.htm
IAS
IAS is Oracle's next evolution of the web server and application server
product technology superceeding the Web Application Server (WAS) and Oracle
Application Server (OAS) product lines.
IAS SERVLET API JSP API EJB API EJE VERSION
VERSION VERSION VERSION VERSION SUPPORTED
9I(1.0.2) 2.2 1.1 1.1 817
8i(1.0.1-NT) 2.0 1.0 1.0 816
8i(1.0.0-UNIX) 2.0 1.0 1.0 816
The IAS product contains two Java Virtual Machines (JVM) within it's
architecture.
They are called :
1) APACHE JSERV servlet engine
2) ORACLE ENTERPRISE JAVA ENGINE (EJE)
APACHE JSERV servlet engine
The APACHE JSERV servlet engine is an EXISTING product licensed from the
apache group which supports the servlet api 2.0.ONLY.
The APACHE JSERV product does not support ANY JSP's unless the customer
installs a third party jsp engine.
The IAS 8i/9i which has the APACHE JSERV product embedded in it, comes with
Oracle's JSP engine (OJSP) already integrated into it. OJSP supports JSP's up
to the specific JSP engine version documented in the Oracle Universal
Installer (OUI) for the 8.1.7 RDBMS or the IAS products. It is also documented
in the product's release notes.
Oracle ENTERPRISE JAVA ENGINE (EJE)
The EJE formerly known as :
1) Oracle 8i Java Virtual Machine (JVM)
2) JSERVER component,
3) Aurora JVM
was originally releas ed in the RDBMS 8.1.5 database with jdk 1.1.6 based java
support.
The currently supported versions of the Oracle 8i RDBMS, versions 2 and 3,
also known as Version 8.1.6 and 8.1.7, respectively, provides a jdk 1.2.1
based java virtual machine support.
"EJE" Version 816
This EJE, found in rdbms 8.1.6 and IAS 8i, contains support for the ejb
api 1.0, corba, and java stored procedures.
"EJE" Version 817
This EJE, found in rdbms 8.1.7 and IAS 9i, contains support for the ejb,
corba, and java stored procedures as well as the Oracle Servlet Engine (OSE)
which provides support for the servlets 2.2 api and JSP 1.1 api.
Note :
EJB support in the "EJE" Version 817 has been upgraded to comply with the EJB
1.1 api specification which includes "entity beans" support.
What is the bottom line ??
1) Servlets deployed to the APACHE JSERV must comply with servlet api 2.0.
2) Servlets 2.1 or higher are only supported in EJE's OSE component found in
the rdbms 817 or ias 9i products. Servlets api 2.0 can also run in the OSE.
References
1) "Oracle9i Application Server Technical White Paper" located at :
http://technet.oracle.com/products/ias/pdf/9ias_102.pdf
2) "Whats New? Oracle8i JVM Accelerator, Oracle Servlet Engine, OracleJSP ..."
located at :
http://technet.oracle.com/products/oracle8i/pdf/504.pdf
3) "Oracle8i Release 3 New Features Summary" located at :
http://technet.oracle.com/products/oracle8i/pdf/8iR3_nfs.pdf
null

which jvm is used by jserv ?? EJE or a separate jdk ?
The Jserv servlet engine is running in a separate jdk JVM external to the EJE jvm which is embedded within the "database" component of ias and the RDBMS.
See the reference below for more details ...
if jserv only support old apis, why it is in oracle's products ?
i would assume that the oracle servlet engine was under development when ias 8i was released and became available in time for the ias 9i and rdbms 817 products.
looking back in history leads me to believe ias 8i was a migration path to get to ias 9i or rdbms 817.
Based upon the long history of new releases of every oracle product being upgraded with new features, it's reasonable to assume that these products will continue to evolve.
when I deploy a jsp how to deploy in the right servlet container ("EJE") ?
as documented in the reference below, you can deploy JSP's to either the apache jserv jvm or the EJE since the ORACLE JSP engine functionality is in both jvm's.
there are many posts where you can see that people have deploy in jserv and they have problems because they don't use the right container (servlet 2.0 instead of
servlet 2.2) http://technet.oracle.com:89/ubb/Forum2/HTML/006349.html
when ias 8i came out this was clearly an issue since servlet support was at api 2.0, and the current servlet api was probably at 2.1.
oracle clearly made every effort to get ias 9i released quickly to supply a servlet 2.1 and 2.2 capable engine to resolve this issue.
since ias 9i and rdbms 8.1.7 are available this is no longer an issue.
The reference below explains the architecture and understanding it would eliminate a lot of "deploy to the wrong ias 9i component" issues.
so why jserv is bundled with oracle 8i/9ias since EJE support the right api version ?
if in ias 9i release , oracle had removed the jserv component without any advance warning, many customers would have been very upset since oracle makes every attempt to give advance notice before removal of functionality.
References
1) "Oracle9i Application Server Technical White Paper" located at :
http://technet.oracle.com/products/ias/pdf/9ias_102.pdf

SERVICE LOCATOR ?? Is it really an interesting Design pattern??

Hi everybody,
i've a problem with the J2EE Design Pattern "Services locator" (it's a singleton).
It is said that by making use of a Service Locator we can :
- hide to the client the complexities of initial context creation, EJB home object lookup,and EJB objectre-creation.
- multiple clients can reuse the Service Locator object to reduce code complexity, provide a single point of control, and improve performance by providing a caching facility.
But i would like to understand at which side should that service locator object reside??!!??
If it is at server side then the clients need well an initial context in order to make a lookup on that object.
Conclusion :
the service locator doesn't hide the complexities of initial context!!
Furthermore the client has to perform a look-up on that service locator object!! The only advantage left is caching facility.
If it is at client side, each client needs his own services locator object
Conclusion :
multiple client don't reuse the same service locator. What's the advantage to be a singleton ???
There is certainly something that i don't understand so help me please!! Thanks.

Hi Yves,
But i would like to understand at which side should
that service locator object reside??!!??
If it is at client side, each client needs his own
services locator object
Conclusion :
multiple client don't reuse the same service locator.
What's the advantage to be a singleton ???The service locator resides on the client side and is implemented as
a singleton. Since it is possible that there could be multiple
class loaders/JVMs on the client side, and therefore, multiple
instances of the "singleton" service locator. This is typical
in a distributed environment (e.g. servlets/JSPs in a web-tier
cluster using service locator). Thus service locator is not
a truly "distributed singleton" object. But, the empahsis
is to design the service locator such that it does not hold
any state that needs to be replicated across multiple
instances across different JVMs as mentioned. Thus, there
is no need for multiple clients to use the "same" service locator,
but still the benefits of implementing this pattern is realized.
By making it a singleton, and keeping it from holding state
that needs to be replicated, we realize the benefits of this pattern.
You may also want to visit the J2EE Pattern interest list
and see these relevant discussions :
Topic: Service Locator and passivation
http://archives.java.sun.com/cgi-bin/wa?A2=ind0106&L=j2eepatterns-interest&F=&S=&P=1026
Topic: Caching EJBHome interfaces
http://archives.java.sun.com/cgi-bin/wa?A2=ind0106&L=j2eepatterns-interest&F=&S=&P=9226
Topic: Using Service Locator for Data Source caching
http://archives.java.sun.com/cgi-bin/wa?A1=ind0106&L=j2eepatterns-interest#31
hope this helps,
thanks,
-deepak

ANN: New Design Pattern (DAO)

Hello,
Thanks for your overwhelming response to our previous sample applications demonstrating various [url http://www.oracle.com/technology/sample_code/tech/java/j2ee/designpattern/index.html]design patterns.
Continuing with the series, this month we have showcased the [url http://www.oracle.com/technology/sample_code/tech/java/j2ee/designpattern/dataaccesstier/index.html]Data Access Object (DAO) Design Pattern which is considered as a best practice for applications accessesing the database or the underlying persistence layer from the business tier.
The DAO implements the access mechanism required to work with the data source. The data source could be a persistent store like an RDBMS, an external service like a B2B exchange, a repository like an LDAP database, or an XML Repository. Using the scenario of web based News Application, this sample application demonstrates the effective use of this pattern.
[url http://www.oracle.com/technology/sample_code/tech/java/j2ee/designpattern/dataaccesstier/index.html]Download the sample application to learn more about this pattern.
More Sample Applications are available at [url http://www.oracle.com/technology/sample_code/index.html]
http://www.oracle.com/technology/sample_code/index.html
Thanks,
Rajat
OTN Team

Hi
This is because you are not using the latest jdbc driver version. Either use the latest ojdbc14.jar downloadable from the location given in the readme(Oracle Database 10g (10.1.0.2.0) drivers),
Or simply comment this part in the code.
Also you may just replace the close method call with ods=null;
Hope this helps
Shrinivas

Design Pattern and ABAP Objects

Hello Friends,
I would like to know, if ABAP Objects can be used to do pattern oriented programming ?
For example GANG of four has provided almost more then 30 design pattern ( MVC, singelton, Obserable, FACADE,,,etc) can we implement patterns using ABAP ??
Many thanks
Haider Syed

Hi,
Take a look at the following site:
http://patternshare.org/
It has all the basic patterns from the GOF and a lot more. I can recommend the ones from Martin Fowler but be sure you start with the ones from the GOF.
All patterns are described by using UML so it's very easy to translate them into ABAP OO code.
Regarding your other question. For the observer pattern I used an interface which the SAP had already created if_cm_observer and created my own abstract observable class. The observable class is nearly a 100% copy of the java.util. one
regards
Thomas

Design Patterns w/o EJB

Greetings, I am attempting to build a JSF application while learning JSR 127 and a few of the J2EE design patterns. The problem that I am having is that I don't plan on using EJB/Spring with my project and many of the tutorials I have been able to find place a focus on the EJB/Spring implementation details which are both overkill for this project. That said, I want to learn the appropriate patterns to build a functional application without catching "pattern fever".
I have a general idea of some of the patterns I need to use to get from the presentation tier to the data tier, such as Business Delegate and Data Transfer Object. However, I'm not sure I understand how to use these in conjunction with the managed beans facility. Do the managed beans contain (as in composition) the Business Delegate objects? Or do I use a DTO to push the data from the managed bean to the Delegate? How much if any logic do I put in the managed beans if I'm using them in this fashion (or are they basically just fields and getter/setters)?
All comments or suggestions are sincerely appreciated,
Jon

Hi,
Have you taken a look at Java BluePrints Solutions Catalog:
https://blueprints.dev.java.net/bpcatalog/
The Solutions Catalog focuses on different topics specifically so that you can pick and choose which articles are most interesting to you.
-Larry

Design patterns implemented in java API

Similar Messages

Maybe you are looking for