dependant class paths in WAS 4.0

[Fred Abbot]

in 3.5x ypu were able to set dependant class paths for the serevr how can you do this in 4.0?

[Kyle Brown]

Originally posted by Fred Abbot:
in 3.5x ypu were able to set dependant class paths for the serevr how can you do this in 4.0?

In general you don't. I take it you have some JAR files you want your EJB jar file to use? If so, then you need to add them to the EAR file that you deploy to 4.0. Then update the manifest of your EJB-JAR file so that its files can reference the other JAR files.
More details can be found in my workbook for WebSphere AEs 4.0.
Kyle

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.

[Fred Abbot]

thanx Kyle
actually when i deploy my jar file from VAJ i select the button indicating get allr efrenced classes etc..
but i have also made changes to the VAP code i added my own converters among other things
so i change the vaprt as well as adding another file and this always worked for me
so I really dont know how the new one works

[Fred Abbot]

I am now getting the following error when trying to start my apllication

exception:
com.ibm.ejs.sm.exception.StaleActiveObjectInvocationException

--------
com.ibm.ejs.sm.client.command.ExecutionException: Command MIDAS.start failed.
at com.ibm.ejs.sm.client.command.AbstractCommand.handleAct(AbstractCommand.java:286)
at com.ibm.ejs.sm.client.command.StartCommand.execute(StartCommand.java:94)
at com.ibm.ejs.sm.client.command.CommandManager$ExecutionThread.run(CommandManager.java:264)
at com.ibm.ejs.sm.client.command.ThreadPool$PooledThread.run(ThreadPool.java:89)