duplicate classes (SAX problem)
Thu Oct 24 11:33:00 GMT 2002
Mark Wielaard <email@example.com> writes:
> On Thu, 2002-10-24 at 11:13, firstname.lastname@example.org wrote:
> > Instead of throwing an exception shouldn't this somehow allow the use
> > of the existing (already loaded) class?
> This does make sense to me since it mimics that way traditional java
> implementations work. Only the first class with a certain name (from the
> same package and classloader) is loaded into the runtime, others are
> Would making that change here make sense or do we get problems later on?
> Nic, have you tried just commenting out if block?
I'm testing some thoughts about fixing it. When I find out some stuff
I'll let the list know.
More information about the Java