 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | TO pattern | TO pattern 2006-04-17 - By Jin Chun
Back
Hmmm, I think this is an instance where the pattern has gone off track. It
would be better imho to separate out aggregations via the collections
interfaces, such as List as return values from the business layer directly
instead of introducing collection like behaviour (such as lists) in a business
oriented interface, transfer object or not, eg
public List getOrders();
Or using the 1.5 generics for stronger typing.
Just my 2 cents :-)
Thanks,
Jin
-- -- Original Message -- --
From: An interest list for Sun Java Center J2EE Pattern Catalog [J2EEPATTERNS
-INTEREST@(protected)]
Sent: 04/17/2006 12:34 AM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: TO pattern
An inner class is made static if it does not need to access member variables
in the enclosing class automatically. MutableOrdersTO and OrdersTO seem to
be independent and I guess hence MutableOrdersTO is a static inner class.
Thanks,
Dhawal Ogale
Solution Architect | Catalytic Software, Ltd.
Office: +91 8414.233300
Mobile: +91 98856.28282
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system
administrator - netops@(protected)
-- --Original Message-- --
From: An interest list for Sun Java Center J2EE Pattern Catalog
[mailto:J2EEPATTERNS-INTEREST@(protected)] On Behalf Of Sheetal Desai
Sent: Thursday, April 13, 2006 10:50 PM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: TO pattern
I was going thru the code for the MutableOrdersTO.
This is the TO pattern and I was wondering why MutableOrdersTO is static?
Other than the fact that it can be instantiated using
new OrdersTO.MutableOrdersTO();
public interface OrdersTO extends Serializable {
o
o public Iterator iterator();
o public int size();
o public boolean contains(Object o);
o public boolean containsAll(Collection c);
o public boolean equals(Object o);
o public int hashCode();
o public boolean isEmpty();
o public Object[] toArray();
o public Object[] toArray(Object[] a);
o
o static class MutableOrdersTO extends ArrayList
implements OrdersTO {
o }
o }
Will this result into the same OrdersTO for all the clients hat request it?
===================================================================Companion
Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
listserv@(protected)
===================================================================Companion
Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
===================================================================Companion
Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
