[JBoss JIRA] Closed: (JBMAIL-130) clusterize locks table
by Andrew Oliver (JIRA)
[ http://jira.jboss.com/jira/browse/JBMAIL-130?page=all ]
Andrew Oliver closed JBMAIL-130.
--------------------------------
Fix Version/s: (was: 1.0-RC1)
Resolution: Won't Fix
Assignee: (was: Andrew Oliver)
> clusterize locks table
> ----------------------
>
> Key: JBMAIL-130
> URL: http://jira.jboss.com/jira/browse/JBMAIL-130
> Project: JBoss Mail ** Closed - moved to http://buni.org **
> Issue Type: Feature Request
> Components: POP
> Affects Versions: 1.0-RC1
> Reporter: Andrew Oliver
>
> Locks table needs to have some kind of instance id and the thread id. Locks should be deleted or at runtime if they are from the same instance upon startup and if that thread is known to be gone and from the owning instance. Meaning if server A owns the lock and the same user connects to server A, server A can check the thread pool and see if the same thread ID is still in existence with the same userID. . . IF not then the lock can be safely ignored/deleted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Closed: (JBMAIL-133) Can't build and run under IBM SDK
by Andrew Oliver (JIRA)
[ http://jira.jboss.com/jira/browse/JBMAIL-133?page=all ]
Andrew Oliver closed JBMAIL-133.
--------------------------------
Resolution: Won't Fix
Assignee: (was: Andrew Oliver)
> Can't build and run under IBM SDK
> ---------------------------------
>
> Key: JBMAIL-133
> URL: http://jira.jboss.com/jira/browse/JBMAIL-133
> Project: JBoss Mail ** Closed - moved to http://buni.org **
> Issue Type: Task
> Components: SMTP, POP, IMAP
> Affects Versions: 1.0-M4
> Environment: All Linux distributions running IBM SDK 1.4 and 1.5.
> This will also be observed on all platforms not running a Sun SDK
> Reporter: Ulrich Romahn
>
> The SSL support of all three protocols (IMAP, POP, SMTP) will not be working on a non-Sun SDK.
> The "offending" line is:
> java.security.Security.addProvider( new com.sun.net.ssl.internal.ssl.Provider());
> and is located in the following three files:
> - org.jboss.mail.imap4.handlers.CmdSTARTTLS.java
> - org.jboss.mail.smtp.handlers.CmdSTARTTLS.java
> - org.jboss.mail.pop3.handlers.CmdSTLS
> This should be changed, if possible.
> I am working on a possible solution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Closed: (JBMAIL-142) ICalendar export/import
by Andrew Oliver (JIRA)
[ http://jira.jboss.com/jira/browse/JBMAIL-142?page=all ]
Andrew Oliver closed JBMAIL-142.
--------------------------------
Fix Version/s: (was: 1.0-RC1)
Resolution: Won't Fix
Assignee: (was: Aron Sogor)
> ICalendar export/import
> -----------------------
>
> Key: JBMAIL-142
> URL: http://jira.jboss.com/jira/browse/JBMAIL-142
> Project: JBoss Mail ** Closed - moved to http://buni.org **
> Issue Type: Sub-task
> Affects Versions: 1.0-RC1
> Reporter: Aron Sogor
>
> Import ICAL/VCAL via WebDAV( fancy way to say Http PUT/GET). Sunbird/Firfox/ThunderBird/Mozilla Calendar, Mac ICal(I think needs checking) and OSAF Chandler all share caldars over webdav, by uploading their file via an http put and getting/refreshing their caledar with an HTTP GET.
> Enable exporting users calendar hence meaning user's invites to ICal/VCal format.
> - Each entry exported useing GUIDs for each calendar entry.
> - if the entry cancelled do not export it.
> Parse the uploaded Ical with Ical4j and compare each entry (ID by GUID):
> -if the GUID not found the entry is new create a personal event as organizer and invite itself.
> -if the GUID known comapre each field if that has changed, if needed update entry*
> -if GUID found but event canceled do nothing.
> * according the ical spec if the event changes they should/could change the version/sequence attribute. That is not done by Mozilla.
> if there is a version/sequence attribute compare it with current version, if it is a stale/old record skip the update.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months