ok.. more testing shows the following; the above described scenario applies to ejb's exposing a web-service. When they also act as a ws-client, jbossws behaves slightly different;
We have generated client stubs from existing docliteral wsdls using wscompile and added the according service-refs. wscompile generates the same type of mapping files as described above.. our findings for the client calls are: 1) "outgoing" serialization from our client (ie the request) needs the above mentioned modifications to work 2) "incoming" deserialization (ie the remote response) works without modifications (!), ie for response elements/complexTypes jbossws correctly finds these in the generated mapping file ok.. next step is to test all the above with nodatabinding, both as server and client.. stay tuned.. /Ole View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867031#3867031 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867031 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
