[HACKYSTAT-DEV-L] Investigating upgrade to Java 1.5

[Aaron Kagawa]

Hey Guys,

I've just started looking at the upgrade to Java 1.5.  Things aren't moving very smoothly. Here is a short summary of what I've found so far:

---------------------------------------------------------------------------------------
TOMCAT ISSUES

Issue for Tomcat 5.0  (I suppose this isn't important because we will be moving to Tomcat 5.5)
Tomcat 5.0.x introduced a weird mechanism for automatically deploying a web application with a <webappname>.xml file in the Tomcat/conf/Catalina/localhost/ directory.  This gave Philip a problem a long time ago.  If my memory serves me correctly, tomcat saved the location of the War directory of a previous Hackystat installation and Philip actually wanted to build the system that had a different War directory.  So, after building Hackystat from this new location, he didn't see his changes.  Since then, the following line was placed in the undeployHackystatWar target.  This removes the hackystat.xml file from the Catalina directory.  Again, this xml file apparently automatically deploys the webapp from the last location that it was installed.

    <delete dir= "${tomcat.home}/conf/Catalina/localhost/hackystat.xml" quiet= "yes" />

From what I can gather, I'm not sure if this totally solves the problem for quickStart and freshStart targets.  Currently, under Tomcat 5.0 when Tomcat is started tomcat still initializes Hackystat because the hackystat.xml file is still in the conf/Catalina/localhost directory.  Just start tomcat and you will see the following.  But, I don't know if still causes the problem that Philip encountered. 

INFO: Processing Context configuration file URL file:C:\java\jakarta-tomcat-5.0.
28\conf\Catalina\localhost\hackystat.xml
08/18 21:28:40 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
08/18 21:28:40 Hackystat:  Initializing system.


Issue for Tomcat 5.5
Unfortunately, Tomcat 5.5 does the same thing but in a totally different way Tomcat 5.0.  In 5.5, after deploying, shutdown and startup the Hackystat system is automatically initialized. But, in 5.5 they don't use the hackystat.xml instead the

    <property name= "deploy.url.path"   value= "file://${install.war.dir}/" />
    <property name= "deploy.params"  value= "path=/${hackystat.context.root}&amp;war=${deploy.url.path}" />
    <property name= "deploy.install.url"   value= "${hackystat.host}/manager/deploy" />
    <get src=""> "${deploy.install.url}?${deploy.params}"
         dest= "install-results.tmp"
         username= "${tomcat.admin.user}"
         password= "${tomcat.admin.password}" />

actually copies the war directory to the tomcat/webapps directory.  So after the execution of installHackystat the tomcat/webapps contains a hackystat folder full of the war contents. And removeHackystat deletes everything in the tomcat/webapps/hackystat directory. 

The thing is that I don't think that functionality of 5.5 will cause the same problem we seen in 5.0.  I suppose only time will tell.

Anyway.. that is what I've found in my investigation.  I'm not sure if any of these are problems; they are just differences from the Tomcat 4.x that I'm used to. 

---------------------------------------------------------------------------------------
OTHER ISSUES
I plan to continue looking at the upgrade of Hackystat to Java 1.5.  I've been building everything up to hackyStdExt.  So far I've found that:

1) you can't deploy an old hackystat war file (compiled in Java 1.4) in the new Java 1.5 environment. there seems to be a problem with the soap deployment.
2) there are many warnings but it compiles
3) there are appears to be a problem with Ant 1.6.5's replace task.. I get the following exception when the build.utils.xml tries to replace the Admin key after running the unittests.  The funny thing is that I stripped out the Ant xml code and ran the replace task in its own little build.xml file and everything works.  There seems to be a problem with the replace task when other things are executed before it.  I haven't figured out why yet.   the task works fine in Java 1.4!

     [echo] (hackyBuildUtils) Running JUnit tests on module hackyStatistics.

BUILD FAILED
C:\java\cvs\hackyBuild\build.xml:499: The following error occurred while executi
ng this line:
C:\java\cvs\hackyBuild\build.utils.xml:725: The following error occurred while e
xecuting this line:
C:\java\cvs\hackyBuild\build.utils.xml:486: IOException in C:\java\cvs\hackyBuil
d\build\reports\junit\hackyStatistics\org\hackystat\stdext\statistic\0_TestDataS
equence.html - java.io.IOException:Failed to delete C:\java\cvs\hackyBuild\build
\reports\junit\hackyStatistics\org\hackystat\stdext\statistic\0_TestDataSequence
.html while trying to rename C:\java\cvs\hackyBuild\build\reports\junit\hackySta
tistics\org\hackystat\stdext\statistic\rep1420225305.tmp


4) this one is a little ironic.  You can't build Hackystat without the installation of the sensors.  I kind of wanted to build Hackystat without any jar files (specifically sensor jar files) that could possibly be Java 1.5 incompatible but that isn't possible.
5) the stackyHack system in CVS has an error in the build.xml file.  it refers an old version of the build sensor. But, the zip file obtainable in the docbook is correct.

thanks, aaron