Brian Pontarelli wrote:
> I think the cast to (Class) is what is causing the problem. The
> String.class Object is inherently Class<String> so casting it to Class
> is causing the compiler error. The XJC, shouldn't be generating the cast
> unless absolutely necessary. This would fix the problem.
See the other e-mail I sent to this thread. I agree that it would reduce
the problem, but it won't fix it.
Like I said, in general there are cases where we cannot remove this
warning, so I feel uncomfortable to commit to the no-warning code
generation.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com