I have only recently started using Axis, so I'm not sure if I'm even
understanding your question correctly. but it sounds like you're
trying to do something I just did yesterday.
I had written a Java interface with a bunch of methods. The
arguments and return values of the methods were either simple Java
types, or one of two bean types I had also written. I found that
running the java2wsdl ant task didn't generate XML schema definitions
for my bean types.
After poking around in the source, I found what appears to be an
undocumented feature of the java2wsdl ant task. I'm using the
current CVS code, so that may be why it's undocumented. could be I'm
using it wrong, or that there's no plans on making this feature
public, or whatever.
anyhow, you can include <complexType> elements inside the java2wsdl
task. these just map a Java class to a namespace. you can also
specify [de]serializers, although in my case the default bean
serializer was fine. the task looks something like this:
<java2wsdl classname=' ... '
namespace='http://services.hawaii.edu/...'
style='document'
use='encoded'>
<classpath>
<path refid='cp'/>
<pathelement location='hawaii-service.jar'/>
</classpath>
<mapping namespace='http://services.hawaii.edu/technews'
package='hawaii.service.technews'/>
<complexType namespace='http://services.hawaii.edu/technews'
classname='hawaii.service.technews.Item'/>
<complexType namespace='http://services.hawaii.edu/technews'
classname='hawaii.service.technews.Update'/>
</java2wsdl>
one strange thing I encountered: even though all the Java classes
(the interface and the beans) were in the jar file listed above, ant
couldn't find the bean classes. I had to set my global (shell)
CLASSPATH to include the jar file to get the generation to work.
HTH,
--
joe
