Re: Ignore newly added fields to remain compatible
Thank you Ajith, that'll do for me. best, mirco What I can suggest as a work around is to add a user level handler (you might need to write a module. writing modules is very easy) that removes the newly added fields from the XML message. Hence when the message reaches databinding stage it will be seen as a valid message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ignore newly added fields to remain compatible
Hi again, did I miss some hints in the docs regarding this question? Pls would anyone be so kind as to provide me a hint for this as I cannot find related topics to this. thx, mirco Mirco Jeske schrieb: Hi group, I am dealing with a couple of web services facing a problem with newly added fields. One wsdl changed as there was added an additional field. Unfortunately I cannot rebuild my stubs due to heavy release problems. Therefore I would like to configure axis to just ignore this new field. Is there a way to stay compatible as long as the original fields remain available no matter how may new field would haven been added? thanx for any hint, mirco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ignore newly added fields to remain compatible
Hi group, I am dealing with a couple of web services facing a problem with newly added fields. One wsdl changed as there was added an additional field. Unfortunately I cannot rebuild my stubs due to heavy release problems. Therefore I would like to configure axis to just ignore this new field. Is there a way to stay compatible as long as the original fields remain available no matter how may new field would haven been added? thanx for any hint, mirco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with order of parameters
I have been working on this problem for a few days now but still have no solution. Using the WSDL2Java Stub works fine Any hints welcome :-) regards, mirco Mirco Jeske schrieb: Hi List, I built a webservice wich accepts three string parameters as input. I deployed the service to the tomcat5 container. Everything seems to be fine. Now I would like to test the service by calling it from my browser with the following url http://localhost:8080/MyServiceName/services/WorklistServices?method=getPayload&username=someuser&password=mypassword Please find the code of the webservice at the end of this mail. It first writes out the transferred parameters but the assignment is not corrent. The output is "Calling getTaskliste method with user mypassword and password someuser" Since the assignment should depent on the name of the passed parameter I cannot understand why this happens. I then called the service with completely different parameter names http://localhost:8080/MyServiceName/services/WorklistServices?method=getPayload&a=someuser&b=mypassword Output is still "Calling getTaskliste method with user mypassword and password someuser" Any ideas what could be wrong here? Thanx; mirco CODE public String[] getTaskliste(String username, String password) { System.out.println("Calling getTaskliste method with user " + username + " and password " + password ); } WSDL (partly) ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with order of parameters
Hi List, I built a webservice wich accepts three string parameters as input. I deployed the service to the tomcat5 container. Everything seems to be fine. Now I would like to test the service by calling it from my browser with the following url http://localhost:8080/MyServiceName/services/WorklistServices?method=getPayload&username=someuser&password=mypassword Please find the code of the webservice at the end of this mail. It first writes out the transferred parameters but the assignment is not corrent. The output is "Calling getTaskliste method with user mypassword and password someuser" Since the assignment should depent on the name of the passed parameter I cannot understand why this happens. I then called the service with completely different parameter names http://localhost:8080/MyServiceName/services/WorklistServices?method=getPayload&a=someuser&b=mypassword Output is still "Calling getTaskliste method with user mypassword and password someuser" Any ideas what could be wrong here? Thanx; mirco CODE public String[] getTaskliste(String username, String password) { System.out.println("Calling getTaskliste method with user " + username + " and password " + password ); } WSDL (partly) ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]