[jira] Created: (JAMES-1139) The specific implementation of the X509 algorithm used for the SSL certificates should be configurable

The specific implementation of the X509 algorithm used for the SSL certificates should be configurable -- Key: JAMES-1139 URL:

[jira] Updated: (JAMES-1139) The specific implementation of the X509 algorithm used for the SSL certificates should be configurable

[ https://issues.apache.org/jira/browse/JAMES-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilo Goetz updated JAMES-1139: --- Attachment: james-X509-patch.txt Patch against the current trunk, tested to the best of my

[jira] Commented: (JAMES-1139) The specific implementation of the X509 algorithm used for the SSL certificates should be configurable

[ https://issues.apache.org/jira/browse/JAMES-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934877#action_12934877 ] Thilo Goetz commented on JAMES-1139: Is there any documentation that needs updating as

[jira] Commented: (JAMES-1139) The specific implementation of the X509 algorithm used for the SSL certificates should be configurable

[ https://issues.apache.org/jira/browse/JAMES-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934902#action_12934902 ] Eric Charles commented on JAMES-1139: - For the documentation, there is

svn commit: r1038274 - in /james/server/trunk: container-spring/src/main/config/examples/smtpserver.xml netty-socket/src/main/java/org/apache/james/socket/netty/AbstractConfigurableAsyncServer.java

Author: norman Date: Tue Nov 23 18:51:16 2010 New Revision: 1038274 URL: http://svn.apache.org/viewvc?rev=1038274view=rev Log: Allow to specify the algorithm for TLS to be able to use secure sockets in non SUN JVM's. See JAMS-1139. Thx to Thilo Goetz for the patch! Modified:

[jira] Resolved: (JAMES-1139) The specific implementation of the X509 algorithm used for the SSL certificates should be configurable

[ https://issues.apache.org/jira/browse/JAMES-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Maurer resolved JAMES-1139. -- Resolution: Fixed applied to trunk.. Thx for the patch! The specific implementation of the

[jira] Created: (IMAP-232) Allow to read Content via InputStream as optional implementation

Allow to read Content via InputStream as optional implementation Key: IMAP-232 URL: https://issues.apache.org/jira/browse/IMAP-232 Project: JAMES Imap Issue Type: Improvement

svn commit: r1038286 - in /james/imap/trunk: mailbox/src/main/java/org/apache/james/mailbox/ store/src/main/java/org/apache/james/mailbox/store/ store/src/main/java/org/apache/james/mailbox/store/stre

Author: norman Date: Tue Nov 23 19:13:12 2010 New Revision: 1038286 URL: http://svn.apache.org/viewvc?rev=1038286view=rev Log: Allow to read Content via InputStream a optional implementation. See IMAP-232 Added:

[jira] Commented: (IMAP-232) Allow to read Content via InputStream as optional implementation

[ https://issues.apache.org/jira/browse/IMAP-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934982#action_12934982 ] Norman Maurer commented on IMAP-232: Add InputStreamContent interface which extent

[jira] Resolved: (IMAP-232) Allow to read Content via InputStream as optional implementation

[ https://issues.apache.org/jira/browse/IMAP-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Norman Maurer resolved IMAP-232. Resolution: Fixed Allow to read Content via InputStream as optional implementation

[jira] Created: (IMAP-233) jpa mapping files

jpa mapping files - Key: IMAP-233 URL: https://issues.apache.org/jira/browse/IMAP-233 Project: JAMES Imap Issue Type: New Feature Environment: JPA Reporter: Mohammad Naghavi Trying to move all hard

[jira] Updated: (IMAP-233) jpa mapping files

[ https://issues.apache.org/jira/browse/IMAP-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Naghavi updated IMAP-233: -- Attachment: jpa_metadata.patch My first try to move the annotations out of classes jpa mapping