I asked a similar question earlier but got no reply,
so I'll try again.
Taking the EJB sample, the Run.java has code that maps
the types to specific java classes:
service.mapType(new
QName("http://wsiftypes.addressbook/","Phone";),
Class.forName("ejb.service.addressbook.wsiftypes.Phone"));
For this, the WSDL needs to be run through WSDL2Java
and the mapped java classes (Phone in this case) need
to be generated.
But currently, if the mapping is anything other that
SOAP, none of the WSDL2Java tools that I know of
(Axis, WebSphere 5.1.x etc) will work.
Is this a feature that is "still to be implemented" in
WSIF?
Clearly, the suggested approach of "using a WSDL with
a SOAP binding and then keeping the generated java
classes and deleting the rest" as suggested in the
samples will not work in a production env. So, people
who are planning to use WSIF seriously - are they
supposed to come up with their own implementation of
the WSDL2Java?
Thanks for any reply.
Shantanu Sen
