Sample code for 30+ languages & platforms
Java

Add an Attachment from a BinData Object

See more Email Object Examples

Demonstrates the Chilkat Email.AddAttachmentBd method, which adds an attachment using the contents of a BinData object. The first argument is the attachment filename, the second is the BinData, and the third is the content type — if empty, it is inferred from the filename extension. This example loads a PDF into a BinData and attaches it.

Background: BinData is Chilkat's container for raw binary data. Attaching from a BinData is the right approach when the file's bytes are already in memory — generated on the fly, downloaded, or read from a database — rather than sitting on disk (which would use AddFileAttachment). Chilkat Base64-encodes the bytes into the message automatically.

Chilkat Java Downloads

Chilkat2 Java
import com.chilkatsoft.chilkat2.BinData;
import com.chilkatsoft.chilkat2.ChilkatException;
import com.chilkatsoft.chilkat2.Email;

public class ChilkatExample {

    public static void main(String[] args) {
        // Demonstrates the AddAttachmentBd method, which adds an attachment using the contents of a
        // BinData object.  The first argument is the attachment filename, the second is the BinData
        // object, and the third is the content type (inferred from the filename extension if empty).

        Email email = new Email();
        email.setSubject("Attach from BinData");
        email.setBody("Please see the attached file.");

        // Load a file into a BinData object, then attach it.
        BinData bd = new BinData();
        try {
            bd.loadFile("qa_data/attachments/report.pdf");

            email.addAttachmentBd("report.pdf", bd, "application/pdf");
        } catch (ChilkatException e) {
            System.out.println(e.getLastErrorText());
            return;
        }

        System.out.println("NumAttachments = " + email.getNumAttachments());

        // Note: The path "qa_data/attachments/report.pdf" is a relative local filesystem path,
        // relative to the current working directory of the running application.
    }
}