Ken,
I looked at the code concerning the "data" variable and concluded that was
not the problem. One important thing that should be included in every bug
report is how to reproduce it. Hopefully Anissa will give us some feedback
on this.
Mike
On Feb 16, 2008 3:08 PM, Ken Paulsen <Ken.Paulsen_at_sun.com> wrote:
>
> Hi Mike,
>
> Thanks for looking into this!
>
> I don't think it is "descriptor" that is (null) as this should never
> happen. I think it is the variable "data" or perhaps something inside
> data that caused this problem. However, in quickly looking at the
> code... I don't see any problems with it. If you can't reproduce the
> problem, you may need to ask Anissa (looks like she filed this issue) to
> provide a test case or more information.
>
> It's possible that this issue has already been fixed... but I'm not sure.
>
> Thanks,
>
> Ken
>
>
> Michael Phoenix wrote:
> > am looking at issue #6 and wanted to clarify it a bit and see if my
> > take on the issue is valid.
> > What I understand the text to be saying is that the parm variable
> > named "descriptor" is sometimes being passed as a null. Is this correct?
> > If so then it looks like what it is asking for is to initialize
> > descriptor as an ArrayList containing a single empty ArrayList before
> > calling setOptions. Is this correct? The issue description uses the
> > term "List", but that is just an interface.
>