September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMAIL-249) Message Bodies should not display if more than 1 message is selected in a given folder

by David Fuelling (JIRA)

Message Bodies should not display if more than 1 message is selected in a given folder -------------------------------------------------------------------------------------- Key: JBMAIL-249 URL: http://jira.jboss.com/jira/browse/JBMAIL-249 Project: JBoss Mail Issue Type: Sub-task Security Level: Public (Everyone can see) Components: WebMail Affects Versions: 1.0-RC1 Environment: Windows XP Professional, Flash Player 9 v 3 Reporter: David Fuelling Assigned To: Andrew Oliver Priority: Optional Fix For: 1.0-RC1 When more than 1 message is selected in a given folder, the webmail should not show the message bodies of every message. Currently, if 4 messages are selected (for example), then all of the message bodies display, which can take a long time if one selects lots of messages -- imagine 5 messages that are each 1 Meg each. Displaying each body takes forever. In such a scenario where a user multiselects >1 message, a user probably doesn't care to see the message bodies. They are probably doing a drag/drop operation (IMHO). -- 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

19 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMAIL-245) getBoundary() in MessageData crashes if no Content-Type header is present

by Pat Osterday (JIRA)

getBoundary() in MessageData crashes if no Content-Type header is present ------------------------------------------------------------------------- Key: JBMAIL-245 URL: http://jira.jboss.com/jira/browse/JBMAIL-245 Project: JBoss Mail Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Pat Osterday Assigned To: Andrew Oliver In the getBoundary() method in MessageData, I think the line: String[] header = getHeader("Content-Type").split("\\r\\n"); Should be moved into the try/catch. If a message doesn't have a Content-Type, the method crashes. Not sure how the writeMessage in CmdRETR in the pop3 handlers would handle this, but I'm using similar code to read messages via a servlet and this issue just popped up for us. Another option would be something like this in the beginning of the method: String ctHeader = getHeader("Content-Type"); String[] header = null; if (ctHeader != null) { header = ctHeader.split("\\r\\n"); } else { return null; } -- 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

19 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMAIL-247) MessageData NPE in getBoundary when Content-Type header is missing

by David Fuelling (JIRA)

MessageData NPE in getBoundary when Content-Type header is missing ------------------------------------------------------------------ Key: JBMAIL-247 URL: http://jira.jboss.com/jira/browse/JBMAIL-247 Project: JBoss Mail Issue Type: Bug Security Level: Public (Everyone can see) Components: IMAP, Mail Server APIs, POP, WebMail Affects Versions: 1.5-M4, 1.5-M5 Environment: WinXP, JBossAS 4.0.4GA_Patch1, JBCS Head as of July 31st, 2006. Reporter: David Fuelling Assigned To: Andrew Oliver Priority: Minor See forum post here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=88893 Here is a patch. It simply moves the creation of the "header" string array inside of the try/catch block. If an exception is thrown, it is caught and ignored. Index: MessageData.java =================================================================== RCS file: /cvsroot/jboss/jboss-mail/src/java/org/jboss/mail/mailbox/MessageData.java,v retrieving revision 1.21 diff -u -r1.21 MessageData.java --- MessageData.java 11 Jun 2006 14:06:23 -0000 1.21 +++ MessageData.java 18 Aug 2006 15:16:02 -0000 @@ -342,9 +342,9 @@ } public String getBoundary() { - String[] header = getHeader("Content-Type").split("\\r\\n"); - String retval = null; + String retval = null; try { + String[] header = getHeader("Content-Type").split("\\r\\n"); for (int i = 0; header != null && i < header.length; i++) { if( header[i].indexOf("boundary=\"") >-1) { String[] temp = header[i].split("boundary\\=\\\""); -- 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

19 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMAIL-243) ClassLoader Deployment Error

by Ryan Maloney (JIRA)

ClassLoader Deployment Error ----------------------------- Key: JBMAIL-243 URL: http://jira.jboss.com/jira/browse/JBMAIL-243 Project: JBoss Mail Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows XP Professional, JBoss 4.0.4.GA, JBMS 1.0M5 Reporter: Ryan Maloney Assigned To: Andrew Oliver mail.ear fails to deploy with the following error: No ClassLoaders found for: org.jboss.varia.scheduler.Scheduler -- 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

19 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMAIL-244) Fetching mail with MalformedHeader from POP3 server

by Ryan Maloney (JIRA)

Fetching mail with MalformedHeader from POP3 server ---------------------------------------------------- Key: JBMAIL-244 URL: http://jira.jboss.com/jira/browse/JBMAIL-244 Project: JBoss Mail Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss application server 4.0.4-CR2 running on Windows XP Profesional SP2 Reporter: Ryan Maloney Assigned To: Andrew Oliver Enabled fetchmail and added a pop3 account. Manually invoked the pop() method via the mx-console and received the following: [Top part of the stack trace] INFO [org.jboss.mail.fetchmail.Popper] Found 104 messages (0) new ones INFO [org.jboss.mail.fetchmail.Popper] Trying to get message 0 INFO [org.jboss.mail.fetchmail.Popper] Message 0 Subject: EMAIL SUBJECT REMOVED ERROR [org.jboss.mail.fetchmail.Popper] org.jboss.mail.message.MalformedHeaderException: Malformed Header: This is a multi-part message in MIME format. [end snippet] Mail retrieval ended immediately thereafter. I have sent the offending header to acoliver(a)jboss.com -- 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

19 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-141) Add a glosssary of terms

by Mark Little (JIRA)

Add a glosssary of terms ------------------------ Key: JBESB-141 URL: http://jira.jboss.com/jira/browse/JBESB-141 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 -- 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

19 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-140) The JTS UserTransaction raises the wrong exception if the transaction has been terminated through the transaction reaper as a consequence of a timeout.

by Kevin Conner (JIRA)

The JTS UserTransaction raises the wrong exception if the transaction has been terminated through the transaction reaper as a consequence of a timeout. ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-140 URL: http://jira.jboss.com/jira/browse/JBTM-140 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 -- 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

19 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-98) Adding padding support to Xid for Oracle OCI driver

by Mark Little (JIRA)

Adding padding support to Xid for Oracle OCI driver --------------------------------------------------- Key: JBTM-98 URL: http://jira.jboss.com/jira/browse/JBTM-98 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 Plus add it to qualification drivers for DTF. -- 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

19 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-977) 403 error when logging in as admin with LDAP

by Kevin Barfield (JIRA)

403 error when logging in as admin with LDAP -------------------------------------------- Key: JBPORTAL-977 URL: http://jira.jboss.com/jira/browse/JBPORTAL-977 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Environment: Portal 2.4 CR3 bundled Reporter: Kevin Barfield Fix For: 2.4 Final A 403 error is shown when logging in as admin using LDAP. Open a new browser, and now you are logged in. Same issue with logout. Logging in as a regular user is fine. Here is the login config: <policy>  <application-policy name="cms"> <authentication> <login-module code="org.apache.jackrabbit.core.security.SimpleLoginModule" flag="required"/> </authentication> </application-policy> <application-policy name="portal"> <authentication> <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required"> <module-option name="java.naming.factory.initial"> com.sun.jndi.ldap.LdapCtxFactory </module-option> <module-option name="java.naming.provider.url"> ldap://localhost/ </module-option> <module-option name="java.naming.security.authentication"> simple </module-option> <module-option name="java.naming.security.principal"> cn=Manager,dc=example,dc=com </module-option> <module-option name="java.naming.security.credentials"> secret </module-option> <module-option name="principalDNPrefix">cn=</module-option> <module-option name="principalDNSuffix"> ,ou=people,dc=example,dc=com </module-option> <module-option name="password-stacking">useFirstPass</module-option> <module-option name="rolesCtxDN"> ou=groups,dc=example,dc=com </module-option> <module-option name="uidAttributeID">member</module-option> <module-option name="matchOnUserDN">true</module-option> <module-option name="roleAttributeID">cn</module-option> <module-option name="roleAttributeIsDN">false </module-option>  </login-module> </authentication> </application-policy> </policy> -- 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

19 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-308) Upgrade commons-logging from 1.0.3 to 1.1.0

by Bela Ban (JIRA)

Upgrade commons-logging from 1.0.3 to 1.1.0 ------------------------------------------- Key: JGRP-308 URL: http://jira.jboss.com/jira/browse/JGRP-308 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Needs some testing -- 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

19 years, 5 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006