I am trying to run an older and newer version of a site on the same instance of tomcat. The reason for this is because there will be a transition period from old to new - I want both to be running simaltaneously for a period at the same url.
The old and new site both have their own packages. These packages, however, contain some beans with the same name. The old and the new site appear to be referencing each others beans even though we reference them by package in the jsps <%@ page import="almbeans.*" %> for example. Now in the beans inside the packages we do not always specify the package in a call to another bean within that package. For example RegistrationBean may call BeanUtils.method1 in package 1. Package 2 also has a BeanUtils.method1. Both packages are in the classpath. Can packages get crossed this way? A call from a class in Package 1 won't necessarily go first to a class.method in Package 1, but may goto a class.method with the same name elsewhere in the classpath? ?? -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
