On 11/17/06, Jerome Louvel <[EMAIL PROTECTED]> wrote: [...]
Interestingly, java.awt.List conflicts with java.util.List and java.lang.annotation.Annotation with java.text.Annotation, so even Sun isn't immune to these kind of issues.
This is a perennial problem in Java.
IMHO, we should just try to live with this.
Everybody has to live with this at one level or another so I don't think this is anything different for us.
It is for example not very likely that someone would want to develop Restlets and AWT code at the same time. Component will rarely be used by developers (abstract class). Maybe Container could be renamed to Engine, that would be consistent with the NRE terminology? But is it even worth it, I'm not sure.
Container is the usual terminology for this in the Java world so changing to something else would, IMHO, need to be justified. The only potential justification that comes to my mind is that there might be some confusion if people talk about running Reslets inside another "container" -- we'd end up with two levels of different "containers". For example, the Restlet container embedded inside a Servlet container. Personally, that doesn't confuse me at all but I've seen people get confused by stuff like that. Hope this helps, John
