Clark, Yeah good point. Okay I'm sold on Closable. Autoclosable would be much better, but for now we are retaining 1.6 compatibility and I suspect the use case of temporarily creating a producer would actually be a more rare case.
-Jay On Mon, Jan 27, 2014 at 9:29 AM, Clark Breyman <cl...@breyman.com> wrote: > re: "Using package to avoid ambiguity" - Unlike Scala, this is really > cumbersome in Java as it doesn't support package imports or import aliases, > so the only way to distinguish is to use the fully qualified path. > > re: Closable - it can throw IOException but is not required to. Same with > AutoCloseable (are J7-specific classes and methods permitted?). Closable > and AutoClosable are really nice in eliminating finally clauses. What to > do with a exception on close()? Log it, use it as a signal of environment > health and move on. If it happens too frequently, you know your process > environment is degraded and might need to fail over and restart. >
