* code verbose. Whenever following this advice, you should check whether {@code Stream} could be
 * adopted more comprehensively in your code; the end result may be quite a bit simpler.
 *
 * <h3>See also</h3>
 *
 * <p>See the Guava User Guide article on <a href=
 * "https://github.com/google/guava/wiki/OrderingExplained">{@code Ordering}</a>.
 *
 * @author Jesse Wilson

 * were never supposed to be seen on the wire. That assumption was dropped, some say mistakenly, in
 * later RFCs with the apparent aim of making IPv4-to-IPv6 transition simpler.
 *
 * <p>Technically one <i>can</i> create a 128bit IPv6 address with the wire format of a "mapped"
 * address, as shown above, and transmit it in an IPv6 packet header. However, Java's InetAddress

        // Verify a sample of encrypted messages can be decrypted (to avoid extensive decryption that might fail)
        int sampleSize = Math.min(5, encrypted.size());
        for (int i = 0; i < sampleSize; i++) {
            try {
                byte[] decrypted = context.decryptMessage(encrypted.get(i));
                assertArrayEquals(messages.get(i).getBytes(), decrypted, "Sample message " + i + " should decrypt correctly");

   * between elements will be made, but the order in which those pairs of elements are passed to the
   * consumer is <i>not</i> defined.
   *
   * <p>Note that many usages of this method can be replaced with simpler calls to {@link #zip}.
   * This method behaves equivalently to {@linkplain #zip zipping} the stream elements into
   * temporary pair objects and then using {@link Stream#forEach} on that stream.
   *

            assertArrayEquals(data, readData, "File content should match");
        }
    }

    @Test
    void testSimpleMultipleFiles() throws Exception {
        // Test creating multiple files sequentially (simpler than concurrent access)
        for (int i = 0; i < 3; i++) {
            SmbFile file = new SmbFile(baseUrl + "shared/multi" + i + ".txt", context);
            String content = "Content for file " + i;

 * were never supposed to be seen on the wire. That assumption was dropped, some say mistakenly, in
 * later RFCs with the apparent aim of making IPv4-to-IPv6 transition simpler.
 *
 * <p>Technically one <i>can</i> create a 128bit IPv6 address with the wire format of a "mapped"
 * address, as shown above, and transmit it in an IPv6 packet header. However, Java's InetAddress

  private static final class NavigableAsMapView<
          K extends @Nullable Object, V extends @Nullable Object>
      extends AbstractNavigableMap<K, V> {
    /*
     * Using AbstractNavigableMap is simpler than extending SortedAsMapView and rewriting all the
     * NavigableMap methods.
     */

    private final NavigableSet<K> set;
    private final Function<? super K, V> function;

  private static final class NavigableAsMapView<
          K extends @Nullable Object, V extends @Nullable Object>
      extends AbstractNavigableMap<K, V> {
    /*
     * Using AbstractNavigableMap is simpler than extending SortedAsMapView and rewriting all the
     * NavigableMap methods.
     */

    private final NavigableSet<K> set;
    private final Function<? super K, V> function;

                });
        emlExtractor = container.getComponent("emlExtractor");
    }

    public void test_getText() throws IOException {
        try (final InputStream in = ResourceUtil.getResourceAsStream("extractor/eml/sample1.eml")) {
            ExtractData data = emlExtractor.getText(in, null);
            final String content = data.getContent();
            logger.info(content);
            assertTrue(content.contains("プレイステーション"));

Shinsuke Sugaya <******@****.***> 1452930635 +0900