J2EE design patterns /

By:

Crawford, William

Contributor(s):

Kaplan, Jonathan

Material type: Text

TextPublication details: Beijing ; Farnham : O'Reilly, 2003.Description: 1 online resource (xvi, 350 pages) : illustrationsSubject(s):

Additional physical formats: Print version:: J2EE design patterns.DDC classification:

005.71262

LOC classification:

QA76.73.J38 C74 2003

Action note:

digitized 2010 HathiTrust Digital Library committed to preserve

Summary: Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes. It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns. A software design pattern can be identified as "a recurring solution to a recurring problem." Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another? But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started. Crawford and Kaplan's J2EE Design Patterns approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software. They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability. J2EE Design Patterns offers extensive coverage of the five problem areas enterprise developers face: Maintenance (Extensibility) Performance (System Scalability) Data Modeling (Business Object Modeling) Transactions (process Modeling) Messaging (Interoperability)And with its careful balance between theory and practice, J2EE Design Patterns will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience

Tags from this library: No tags from this library for this title. Log in to add tags.

Average rating: 0.0 (0 votes)

Holdings
Item type	Current library	Collection	Call number	Status	Barcode
Books	Botho University Botswana Open Shelves	Information Technology	005.71262 CRA (Browse shelf(Opens below))	Available	BC-LIB13043
Books	Botho University Botswana Open Shelves	Information Technology	005.71262 CRA (Browse shelf(Opens below))	Available	BC-LIB13041
Books	Botho University Botswana Open Shelves	Information Technology	005.71262 CRA (Browse shelf(Opens below))	Available	BC-LIB13040
Books	Botho University Botswana Open Shelves	Information Technology	005.71262 CRA (Browse shelf(Opens below))	Available	BC-LIB13039

Includes bibliographical references and index.

Use copy Restrictions unspecified star MiAaHDL

Architects of buildings and architects of software have more in common than most people think. Both professions require attention to detail, and both practitioners will see their work collapse around them if they make too many mistakes. It's impossible to imagine a world in which buildings get built without blueprints, but it's still common for software applications to be designed and built without blueprints, or in this case, design patterns. A software design pattern can be identified as "a recurring solution to a recurring problem." Using design patterns for software development makes sense in the same way that architectural design patterns make sense--if it works well in one place, why not use it in another? But developers have had enough of books that simply catalog design patterns without extending into new areas, and books that are so theoretical that you can't actually do anything better after reading them than you could before you started. Crawford and Kaplan's J2EE Design Patterns approaches the subject in a unique, highly practical and pragmatic way. Rather than simply present another catalog of design patterns, the authors broaden the scope by discussing ways to choose design patterns when building an enterprise application from scratch, looking closely at the real world tradeoffs that Java developers must weigh when architecting their applications. Then they go on to show how to apply the patterns when writing realworld software. They also extend design patterns into areas not covered in other books, presenting original patterns for data modeling, transaction / process modeling, and interoperability. J2EE Design Patterns offers extensive coverage of the five problem areas enterprise developers face: Maintenance (Extensibility) Performance (System Scalability) Data Modeling (Business Object Modeling) Transactions (process Modeling) Messaging (Interoperability)And with its careful balance between theory and practice, J2EE Design Patterns will give developers new to the Java enterprise development arena a solid understanding of how to approach a wide variety of architectural and procedural problems, and will give experienced J2EE pros an opportunity to extend and improve on their existing experience

Electronic reproduction. [Place of publication not identified] : HathiTrust Digital Library, 2010. MiAaHDL

Master and use copy. Digital master created according to Benchmark for Faithful Digital Reproductions of Monographs and Serials, Version 1. Digital Library Federation, December 2002. MiAaHDL