ATG-Class-Path Usage and Duplicate Class Files in JARS

-
I came across a situation in which i have two Class Files of the same name in different JARs but with some methods similar and other methods entirely different , these two JARS are required for the same Project with different Modules and i want to access the one which is compatible with my Code and Module,The other Module obviously dont want this Class file but requires other Classes,now the issue is you  have both the jars in CLASSPATH.How will you make sure you are pointing to the correct Class files in this situation, you need the Class Files from one JAR which has your updated method for a new functionality,

You may experience the same issue while organizing imports or resolving a Java component.

Here you need to do two things,first one is to resolve the component at Compile time in Eclipse or other IDEs,the second part is to resolve the runtime conflicts in the Application Server

So for Compile time,Assume if you are using Eclipse and you have both  JAR added to your build path ,you need to go to "Order and Export" tab and move your  updated jar above the other one,after this  you may able to build your Project smoothly without any issues.Second is to resolve the runtime conflicts

ATG has provided a beautiful way of handling this scenario,we have in ATG a better way of loading the CLASSPATHS,ATG looks for  MANIFEST.MF file,this file will specify which oder your Application Server has to load the CLASSPATHs.So put your updated JAR files before the other one in this Property.

Below is the example

ATG-Class-Path: lib/updated.jar lib/old.jar

Here its generally not that tough to resolve the issue by either finding the Class and the dependant Files , but there are situations in which we might face the similiar issues in OOTB Classes of different Vendors which need to be resolved.So this will be a good reference for the Beginners.

MANIFEST.MF
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 16.0-b13 (Sun Microsystems Inc.)
ATG-Product: The Commerce Reference Store
ATG-Class-Path: classes lib/ lib/updated.jar lib/old.jar
ATG-Config-Path: config
ATG-Required:Store.EStore

After Configuring the Manifest File and Deploying the Application you can verify the Application Server Startup logs.You may see the updated.jar will be loaded first then the old.jar will be loaded.

Comments

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more