My idea is that hackyReport can throw a RuntimeException if there is name duplication (which does not violate its design feature).

Fail-fast is always better than fail-late (and leave every one wondering what goes wrong).

This is the second time that I have spent time debugging this issue. I am sure there will be the third time (either me or somebody else) if we don't do anything about it.

Anyway, I have to change my program logic.

Cheers,

Cedric


Philip Johnson wrote:
My initial thought is that requiring each series to be uniquely identified by name is not an unreasonable design feature for hackyReport.

Cheers,
Philip

--On Sunday, October 10, 2004 2:16 PM -1000 "(Cedric) Qin ZHANG" <[EMAIL PROTECTED]> wrote:

Hi,

In report package, chart model consists of one or more "series", and each
series has a name.

I found that if two series has the same name, then only one of them will
show up in the rendered chart.

While I can change my program logic to guarantee uniqueness of series
name, but I am not sure whether the problem is generic enough so that
it's better to be handled in report model or not.

Any opinion?

Thanks.

Cedric








Reply via email to