You should go for an exploded deployment in order to automatically have the changed app deployed. The change aware classloader does that. The classloader should aldo be able to pick up changes to the EAR and auto deploy if needed.
Coding specific changes that depend on weblogic or class loader hierarchy can be dangerous
my weblogic 9 is in dev mode and the ear is exploded then also it does not pick the APP-INF/classes changes.
i guess the ApplicationClassLoader being not changeawareclassloader causing this..
(weblogic.utils.classloaders.GenericClassLoader@793536( finder: weblogic.utils.classloaders.CodeGenClassFinder@16e523d, annotation: ApplicationClassLoader@)
is ther some configuration change which will solve this..
or can you please give details of the coding method..
This is not a coding related change. Some EARs are known to have problems with exploded deployment. You will have to consult the weblogic user guide for more details. Coding / config changes to class loader hierarchy are a bad idea. It is hard enough trying to guess what classes weblogic loads at runtime since V 9.2
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com