Hai dimitris, Thanks for your reply again.
I was looking for a solution for the problem and found the article 'JBossClassLoadingUseCases'.This says, 'However, it is possible to trick the server (or the VM) into doing this. If application A interacts with application B, but doesn't have any direct references to the B classes, and B changes, let's say a newer and better version becomes available, it is possible to create a new class loader, load the new B classes and have the invocation bus (the application server) route all invocations from A to the new B classes. This way, A deals with a new version of B without even knowing it. If the application server is careful to drop all explicit references to the old B classes, they will eventually be garbage collected and the old B will eventually disappear from the system.' Is this a feasible solution ? But I also understand that usage of new Custom Class Loaders is a violation of EJB Specifications. Is there any other way to get around you propose for this scenario ?Because we dont want to redeploy the Static.ear,as it runs in production environment on a 24*7 basis. Hoping for your inputs on this. Thanks Hari View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932822#3932822 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932822 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
