MethodHandles.Lookup lookup = MethodHandles.lookup();
MethodType mt = MethodType.methodType(boolean.class, int.class);
MethodHandle handle = lookup.findVirtual(Connection.class, "isValid", mt);
// ...
boolean isValid = (boolean) handle.invokeExact(connection, timeout);
The findVirtual() call abo
On Wed, Mar 29, 2017 at 8:28 AM, Matt Sicker wrote:
> Using a MethodHandle lookup ahead of time to create a fast invocation proxy
> and using that where available would make sense. I don't like the idea of
> catching errors like that.
>
Hi Matt,
Thank you for the tip. Do you have an example han
Using a MethodHandle lookup ahead of time to create a fast invocation proxy
and using that where available would make sense. I don't like the idea of
catching errors like that.
On 29 March 2017 at 01:53, Gary Gregory wrote:
> Hi All:
>
> The method:
>
> org.apache.commons.dbcp2.DelegatingConnect
Github user asfgit closed the pull request at:
https://github.com/apache/commons-compress/pull/17
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featur
Github user bodewig commented on the issue:
https://github.com/apache/commons-compress/pull/17
Great, many thanks,
I've just found
https://people.freebsd.org/~kientzle/libarchive/man/cpio.5.txt states
> The CRC format is identical to the new ASCII format described in
Github user coveralls commented on the issue:
https://github.com/apache/commons-compress/pull/17
[](https://coveralls.io/builds/10826707)
Coverage increased (+0.001%) to 84.176% when pulling
**dd1ec97f687c462f
GitHub user dcollin opened a pull request:
https://github.com/apache/commons-compress/pull/17
CPIO crc overflow resolved for large files
When unpacking a CPIO file containing a large file the crc check will
overflow and throw an IOException("CRC Error...").
Did not find
You can run a verification SQL instead. So I guess doing nothing would be fine
as well, as the verification SQL (on borrow) could be configured instead.
Other methods which do a round trip to the database can be used as well (for
example setAutocommit() on some drivers).
Gruss
Bernd
--
http://b