Skip to content

Commit 01a52d0

Browse files
committed
docs(config): fix reference.conf PBFT naming comment
Only committee.pBFTExpireNum has the JavaBean naming mismatch. Other PBFT keys (PBFTEnable, PBFTPort) start with uppercase and auto-bind correctly via ConfigBeanFactory.
1 parent 5477171 commit 01a52d0

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

common/src/main/resources/reference.conf

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,12 @@
2424
#
2525
# Key naming rules (required for ConfigBeanFactory auto-binding):
2626
# - Use standard camelCase: maxConnections, syncFetchBatchNum, etc.
27-
# - Do NOT use consecutive uppercase letters at the start: "pBFTExpireNum"
28-
# breaks binding because JavaBean spec converts setPBFTExpireNum -> key
29-
# "PBFTExpireNum" (capital P), not "pBFTExpireNum" (lowercase p).
30-
# - Currently 4 keys violate this rule (all PBFT-related): allowPBFT,
31-
# pBFTExpireNum, httpPBFTEnable, httpPBFTPort. These are handled manually
32-
# in the bean classes with documented workarounds.
27+
# - Keys starting with lowercase then consecutive uppercase break binding:
28+
# "pBFTExpireNum" -> setPBFTExpireNum -> property "PBFTExpireNum" (capital P),
29+
# mismatches config key "pBFTExpireNum" (lowercase p).
30+
# - Only committee.pBFTExpireNum has this issue, handled manually in
31+
# CommitteeConfig. Other PBFT keys (PBFTEnable, PBFTPort) start with
32+
# uppercase and auto-bind correctly.
3333
# =============================================================================
3434

3535
net {

0 commit comments

Comments
 (0)