[
https://issues.apache.org/jira/browse/QPID-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598290#action_12598290
]
Rafael H. Schloming commented on QPID-1018:
-------------------------------------------
I can see why it is useful to have a uniform way for the configuration object
to internally fetch its values, however I don't see the point of exposing enums
as part of the interface to the code. Is there some reason I'm missing that the
natural interface, i.e. Configuration.getFoo() is inadequate? So far I don't
see anything that Configuration.BLAH.getValue() provides for the calling code
beyond Configuration.getBlah(), whereas a natural set of getters can easily be
turned into an interface or abstract class which can be swapped out wholesale
with whatever mechanism we want behind it.
> Client properties centralization
> ---------------------------------
>
> Key: QPID-1018
> URL: https://issues.apache.org/jira/browse/QPID-1018
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M3
> Reporter: Arnaud Simon
> Assignee: Arnaud Simon
> Fix For: M3
>
>
> Currently client props are distributed all over the code. It would be more
> coherent and easy to document if we centralized them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
