[JBoss JIRA] Created: (JBFORUMS-115) NPE in ViewTopic
by Ryszard Kozmik (JIRA)
NPE in ViewTopic
----------------
Key: JBFORUMS-115
URL: http://jira.jboss.com/jira/browse/JBFORUMS-115
Project: JBoss Forums
Issue Type: Bug
Components: Java Server Faces based UIController layer
Reporter: Ryszard Kozmik
Fix For: 1.0.0 Alpha
Clicking this link http://forums.proto.jboss.com:8080/portal/index.html?ctrl:cmd=render&ctrl... , causes whole forums to dissapear and throw this exception:
18:06:20,855 ERROR [[/portal-forums]] Exception in FacesServlet
java.lang.NullPointerException
at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:393)
at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266)
at org.jboss.portlet.forums.ui.ForumsJSFPortlet.doView(ForumsJSFPortlet.java:94)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:167)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:407)
at org.jboss.portlet.forums.ui.ForumsJSFPortlet.render(ForumsJSFPortlet.java:128)
at org.jboss.portal.portlet.PortletContainer.invokeRender(PortletContainer.java:521)
at org.jboss.portal.portlet.PortletContainer.dispatch(PortletContainer.java:433)
at org.jboss.portal.server.app.ComponentInvocation.dispatch(ComponentInvocation.java:79)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:140)
at org.jboss.portal.core.aspects.component.TransactionInterceptor.invoke(TransactionInterceptor.java:72)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.component.HeaderInterceptor.invoke(HeaderInterceptor.java:50)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.component.NavigationInterceptor.invoke(NavigationInterceptor.java:76)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.component.CacheInterceptor.invoke(CacheInterceptor.java:111)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.component.ModesInterceptor.invoke(ModesInterceptor.java:88)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.component.WindowStatesInterceptor.invoke(WindowStatesInterceptor.java:87)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:49)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.portlet.aspects.component.SessionPostDispatchInterceptor.invoke(SessionPostDispatchInterceptor.java:65)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.component.ContextDispatcherInterceptor$InvokeNextCommand.execute(ContextDispatcherInterceptor.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.portal.server.servlet.CommandServlet.doGet(CommandServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:539)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at org.jboss.portal.server.app.impl.AbstractRequestContext.include(AbstractRequestContext.java:247)
at org.jboss.portal.server.aspects.component.ContextDispatcherInterceptor$1.include(ContextDispatcherInterceptor.java:73)
at org.jboss.portal.server.servlet.CommandServlet.include(CommandServlet.java:81)
at org.jboss.portal.server.aspects.component.ContextDispatcherInterceptor.invoke(ContextDispatcherInterceptor.java:79)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.portlet.aspects.component.SessionPreDispatchInterceptor.invoke(SessionPreDispatchInterceptor.java:94)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.component.ContextTrackerInterceptor.invoke(ContextTrackerInterceptor.java:49)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.portlet.aspects.component.SecureTransportInterceptor.invoke(SecureTransportInterceptor.java:69)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.portlet.aspects.component.ValveInterceptor.invoke(ValveInterceptor.java:64)
at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.invocation.Invocation.invoke(Invocation.java:175)
at org.jboss.portal.core.command.RenderWindowCommand.execute(RenderWindowCommand.java:84)
at org.jboss.portal.core.command.ControllerCommand.dispatch(ControllerCommand.java:78)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:140)
at org.jboss.portal.core.aspects.controller.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:85)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:168)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.controller.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:61)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.controller.NavigationInterceptor.invoke(NavigationInterceptor.java:68)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.invocation.Invocation.invoke(Invocation.java:175)
at org.jboss.portal.core.command.CommandContext.execute(CommandContext.java:107)
at org.jboss.portal.core.command.CommandContext.chain(CommandContext.java:141)
at org.jboss.portal.core.command.RenderPageCommand.renderPortlets(RenderPageCommand.java:231)
at org.jboss.portal.core.command.RenderPageCommand.execute(RenderPageCommand.java:164)
at org.jboss.portal.core.command.ControllerCommand.dispatch(ControllerCommand.java:78)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:140)
at org.jboss.portal.core.aspects.controller.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:85)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:168)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.controller.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:61)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.controller.NavigationInterceptor.invoke(NavigationInterceptor.java:58)
at org.jboss.portal.core.command.CommandInterceptor.invoke(CommandInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.invocation.Invocation.invoke(Invocation.java:175)
at org.jboss.portal.core.command.CommandContext.execute(CommandContext.java:107)
at org.jboss.portal.core.command.ExecutionContext.execute(ExecutionContext.java:93)
at org.jboss.portal.core.command.ExecutionContext.execute(ExecutionContext.java:151)
at org.jboss.portal.core.command.ExecutionContext.execute(ExecutionContext.java:77)
at org.jboss.portal.core.CoreController.handle(CoreController.java:190)
at sun.reflect.GeneratedMethodAccessor310.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:273)
at $Proxy136.handle(Unknown Source)
at org.jboss.portal.server.ServerInvocation.dispatch(ServerInvocation.java:76)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:140)
at org.jboss.portal.core.aspects.server.SubjectAssociationInterceptor.invoke(SubjectAssociationInterceptor.java:47)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.server.PolicyAssociationInterceptor.invoke(PolicyAssociationInterceptor.java:52)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:69)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:184)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.aspects.server.SessionInvalidatorInterceptor.invoke(SessionInvalidatorInterceptor.java:87)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java:75)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.server.invocation.Invocation.invokeNext(Invocation.java:130)
at org.jboss.portal.server.invocation.Invocation.invoke(Invocation.java:175)
at org.jboss.portal.server.servlet.PortalServlet.doGet(PortalServlet.java:221)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:407)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
--
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
[JBoss JIRA] Created: (JBMAIL-252) Failed to load IMAP envelope
by Brian Waskiewicz (JIRA)
Failed to load IMAP envelope
----------------------------
Key: JBMAIL-252
URL: http://jira.jboss.com/jira/browse/JBMAIL-252
Project: JBoss Mail
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: IMAP
Affects Versions: 1.0-M5
Environment: Windows XP, JBoss Mail 1.0-M5
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)
Reporter: Brian Waskiewicz
Assigned To: Andrew Oliver
I'm trying to use IMAP to retrieve messages from JBoss Mail. I'm able to get the array of messages, but when I try to iterate through them and print out the message subjects, I get:
Exception in thread "main" javax.mail.MessagingException: Failed to load IMAP envelope
at com.sun.mail.imap.IMAPMessage.loadEnvelope(IMAPMessage.java:1196)
at com.sun.mail.imap.IMAPMessage.getSubject(IMAPMessage.java:302)
And the server has this error message:
13:34:41,201 ERROR [STDERR] TODO Implement subfolders for LIST command
13:34:41,342 ERROR [STDERR] TODO implement FETCH
13:34:41,405 INFO [ConnectionHandler] ConnectionHandler finished
13:34:41,405 ERROR [STDERR] Exception in thread "Thread-23"
13:34:41,405 ERROR [STDERR] java.lang.RuntimeException: java.net.SocketException: Connection reset
13:34:41,405 ERROR [STDERR] at org.jboss.mail.ConnectionHandler.runSocket(ConnectionHandler.java:222)
13:34:41,405 ERROR [STDERR] at org.jboss.mail.ConnectionHandler.run(ConnectionHandler.java:97)
This only happens when I try to get a property of the message (getSubject(), etc). If I just iterate through the messages and call their toString method, it works fine.
--
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
[JBoss JIRA] Created: (JBMAIL-250) MailUserImpl.getAliases(..) throws an NPE if there is no mailbox for a given alias to check.
by David Fuelling (JIRA)
MailUserImpl.getAliases(..) throws an NPE if there is no mailbox for a given alias to check.
--------------------------------------------------------------------------------------------
Key: JBMAIL-250
URL: http://jira.jboss.com/jira/browse/JBMAIL-250
Project: JBoss Mail
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Mail Server APIs
Affects Versions: 1.0-M5, 1.0-RC1
Environment: WinXp, Jdk 1.5
Reporter: David Fuelling
Assigned To: Andrew Oliver
Priority: Minor
MailUserImpl.getAliases(..) throws an NPE if there is no mailbox for a given alias to check. Instead, the function should simply check if the mbox is null, and if so, simply return an empty list of aliases (i.e., there are no aliases for this user).
Here is my patch:
Index: MailSenderImpl.java
===================================================================
RCS file: /cvsroot/jboss/jboss-mail/src/java/org/jboss/mail/userapi/MailSenderImpl.java,v
retrieving revision 1.13
diff -u -r1.13 MailSenderImpl.java
--- MailSenderImpl.java 13 Jun 2006 23:53:04 -0000 1.13
+++ MailSenderImpl.java 28 Sep 2006 13:05:06 -0000
@@ -273,6 +273,9 @@
@Tx(TxType.REQUIRED)
public List<String> getAliases(String user) {
Mailbox box = this.mailboxService.getMailboxByAlias(user);
+ if(box == null)
+ return new ArrayList<String>(); //No Aliases exist for this user.
+
Collection<Alias> a = box.getAliases();
List<String> l = new ArrayList<String>(a.size());
Iterator<Alias> i = a.iterator();
--
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
[JBoss JIRA] Created: (JBMAIL-251) WebMail LoginView RememberME Functionality
by David Fuelling (JIRA)
WebMail LoginView RememberME Functionality
------------------------------------------
Key: JBMAIL-251
URL: http://jira.jboss.com/jira/browse/JBMAIL-251
Project: JBoss Mail
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: WebMail
Affects Versions: 1.0-M4, 1.0-M3, 1.0-M2, 1.0-M5, 1.0-RC1, 1.0-final
Reporter: David Fuelling
Assigned To: Andrew Oliver
Priority: Minor
Fix For: 1.0-M5, 1.0-RC1, 1.0-final
Attachments: LoginView_patch.mxml.java
When a user logs into the webmail, he/she can click the "Remember Me" checkbox and have the Flash webmail application remember his username/password information. The functionality to do this has been implemented with this patch, by leveraging the Flash Shared Object feature (which acts like a browser cookie) to store the login credentials for later use.
It is unknown what the security implications of this are. Flash Shared Objects are stored to disk in a specified user directory. In WinXP, for example, this directory is not accessible unless you are logged in as an admin or the designated user (same for Unix, I assume). So, even if the uid/password are un-encrypted on disk, this may not be a security concern.
--
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
[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
[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
[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