I have j2ee on windows 98 and have successfully deployed a ejb previously on it ,(the deployment was ok but I could not run the client) now when I want to reopen the deploytool by first running the j2eee server and then setting home and path and then I say deploytool in the command prompt , what I get is the first deploytool screen and then my ms dos prompt runs a long list of errors, I tried finding the .ear files and delete them so that deploytool starts without the previous ejb I deployed but I can't find the .ear file anywhere on my computer what should I check now???Please help
NageswaraRao Karra
Ranch Hand
Joined: Nov 12, 2000
Posts: 34
posted
0
hello! the exception is nullpointer exception. to get the deploytool again you may try the following. -find delete .ear files you have created for yr.application deployment(in the directory you mentioned while deployment). -find and delete .jar files (which will be starting with yr.application name).these files will be in - C:\j2sdkee...\repository\computername\applications....here delete all the jar files which are particular to yr. application. there are still jar files in \repository\gnrtemp\... here also delete the jar files of yr.applications. -delete log files. -still there is another directory you have to look for. C:\windows\j2eedeploytool\... here there will be yr.application files.delete them. if you do all these you can start the deploytool even without warnings. -there is another way of doing this.execute cleanup.bat in j2sdkee...\bin directory after shutting down the server.but to what extent it does i don't know. pl.verify the directory structure and names. only thing when deleting just be careful that's all deploytool can be run
Mohammed Umer
Greenhorn
Joined: Feb 04, 2001
Posts: 15
posted
0
Thanks once more, your really cool!!! I did not find any .ear files but I deleted the jar files like u said, I had copied a jar file to the c:\j2sdkee1.2.1\bin which I noticed and deleted and the deploytool opened after giving a warning that it could not find the previous EJB file. Thanks
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.