I found the answer to my issues. After looking through the source code some more, it seems like the java2wsdl Ant task is much more capable than the java2wsdl main class. I would have used the Ant task to begin with, but I couldn't figure out a way to get my java class into the classpath of the ant task. There was an undocumented classpath added to the ant task sometime last summer which now makes that possible. However, one author also pointed out that one could add to the global classpath of Ant at runtime during the <taskdef> that brought in the <ant-java2wsdl> and other tasks. This is what I now have an it works for generating WSDL for interfaces accepting a custom bean type. I have more Ant properties to add in the generation, but the WSDL is now starting to be generated with the bean. Note too that the taskdef load fails if Ant cannot resolve the javax.xml classes. This was corrected in my case by adding j2ee.jar into the AXIS_HOME/lib directory. <taskdef resource="axis-tasks.properties"> <classpath> <fileset dir="${AXIS_HOME}/lib" includes="*.jar"/> </classpath> </taskdef> <target name="_axiswsdl_"> <property name="ws.style" value="DOCUMENT"/> <property name="ws.file" value="${ws.name}.wsdl"/> <property name="destName" value="topics.general"/> <property name="destType" value="TOPIC"/> <property name="cfName" value="TopicConnectionFactory"/> <property name="jndiFactory" value="${EWM_JNDI_FACTORY}"/> <property name="jndiUrl" value="${EWM_JNDI_URL}"/> <property name="urlProps" value=""/> <property name="extraClasses" value="java.lang.String"/> <property name="ws.url" value= "jms:/${destName}?domain=${destType}& vendor=JNDI&java.naming.factory.initial=${jndiFactory}&java.naming.provi der.url=""> alse&${urlProps}"/> <axis-java2wsdl classname="${ws.class}" output="${APP_BUILD_DIR}/wsdl/${ws.file}" location="${ws.url}" namespace="urn:${ws.name}"> <classpath> <pathelement path="${classes}"/> </classpath> </axis-java2wsdl> </target> Jim Stafford wrote:
|
- deserialization error: no deserializer is registered Sesha Shayan Nandyal
- Re: deserialization error: no deserializer is re... Anne Thomas Manes
- RE: deserialization error: no deserializer is re... FONTDEVILA Diego
- Re: deserialization error: no deserializer i... Sesha Nandyal
- Re: deserialization error: no deserializer i... Jim Stafford
- Jim Stafford