"zeeshan.javeed" wrote : Hi, | I have to modify the current webservices developed using old version of Jbossws. Now I have complied the server side with new jbossws 2.0.2 and new wsdl file is generated and deployed. The new client created against this wsdl file using wsconsume works very fine but the old client, created with pervious version are not working. This is a quite common issue for users that have been using old JBossWS versions. If you need to expose a wsdl contract that is exactly the same of your previous one, you should try with the top-down approach. See this for further information: http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools#Top-Down_.28Using_wsconsume.29 This way your service clients should work without changes.
anonymous wrote : After my investigation, I am of the view that problme is due to mapping and document literal style. Earlier code generated a mapping.xml file and now this time no mapping.xml file is generated. So that is the main reason I asked how we can use the Document Literal in a right way. As previously said, the jaxrpc-mapping.xml is not related to the wsdl style you use (Document/literal, rpc/literal, etc.). That mapping file is simply not generated by our jax-ws stack. anonymous wrote : Secondly, my wsdl file is always generated and deployed in Jboss , default/data folder. I wanted to deploy it some other location and with different port , for example 8080 instead of 80, so that i can debug the out put using TCP MON. Can Any body, help me how to | 1) use Document Literal ( so that it generates mapping.xml file ) | 2) change locatoin and port of wsdl file. Is your concern about the wsdl address or the endpoint address? Please take a look at the FAQ to understand how the endpoint address relates to the context configuration (i.e. how you can change that address): http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#How_do_I_know_what_endpoint_address_is_being_used.3F The port used for every endpoints depends on the jboss-web configuration of your application server. You might also be interested in reading how you can configure JBossWS to rewrite the endpoint addresses in the wsdl files (once you download the wsdl, you get the endpoint address from it's contents... and that automatically generated address can be rewritten changing the host and port): http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#How_does_rewriting_of_the_soap_address_in_WSDL_work.3F Finally, it seems to me there has been a little misunderstanding with Richard on what you need to do. The wsdlLocation attribute of @WebService should be used to point the stack to the wsdl location during the deployment phase. As a matter of fact jbossws needs to read the wsdl (if you decide to expose your own one instead of letting it generate it for you) and wsdlLocation specifies the relative URL to the wsdl. You can of course deploy your wsdl as a simple xml file everywhere you want as a simple jboss-web app and then have jbossws read it from there... but imho that's not the suggest way to go. Please give us some further information to better understand your usecase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111744#4111744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111744 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
