I logged the following tickets: https://fedorahosted.org/augeas/ticket/212 https://fedorahosted.org/augeas/ticket/213
They specifically deal with the Java Binding and the net.augeas.Augeas class. One identifies a bug in that no finalize() method exists which will result in AugPtr being implicitly cleaned up and released during Java GC in the event the implementation using the Java Binding fails to call the Augeas.close() method explicitly. The other reveals that the API Java-Doc for the close() method does not appear to be accurate as it indicates that it will write pending changes to disk. As these issues drastically impact a Java implementation which fails to explicitly call the close() method, I would really like to see these addressed for the next release. Let me know if you need anything else from me. -- Larry O'Leary <[email protected]> Red Hat, Inc. _______________________________________________ augeas-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/augeas-devel
