You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/12/02 14:10:03 UTC

[jira] Updated: (AMQ-2631) activemq - protobuf does not handle nulls well.

     [ https://issues.apache.org/jira/browse/AMQ-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac updated AMQ-2631:
-------------------------------

    Fix Version/s:     (was: 5.4.2)
                   5.5.0

> activemq - protobuf does not handle nulls well. 
> ------------------------------------------------
>
>                 Key: AMQ-2631
>                 URL: https://issues.apache.org/jira/browse/AMQ-2631
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>         Environment: Java 1.6, Activemq - protobug v 1.0
>            Reporter: Tarjei Huse
>             Fix For: 5.5.0
>
>         Attachments: testPatch.patch
>
>
> When assertInitialized does not check if a property is set to null, this then gives an NPE later. 
> The attached patch is the same as the following test:
> package org.apache.activemq.protobuf;
> import junit.framework.TestCase;
> import org.apache.activemq.protobuf.DeferredUnmarshal.Baz;
> /**
>  *
>  * @author tarjei
>  */
> public class NullNotAllowedTest  extends TestCase{
>     public void testNull() {
>         Baz foo = new Baz();
>         foo.setField1(null);
>         byte[] b = foo.toUnframedByteArray();
>     }
> }
> It demonstrates the error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.