[
https://issues.apache.org/jira/browse/STORM-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111273#comment-15111273
]
ASF GitHub Bot commented on STORM-1227:
---------------------------------------
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/1030#issuecomment-173704553
> I will post a link when I have an example.
new
[staticmocking](https://github.com/d2r/storm/tree/56d48faac918123af46f1e021e38549fa6a4cf6c/storm-core/src/jvm/org/apache/storm/testing/staticmocking)
package
See example methods under test:
[Utils](https://github.com/d2r/storm/blob/56d48faac918123af46f1e021e38549fa6a4cf6c/external/storm-hbase/src/main/java/org/apache/storm/hbase/common/Utils.java)
Here is a (clojure) example of
[usage](https://github.com/d2r/storm/blob/56d48faac918123af46f1e021e38549fa6a4cf6c/storm-core/test/clj/org/apache/storm/logviewer_test.clj#L372-L387).
This will all eventually be Java, and it would use a try-with-resources syntax
in place of the `with-open`.
If this seems like a good pattern to follow, we can add it to the
[migration
guidelines](https://cwiki.apache.org/confluence/display/STORM/Java+Migration+Guidelines).
> port backtype.storm.config to java
> ----------------------------------
>
> Key: STORM-1227
> URL: https://issues.apache.org/jira/browse/STORM-1227
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Zhuo Liu
> Labels: java-migration, jstorm-merger
>
> port backtype.storm.config to java. There are some parts of this that for
> convince sake may need to stay in clojure, or have clojure equivalents.
> The code that turns Config.* into clojure constants needs to stay, and
> reading the config may need to stay in clojure until we can cleanup all of
> the places it is used to not need the migration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
