Hello,
I've posted a similar question to this on the Java forums so apologies
if you've already seen this.
Hi,
I'm using JAX RPC to return an ArrayList of objects. These objects are
of a type that conforms to the defintion of a class that can be returned
in JAX RPC.
In an attempt to get the necessary classes generated for this object I
have added the following to my config.xml:
<typeMappingRegistry>
<additionalTypes>
<class name="com.my.type"/>
</additionalTypes>
</typeMappingRegistry>
I then use this generate the required WSDL with the following command:
wscompile -define -g -d WEB-INF -nd WEB-INF -classpath WEB-INF/classes
config.xml -model WEB-INF/export.gz
Looking at the generated WSDL from this, my class is defined in their as
a complex type with all the correct attributes.
So I then run this to generate the server ties:
wscompile -g -gen:server tie-gen-config.xml
Here, tie-gen-config.xml contains:
<configuration
xmlns="
http://java.sun.com/xml/ns/jax-rpc/ri/config">
<wsdl location="WEB-INF\my.wsdl"
packageName="package.where.my.class.is" />
</configuration>
This runs without error and generates many of the required server side
class files, but not the ones for the class I have specified as an
additional type in config.xml.
Similarly these don't get generated for the client ties either.
Does anyone know why this would be? Am I missing a step? Or some kind
of configuration?
Application classes that are referenced explicitly in my end point
interface have tie classes generated as required. This process only
doesn't seem to work for me when they are not referenced in the
interface but I require them to be returned in a Collection and use the
above config. So, a workaround I have is to create a dummy method to
return the type that I'm having problems with and then the required ties
are generated. But this is not ideal.
Any help will be greatly appreciated.
Many thanks,
Ian.
Ian Jones
Senior Analyst Developer
Piper Group plc
Email: ijones_at_piper-group.com
Tel: + 44 (0) 1454 284900
Fax: + 44 (0) 1454 284950
www.piper-group.com <
http://www.piper-group.com/>
Information contained in this e-mail is intended for the use of the
addressee only, and is confidential and may be the subject of legal
professional privilege. Any dissemination, distribution, copying or use
of this communication without permission of the addressee is strictly
prohibited. The views expressed in this communication may not
necessarily be the views held by Piper Group plc.