如何通过uisng BiWeekly库和Java创建和发送对现有事件的更新？

Question

我使用BiWeekly库创建VEVENT，然后使用Java Mail API发送它。一切正常，但我如何为现有事件创建一个更新，即当我收到VEVENT (也就是更新)时，它不会在日历中创建一个新事件，而是会更新一个现有事件？

我尝试以以下方式设置序列，event.setSequence(2)，但它不起作用。在接收电子邮件代理Lotus时，google邮件总是会创建新事件。

这是我创建和发送事件的代码：

try {
            String from = "email@example.com";
            String to = "email@example.com";
            Properties prop = new Properties();
            prop.setProperty("mail.transport.protocol", "smtp");
            prop.setProperty("mail.host", "smtp.example.com");
            prop.setProperty("mail.user", "email");
            prop.setProperty("mail.password", "");

            Session session = Session.getDefaultInstance(prop, null);

            // Define message
            MimeMessage message = new MimeMessage(session);
            message.addHeaderLine("method=REQUEST");
            message.addHeaderLine("charset=UTF-8");
            message.addHeaderLine("component=VEVENT");

            message.setFrom(new InternetAddress(from));
            message.addRecipient(Message.RecipientType.TO, new InternetAddress(to));
            message.setSubject("Message Subject");

            StringBuffer sb = new StringBuffer();


            /*EVENT START*/
            VEvent event = new VEvent();
            event.setUid("ANATOLYTARNAVSKY123");
            event.setDescription("Invitation Description");
            event.setSummary("Invitation Description");
            event.setOrganizer("anatolyt@gmail.com");
            event.setLocation("room");

            event.setSequence(sequence);


            Calendar start = Calendar.getInstance();
            start.add(Calendar.HOUR_OF_DAY, sequence + 2);
            Calendar end = Calendar.getInstance();
            end.add(Calendar.HOUR_OF_DAY, sequence + 2);

            event.setDateStart(start.getTime());
            event.setDateEnd(end.getTime());
            icals.addEvent(event);

            WriterChainText text = Biweekly.write(icals);
            String result = text.go(); 


            System.out.println(result);
            /*EVENT END*/

            StringBuffer buffer = sb.append(result);


            // Create the message part
            BodyPart messageBodyPart = new MimeBodyPart();

            // Fill the message
            messageBodyPart.setHeader("Content-Class", "urn:content-classes:calendarmessage");
            messageBodyPart.setHeader("Content-ID", "calendar_message");
            messageBodyPart.setDataHandler(new DataHandler( new ByteArrayDataSource(buffer.toString(), "text/calendar")));// very important

            // Create a Multipart
            Multipart multipart = new MimeMultipart();

            // Add part one
            multipart.addBodyPart(messageBodyPart);

            // Put parts in message
            message.setContent(multipart);

            // send message
            Transport.send(message);
        } catch (MessagingException me) {
            me.printStackTrace();
        } catch (Exception ex) {
            ex.printStackTrace();
        }

在这里，我将对用于发送邀请的代码进行迭代，

• 第二名：由@Michael通知的财产

提前谢谢你。

更新1：

这是由我的代码和BiWeekly库生成的第一个和第二个VEVENT：

创建事件- VEVENT数据仅限

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Michael Angstadt//biweekly 0.4.3//EN
METHOD:REQUEST
BEGIN:VEVENT
DTSTAMP:20151113T100301Z
UID:ANATOLYTARNAVSKY123
DESCRIPTION:Invitation Description
SUMMARY:Invitation Description
ORGANIZER:mailto:anatolyt@example.com
LOCATION:room
SEQUENCE:0
DTSTART:20151113T120301Z
DTEND:20151113T120301Z
END:VEVENT
END:VCALENDAR

更新事件- VEVENT数据仅限

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Michael Angstadt//biweekly 0.4.3//EN
METHOD:REQUEST
BEGIN:VEVENT
DTSTAMP:20151113T100333Z
UID:ANATOLYTARNAVSKY123
DESCRIPTION:Invitation Description
SUMMARY:Invitation Description
ORGANIZER:mailto:anatolyt@example.com
LOCATION:room
SEQUENCE:1
DTSTART:20151113T130333Z
DTEND:20151113T130333Z
END:VEVENT
END:VCALENDAR

更新2

当我发出第一次和第二次邀请时，我在gmail上收到以下电子邮件：

​

​

由于某些隐私问题，删除了跟踪路径的完整原始电子邮件内容如下：

创建事件-没有路由部件的完整电子邮件

Date: Sat, 14 Nov 2015 08:03:47 -0700
From: anatolyt@example.com
To: anatolyt@gmail.com
Message-ID: *****
Subject: Escape Room Invitation
MIME-Version: 1.0
Content-Type: multipart/mixed; 
    boundary="----=_Part_0_451111351.1447513426727"
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15111415-0021-0000-0000-000004CDC424

method=REQUEST
charset=UTF-8
component=VEVENT

------=_Part_0_451111351.1447513426727
Content-Type: text/calendar; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:calendarmessage
Content-ID: calendar_message

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Michael Angstadt//biweekly 0.4.3//EN
METHOD:REQUEST
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTAMP:20151114T150346Z
UID:anatolyt@example.com
STATUS:CONFIRMED
DESCRIPTION:Invitation Description
SUMMARY:Invitation Summary
ORGANIZER:mailto:anatolyt@example.com
LOCATION:Escape room
TRANSP:OPAQUE
CREATED:20151114T150346Z
LAST-MODIFIED:20151114T150346Z
SEQUENCE:0
DTSTART:20151114T170346Z
DTEND:20151114T170346Z
END:VEVENT
END:VCALENDAR

------=_Part_0_451111351.1447513426727--

更新事件-没有路由部件的完整电子邮件

Date: Sat, 14 Nov 2015 08:05:06 -0700
From: anatolyt@example.com
To: anatolyt@gmail.com
Message-ID: *****
Subject: Escape Room Invitation
MIME-Version: 1.0
Content-Type: multipart/mixed; 
    boundary="----=_Part_0_451111351.1447513506015"
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15111415-0029-0000-0000-000004D409DF

method=REQUEST
charset=UTF-8
component=VEVENT

------=_Part_0_451111351.1447513506015
Content-Type: text/calendar; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:calendarmessage
Content-ID: calendar_message

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Michael Angstadt//biweekly 0.4.3//EN
METHOD:REQUEST
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTAMP:20151114T150505Z
UID:anatolyt@example.com
STATUS:CONFIRMED
DESCRIPTION:Invitation Description
SUMMARY:Invitation Summary
ORGANIZER:mailto:anatolyt@example.com
LOCATION:Escape room
TRANSP:OPAQUE
CREATED:20151114T150505Z
LAST-MODIFIED:20151114T150505Z
SEQUENCE:1
DTSTART:20151114T180505Z
DTEND:20151114T180505Z
END:VEVENT
END:VCALENDAR

------=_Part_0_451111351.1447513506015--

Google 3看起来在Lotus上正确工作，但是Google仍然不识别更新事件。

更新4-解决方案

正如@arnaudq所写的，我错过了ATTENDEE属性来创建一个Google来识别更新事件。下面是一个如何做到这一点的例子：

        VEvent event = new VEvent();
        ...
        Attendee attendee = new Attendee("Anatoly Tarnavsky", "anatolyt@gmail.com");
        attendee.setRsvp(true);
        attendee.setRole(Role.CHAIR);
        attendee.setParticipationStatus(ParticipationStatus.CONFIRMED);
        ...
        event.setProperty(attendee);

Answer 1

您的代码似乎没有明确地设置UID属性。因此，库可能会为您生成一个新的库。

UID属性是标识此VEVENT的其他属性之一。因此，您的更新将包含与先前发送的原始事件相同的UID值。

您还至少丢失了一个与会者属性。与会者之一应该将其值设置为与接收邀请的gmail电子邮件地址相对应的mailto uri。

Answer 2

尝试向VEVENT组件添加最后修改的属性。你似乎做好了所有其他事情--保持UID的一致性和递增顺序。