dev@jsftemplating.java.net

Re: JSFTemplating: first attempt at resolving bug

From: Ken Paulsen <Ken.Paulsen_at_Sun.COM>
Date: Sat, 16 Feb 2008 15:08:17 -0800

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.