When JBossWS deploys a WS it generates the Axis propriatary wsdd deployment
descriptor, which is saved for debugging in ${server.data.dir}/wsdl/[deployment]
It introspects the types being used by the SEI and also scannes the
jaxrpc-mapping.xml for any additional (nested) types.
What you are seeing is a mismatch of Axis operation description from the wsdd
and the actual SEI signature. Inspect your jaxrpc-mapping and the generated
wsdd then you will probably find the mismatch to your SEI.
In the new JBossWS implementation you will be able to use annotations. These
sync problems will then be history.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857140#3857140
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857140
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
