On Sat, 10 Jul 2010 13:40:38 -0300, Inge Solvoll <[email protected]>
wrote:
Hi!
Hi!
In our application we have classes packaged in jars. When we make
changes to
those classes during development, they are compiled into WEB-INF/classes,
making them override the ones in the jars because WEB-INF/classes is read
first by the classloader. This is a convenient way of developing for us.
Why are you packaging in JARs classes you're still developing?
But: The ClassNameLocator does not take this into account. So it finds 2
classes with the same name, one from the jar and one from
WEB-INF/classes.
Is this the desired behaviour? As you can see from the link, this causes
problems for me when using a component from spreadthesource.
I don't know the answer, but having two different versions of the same
class in the classpath at the same time seem like something that should be
avoided.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
