This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: Almost FULL Success in SJSAS integrationwith Eclipse WTP!
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
Guess what folks and Fellow Eclipse fans. Thsi afternoon I will be runing Sun JSAS PE 8.1 server within Eclipse WTP! How did I get the plugin working? Lets jsut say that the TWP0.7.1 implementation of the serverdef file fdormat and what the schema xsd file shows are slightly different. Not by much but jsut enough that I had to get into Gorkem Ercan's head to figure out what definitons and assumptions he was making in the implementation.
Basically, I am resolving the last assumption that produces this error, now:
Oct 14, 2005 11:34:12 AM com.sun.enterprise.util.ASenvPropertyReader setSystemProperties
SEVERE: property_reader.asenvReadError
java.io.FileNotFoundException: null\asenv.bat (The system cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at java.io.FileInputStream.(FileInputStream.java:66)
at java.io.FileReader.(FileReader.java:41)
at com.sun.enterprise.util.ASenvPropertyReader.setSystemProperties(ASenvPropertyReader.java:180)
at com.sun.enterprise.cli.framework.CLIMain.invokeCommand(CLIMain.java:87)
at com.sun.enterprise.cli.framework.CLIMain.main(CLIMain.java:46)
CLI138 Invalid domain path, null
For those new to SUn JSAS 8.1 PE, the server installed in the J2EE SDk Default install, this set of errors means that the asenv.bat that sets environmental variables and called from asadmin.bat is not able to read my startscript and stopscript locations in the serverdef file. Basically, you cannot use the \ path separator in the serverdef file for windows due to the cross platform nature of Eclipse and WTP.
Basically, what I had to add to external launch mode to get it to work was mainClass, and classpathReference tags. Yes, all the tricks and tips are being detailed in an article I expect to post this weekend at Java.Net, EclipseZone, and etc..