[Mc4j-development] MC4J 1.2b9 WebLogic installation detection procedure

[Jim D. <jd...@is...>]

MC4J 1.2b9 was unable to detect my WebLogic 6.1 installation when going 
through the "2. Select Server Installation" step of the add-connection 
wizard.  I found many questions in the mailing lists about how server 
detection works, but no answers, and the FAQ and release notes on the 
mc4j.org web site referred to changes in how server detection works but 
did not contain any details.  After inspecting the MC4J source, I found 
out the detection procedure and was easily able to setup what MC4J 
needed to detect WebLogic 6.1.

Detection is based solely on finding a directory containing the 
sub-directory path "server/lib/weblogic.jar" and inspecting that jar 
file's manifest.  Unfortunately, this is not the path used by the BEA 
WebLogic installer, at least for version 6.1, where the BEA installer 
puts the server's jar file under "bea/wlserver6.1/lib/weblogic.jar". 

I setup a dir tree underneath my MC4J install (/usr/local/MC4J-1.2b9) 
called "server-jars/server/lib" and put a symbolic link to my 
weblogic.jar there. 

Then the folder containing "server" (in my case 
"/usr/local/MC4J-1.2b9/server-jars") shows up in bold in the "Choose 
installation directory" file finder window as "server-jars (weblogic: 
6.1.3.0)", and selecting it enables the "Select Server" button.

Note that you can find this detection procedure in the following classes 
(at least as of 1.2b9):

http://cvs.sourceforge.net/viewcvs.py/mc4j/mc4j/src/org/mc4j/console/connection/install/finder/ServerInstallSelectorPanel.java?rev=1.5&view=markup
 and 
http://cvs.sourceforge.net/viewcvs.py/mc4j/mc4j/src/org/mc4j/console/connection/install/finder/FileSystemModel.java?rev=1.3&view=markup 
and 
http://cvs.sourceforge.net/viewcvs.py/mc4j/mc4j/src/org/mc4j/console/connection/install/WeblogicConnectionTypeDescriptor.java?rev=1.6&view=markup

The key method stating what path to look for is 
WeblogicConnectionTypeDescriptor.getRecongnitionPath.

Jim