On 6/22/07, Lorenzo Cerini <[EMAIL PROTECTED]> wrote:
but my tomcat mismatch the classes, i mean if i recompile the Connessione_dyn belonging to app2 and restart tomcat, even my app1 try to use the app2's Connessione_dyn instead of its own one, thus leading to an error since the pooled connection used by app2 is not 'registered' in the app1 context. I have used the same configuration for a long period on tomcat 5.0.28 with no problems.
I think this most likely caused by cross-context conflict. Have you tried explicitly setting crossContext="false" in your application's context? Try naming the classes and their packages in the two separate apps such that their names are different. Do you have an option to use multiple virtual hosts instead of multiple contexts? I was able to deal with cross context class conflicts by deploying each app on it's own virtual host rather than multiple contexts within the same virtual host.
Maybe can help my java version is: # /tomcat/java/bin/java -version java version "1.6.0_01" Java(TM) SE Runtime Environment (build 1.6.0_01-b06) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_01-b06, mixed mode) Thanks in advance L.Cerini
-Rashmi --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
