> I looked into that when doing the patch. Because these calls are all
> protected by hasNext() checks, IMHO you are guaranteed that there really
> will be a next element. Therefore, the only way you can get a null back
> is if your collection itself contains a null element. This is legal in
> the general case of Java development, but it's hard to say what a null
> value should mean in the context of an <html:options> tag. What do you
> think the behavior should be in that case?
As i said before. I always have the Collection filled in but..
One thing should it not do: a "null" string in the html
if it finds a null it should do insert an empty "" in the html.
johan
