I have successfully created an enterprise application CLIENT using WSAD. It connects to an EJB on a remote server. Problem I am having is that when I try to export the client.jar, it only deploys the classes located in the client project and not any of it's dependencies.
Shouldn't I be able to export a client project without having to worry about manually including all of the internal jar files that WSAD uses when the client runs? My client is a simple swing client that I want to run from command line or a bat file and distribute but of course cannot without including a multitude of .jar files in the manifest.
What I am doing wrong?
No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
William, Unfortunately, that's the way it works in WSAD. If you happen to be running the client on the same box as the server, you can point at the deployed code. If not, you have to figure out what jars you need.
# make sure using path for correct version of WAS's java $WAS/java/bin/java -classpath ".:$MY_EJB_JAR:$RUNTIME:$J2EE:$WAS/lib/ltext.jar:$WAS/lib/namingclient.jar: $WAS/lib/naming.jar:$WAS/lib/ecutils.jar:$WAS/lib/lmproxy.jar:$WAS/lib/bootstrap.jar: $WAS/properties" -Dcom.ibm.CORBA.ConfigURL="$WAS/properties/sas.client.props" -Dserver.root="$WAS" -Dws.ext.dirs="$WAS/java/lib:$WAS/classes;$WAS/lib;$WAS/lib/ext" -Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory -Xbootclasspath/p:"$WAS/java/jre/lib/ext/ibmorb.jar;$WAS/properties" Client
[edited to add linebreaks] [ November 20, 2004: Message edited by: Jeanne Boyarsky ]