-
Notifications
You must be signed in to change notification settings - Fork 10
[WIP] Feature/properties in boundary definitions #113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
f2fbee3
c7dd8a2
9d68b3d
7288da7
5aad601
c2f8beb
1b974b6
5f2e739
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -154,6 +154,8 @@ protected void setWPDElement(WinerysPropertiesDefinition res) { | |
| } | ||
|
|
||
| protected void setWPDNamespace(WinerysPropertiesDefinition res) { | ||
| // bo be overridden by subclasses willing to use getWinerysPropertiesDefinition() | ||
|
||
| // Template method pattern | ||
| } | ||
|
|
||
| @NonNull | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could actually implement it on this level since the methods are identical. To be able to use the
getTargetNamespacemethod, you can check if the current object is aninstance of HasTargetNamespaceand cast it. Otherwise, you could use a default namespace.