Home
About
Blog
Products
Forum
Support
Contact
Sunbelt Computer Software
PL/B Language Development and Support
Home
About
Blog
Products
Forum
Support
Contact
Design-Patterns/structural/composite.java at main · LinuxDevil/Design-Patterns · GitHub
Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
View all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Search
/
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
LinuxDevil
/
Design-Patterns
Public
Notifications
You must be signed in to change notification settings
Fork
0
Star
3
Code
Issues
0
Pull requests
0
Actions
Projects
Security and quality
0
Insights
Additional navigation options
Code
Issues
Pull requests
Actions
Projects
Security and quality
Insights
Files
Expand file tree
main
Breadcrumbs
Design-Patterns
/
structural
/
composite.java
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
134 lines (109 loc) · 3.83 KB
main
Breadcrumbs
Design-Patterns
/
structural
/
composite.java
Copy path
Top
File metadata and controls
Code
Blame
134 lines (109 loc) · 3.83 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
// Composite Design Pattern
// ========================
// The Composite pattern lets clients treat individual objects and compositions
// of objects uniformly.
// Structure
// ---------
// The Composite pattern consists of three types of objects: the component,
// the leaf, and the composite. A component declares the interface for objects
// in the composition, and implements default behavior for the interface common
// to all classes, as appropriate. The base Component class can declare an
// interface for accessing and managing its child components. (optional)
// A leaf represents the end objects of a composition. A leaf has no children.
// It defines behavior for primitive objects in the composition. A composite
// defines behavior for components having children. It stores child components
// and implements child-related operations in the Component interface.
// Using the Composite pattern makes sense only when the core
// model of your app can be represented as a tree.
// Problem:
// --------
// Imagine that you are creating an online store. The store sells products
// and services. Each product or service can be sold individually or as part
// of a bundle. For example, a customer can buy a book, a music CD, and a
// video DVD as a bundle. The customer can also buy each of these items
// individually.
// The Composite pattern lets you treat individual objects and compositions
// uniformly. The client code can work with simple or complex elements without
// depending on their concrete classes.
import
java
.
util
.
ArrayList
;
import
java
.
util
.
List
;
// Component
public
abstract
class
Product
{
public
abstract
double
getPrice
();
}
// Leaf
public
class
Book
extends
Product
{
private
String
title
;
private
double
price
;
public
Book
(
String
title
,
double
price
) {
this
.
title
=
title
;
this
.
price
=
price
;
}
public
double
getPrice
() {
return
price
;
}
}
// Leaf
public
class
MusicCD
extends
Product
{
private
String
title
;
private
double
price
;
public
MusicCD
(
String
title
,
double
price
) {
this
.
title
=
title
;
this
.
price
=
price
;
}
public
double
getPrice
() {
return
price
;
}
}
// Leaf
public
class
VideoDVD
extends
Product
{
private
String
title
;
private
double
price
;
public
VideoDVD
(
String
title
,
double
price
) {
this
.
title
=
title
;
this
.
price
=
price
;
}
public
double
getPrice
() {
return
price
;
}
}
// Composite
public
class
Bundle
extends
Product
{
private
String
name
;
private
List
<
Product
>
products
=
new
ArrayList
<>();
public
Bundle
(
String
name
,
Product
...
products
) {
this
.
name
=
name
;
for
(
Product
product
:
products
) {
this
.
products
.
add
(
product
);
}
}
public
void
addProduct
(
Product
product
) {
products
.
add
(
product
);
}
public
void
removeProduct
(
Product
product
) {
products
.
remove
(
product
);
}
public
double
getPrice
() {
double
totalPrice
=
0
;
for
(
Product
product
:
products
) {
totalPrice
+=
product
.
getPrice
();
}
return
totalPrice
;
}
}
// Client code
public
class
OnlineStore
{
public
static
void
main
(
String
[]
args
) {
Book
book
=
new
Book
(
"The Lord of the Rings"
,
20.0
);
MusicCD
musicCD
=
new
MusicCD
(
"Abbey Road"
,
15.0
);
VideoDVD
videoDVD
=
new
VideoDVD
(
"The Godfather"
,
25.0
);
Bundle
bundle
=
new
Bundle
(
"Entertainment Bundle"
,
book
,
musicCD
,
videoDVD
);
System
.
out
.
println
(
"Total price: "
+
bundle
.
getPrice
());
}
}
// Use the Composite pattern only when your core model can be
// represented as a tree.
// Use the Composite pattern when you want clients to be able to
// ignore the difference between compositions of objects and individual
// objects. Clients will treat all objects in the composite structure
// uniformly.
You can’t perform that action at this time.