It is possible to generate stubs without using WSAD, you could call
ejbdeploy command directly using an exec ant task, but the problem
with this is that if you are in a windows environment your classpath
cannot be longer that 128 characters otherwise you suffer the dreaded
input line too long, this is because ejbdeploy is a batch file.

After looking at redbooks and various newsgroups I could not find any
help, most people seem to do this running wsad in a headless mode.

However after careful examination of the ejbdeploy.bat file, I
discovered it simply sets up classpatchs and then calls an ejbdeploy
class, hence I used the java ant task to mimic this batch file.

You need a few properties like the was.home location, the name of your
db vendor as required by the ejbdeploy tool. Also ensure that the java
task dir property is set to the temporary folder that ejbdeploy uses
for compiling the classes, if its not set that rmic will not be able
to see the generated class files and it will fail.



value="${env.JAVA_HOME}/lib;${was.home}/classes;${was.home}/lib;${was.home}/lib/ext;${was.home}/web/help;${was.home}/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;"
/>














location="${ear.dir}/${build.date}/${app.ear}" />

dir="${scratch.dir}"
fork="true"
failonerror="true"
resultproperty="0"
maxmemory="256m"
output="ejbdeploy.log">



location="${was.home}/deploytool/itp/batch.jar" />
location="${env.JAVA_HOME}/jre/lib/ext/ibmorb.jar" />





I hope this helps

Steve

wrote in message news:<528870298.1081794136106.JavaMail.wasadmin@swg3ws00 6>...
> There is also a "compileWorkspace" Ant Task in Studio, one line and you almost have what you want. Current shipped version just does "javaC" compiles, no other build operations (like JSP compiles/validation etc), but that is coming soon.