More on axis deployment

Mike,

I am getting closer to finally getting my app as a webservice.  (The company I
am building this for have kept going back and forth with what they want).  I
have some remaining questions though:

1. I see that there are some tasks in the keel-assemble-client.xml script that
copy necessary config files over for Axis deployments. However, they depend on
the do.axis property being set.  I don't believe it is being set though
anywhere, such as in "clientconditions" task.  Do you have any updated version
of this file with fixes to this, or have I missed something?

2.  I am interested in having my app available as a webservice and a struts
deployment.  To accomplish this, I figure I need to run the build twice, one
with an ant.properties following the example axis-server (clnt-axis=true,
comm-internal=true, etc).  The other build would have an ant.properties
following axis-struts (comm-axis=true, clnt-struts=true, etc.)  Is there an
easier way to accomplish what I want to do than to have to run two builds?  Is
there a way I can have clnt-struts and clnt-axis running in the same
ant.properties file? Also, if I have to just run two builds, is it as easy as
just changing the ant.properties file and running build-all again without
running clean.


Thank you,
Nate