- This topic has 16 replies, 3 voices, and was last updated 17 years, 8 months ago by
.
-
Posts
-
Some of the lessons learn in this endeavor was very painful and it was not because ME. This leaves user education on the table for discussion and the ever adoption of BP-I be the industry.
Here is my discovery:
Because ME is a little forward thinking in their approach to Web Services, they have instituted some very good tools at catching errors with the WSDL BEFORE all the code is generated. ME may not be 100% perfect, but it is better than what is currently out there in the industry. This alone is reason for starting fresh with a new WSDL (one can use their old WSDL as a guide) and re-generated the WSDL using ME’s tools. Trying to grab the WSDL from like JBoss4.0.5 will not work…there are issues on how JBOSS created their WSDL that will not pass the tools in ME–validation and BP-I ones. Also there is many cosmetic issues too that makes it real ugly when you use the Web Services Explorer to call methods.
The one issue that kept me steaming the hold time was the services.xml file. I had the wrong style/use combination and it prevented the Web Services Explorer from working properly. Once I fixed this error, I started getting some useful errors. I discovered another issue in the WSDL. This one involved the soapaction attribute within the WSDL. The schema for “http://schemas.xmlsoap.org/wsdl/soap/” requires the soapaction within the operation element to be fully qualified down to the method. My old WSDL (WSAD generated) did not have this. Another good technique I found was drilling down to the WSDL using an external browser. This approach isolated the issues for me–server, WSDL or ME.
The last issue involved the use of an outdated jar file on the server. This impacted only the client code. One needs to ensure they the current common-http-client jar. Once I got all this…..it was all downhill.
From all of my efforts I discovered what one needs to accomplish porting an AXIS framework web service over to a XFire Framework web service. Recall, WSAD 5.1.1 uses an older version of AXIS so the WSDL is not created following Today’s BP-I in every case.
I hope this recap will prevent you from experiencing all the pain I went through. One good thing to note is ME has made it less painful with the new tools in ME 5.5 M1. I could not think of debugging a web service without them! I look forward to ME5.5 M2.
Russ
