App Startup problem in WL8.1

Question

We are currently running our application on WL7.04 and are having a classloader
problem deploying this same application on WL8.1.
After compiling our application using JDK141_03 into an EAR, and setting up our
domain, our attempt to deploy the EAR have resulted in ClassNotFoundExceptions.
The relevant portions of our EAR look like the following:
apptest.ear
     -- apptest.jar
     -- app.jar
     -- apptest.war
          -- Manifest.mf
The Manifest.mf found under apptest.war is as follows:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6alpha
Created-By: weblogic70 JDK
Class-Path: apptest.jar app.jar ecs-1.4.1.jar docmgmt.jar momapi-j2e
e-server-ejb.jar
Built-By: jefschum
Implementation-Vendor: American Management Systems, Inc.
Implementation-Title: apptest.war
Implementation-Version: 1.1 20031117130258
Upon application startup, classes found in app.jar are used to verify the existence
of classes in apptest.jar. However, none of the classes in apptest.jar can be
found. After turning on classloader verbosity it is clear that while app.jar
IS in the classpath utilized by the classloader apptest.jar is not.
As noted above, this IS working with no problems in WL7.04. Can you provide any
insight as to why this is NOT working in WL8?
Thanks.

Answer 1

Thanks for replying alhajerif. This was created in the config file after I used console startup configuration:
<StartupClass ClassName="com.dps.image.TestListener"
FailureIsFatal="true" LoadBeforeAppDeployments="false"
Name="TestListener Class"
Notes="Start up class for TestListener class" Targets="app3server"/>
I executed "netstat -n -a" at the DOS command prompt, port 2400 still didn't show up as listening. However, if my listener didn't implement T3StartupDef and use
public static void main(String[] args) throws Exception {...}, port 2400 will be listening. Why?
Michael