On Sat, Jul 10, 2010 at 8:08 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote:
> On Sat, 10 Jul 2010 13:40:38 -0300, Inge Solvoll <inge.tapes...@gmail.com> > 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? > > As I said, it's convenient. Our application consists of many different maven projects that need to be assembled into one web container as jars. It's a complex aggregated application, and it would require extra work to provide a specific setup for development that doesn't use jar files. Espescially since it works the way we do it now, and it doesn't seem like the biggest hack in the world to me. The classloader was probably built like this (handling duplicates by priority) for a reason :) > > 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: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
