It is possible to use an explicit import to resolve conflicts from wildcard
imports, as long as the explicit import is listed after the conflicting
wildcards.
I certain do not suggest that we do this, I just wanted to share =)
--jason
On Sun, 24 Jun 2001, Scott M Stark wrote:
> So you can know what is being used and in general wild card imports
> cannot be used as this causes conflicts when two packages have a
> class with the same name(Attributes for example):
>
> import javax.naming.directory.*;
> import org.xml.sax.*;
>
> class tstImport
> {
> public static void main(String[] args)
> {
> Attributes attrs = null;
> }
> }
> bash-2.04$ javac tstImport.java
> tstImport.java:8: reference to Attributes is ambiguous, both class
>org.xml.sax.Attributes in org.xml.sax and class
> javax.naming.directory.Attributes in javax.naming.directory match
> Attributes attrs = null;
> ^
> 1 error
>
> ----- Original Message -----
> From: "Matt Veitas" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, June 24, 2001 6:56 AM
> Subject: [JBoss-dev] Reasons for using Explicit Imports?
>
>
> Could you briefly explain the reasoning behind EXPLICIT IMPORTS? What is
> wrong with using wildcards. My guess is that by looking at the explicit
> import list you can have some sense of what exactly is being used or is
> there a performance issue?
>
> Matt
>
>
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
