Re: parentCommEventId is never saved in CommunicationEvent entity for storeIncomingEmail service

2009-05-09 Thread Divesh Dutta
After more testing I found that messageId is saved in CommunicationEvent only when I send mails through Party Component. But when I send mail through Marketing component using Contact list feature, then messageId is not saved in CommunicationEvent entity. Thanks -- Divesh Divesh Dutta

Re: parentCommEventId is never saved in CommunicationEvent entity for storeIncomingEmail service

2009-05-09 Thread Ashish Vijaywargiya
Thanks for the update, Divesh. I would like to ask you a question here: Is it desirable behavior or are you planning to submit the patch for Contact List where we don't see any info about messageId ? -- Ashish On Sat, May 9, 2009 at 2:00 PM, Divesh Dutta divesh.du...@hotwaxmedia.comwrote:

Re: parentCommEventId is never saved in CommunicationEvent entity for storeIncomingEmail service

2009-05-08 Thread Divesh Dutta
Intersting to see that still no views on this imp issue. But we had good discussion for webtools login page ;-) . Here looking more into this code and testing , I found that messageId for outgoing mails are not saved in CommunicationEvent entity. If some one is getting the same behaviour

Re: parentCommEventId is never saved in CommunicationEvent entity for storeIncomingEmail service

2009-05-08 Thread BJ Freeman
andy had done some work on the communication even recently. you might put this over in the dev list to have him see it since I don't think he reads the user list. Divesh Dutta sent the following on 5/8/2009 4:54 AM: Intersting to see that still no views on this imp issue. But we had good

parentCommEventId is never saved in CommunicationEvent entity for storeIncomingEmail service

2009-05-07 Thread Divesh Dutta
Hello all, I was tracing and debugging the code in storeIncomingEmail service in CommunicationEventServices.java (on rev. 772658). Steps I followed: -- Sent an outgoing mail from system . (say from abc@gmail.com) -- Then replied to this email id (incoming email) So reffering line no. 599