InwebSphere, the path where a compiled version of a java program does not get the "progname.class"

The path where a compiled version of a java program does not get the "progname.class" / the "*.class" version of three programs that do not  have any compile errors.  I looked in the Tasks btton and had no errors in the java code.
 
How can I promote the compile version of a java program to get into the appropriate path?
 
Even after I deleted a program and created a new one with the same name, the Tasks did not depict any compile errors.  Yet, the class version did not appear in the path above where the compiled version of a java program shoul belong.
 
coolgemAsked:
Who is Participating?
 
apparitionConnect With a Mentor Commented:
Delete your Websphere cache or restart the server.
0
 
coolgemAuthor Commented:
I noticed that if i first copy the program(with a public static void main) from Websphere to Tomcat.
Then I access TOMCAT and  remove the package statement from the program and save and compile the program in the same directory.  Then I can run the program and it works.

Is there something I would have to do in Websphere by:
Creating a new project(a client one) and some how deplying a proper jar file or whatvever? Then create a bat file that can be run from the schedula. But how or does that tie in to the jar file from the newly created client project?
0
All Courses

From novice to tech pro — start learning today.