[JBoss JIRA] Created: (JBAS-6192) mail-ra call getNewMessages on pop3 folder, which always return false
by peter andersen (JIRA)
mail-ra call getNewMessages on pop3 folder, which always return false
---------------------------------------------------------------------
Key: JBAS-6192
URL: https://jira.jboss.org/jira/browse/JBAS-6192
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.3.GA
Environment: Mac os, java 1.5
Reporter: peter andersen
Assignee: Jesper Pedersen
The
org.jboss.resource.adapter.mail.inflow.MailFolder calls javax.mail.Folder.hasNewMessages() to check for new messages.
POP3Folder instances allways return false on this request, see:
http://java.sun.com/products/javamail/javadocs/com/sun/mail/pop3/POP3Fold...
A quick fix/work around:
public Message[] getNewMessages()
throws Exception
{
Message msgs[] = {};
/* This does not seem to be the most reliable new msg check. This should
probably be unread msgs with the msgs marked as read on successful
delivery.
*/
if( folder.hasNewMessages() )
{
int newCount = folder.getNewMessageCount();
int msgCount = folder.getMessageCount();
msgs = folder.getMessages(msgCount - newCount + 1, msgCount);
return msgs;
}
// Special handling of POP3, hasNewMessages() always returns false.
if (protocol.equalsIgnoreCase("pop3")) {
msgs = folder.getMessages();
return msgs;
}
return msgs;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[JBoss JIRA] Created: (JBAS-6190) repository based ProfileService hot deployment is not working
by Scott M Stark (JIRA)
repository based ProfileService hot deployment is not working
-------------------------------------------------------------
Key: JBAS-6190
URL: https://jira.jboss.org/jira/browse/JBAS-6190
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService, VFS
Affects Versions: JBossAS-5.0.0.CR2
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: JBossAS-5.0.0.GA
If the repository profile service is made the default, hot deployment is seen to not work. The jbossas testsuite fails because the minimal configuration shutdown relies on deployment of the shutdown.sar. Steps:
1. Copy the server/src/etc/conf/default/profile-repository.xml to server/src/etc/conf/default
2. build the server
3. start the minimal configuration
4. Copy the testsuite output/lib/shutdown.sar to the minimal config deploy directory:
[starksm@succubus testsuite]$ cp output/lib/shutdown.sar ../build/output/jboss-5.0.0.GA/server/minimal/deploy
[starksm@succubus testsuite]$ ls -l ../build/output/jboss-5.0.0.GA/server/minimal/deploy
total 8
-rw-rw-r-- 1 starksm starksm 3071 Nov 11 21:19 shutdown.sar
the server should shutdown in the next hot deployment cycle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months