Ravi, It says argument type mismatch.. This makes me wonder if you have created a right kind of an elements for the data types selected for your input and output mapping?? Since your error is happening during the creation of incidents, you should specifically look at input mappings..
Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Ravi Sent: Monday, September 17, 2007 8:04 AM To: [email protected] Subject: Webservice Creation Issues Remedy 7.0 Midtier: weblogic Hi: Reposting question, since I am noticing some additional unusual behaviors. Wondering if anyone out there has this. I am creating a webservice and flushing the cache in the mid-tier after that. Towards the end of the webservice XML, after the cache flush, I see the following (the port binding and name are not as I was expecting) <wsdl:service name="Notification_V1Service"> -<wsdl:port binding="s0:PortSoapBinding" name="PortSoap"> <soap:address location="http://reweblogicp01:80/arsys/services/ARService?server=rearsp01&w ebService=Notification_V1"/> The above webservice results in a "java.lang.IllegalArgumentException: argument type mismatch" when I try to submit a new incident. After a few hours or few days, sometimes this changes to what I am expecting in the webservice xml file. The same submit that did not work previously works now. <wsdl:service name="Notification_V1Service"> -<wsdl:port binding="s0:Notification_V1SoapBinding" name="Notification_V1Soap" <soap:address location="http://reweblogicp01:80/arsys/services/ARService?server=rearsp01&w ebService=Notification_V1"/> Is there anything else I need to do when I create a new webservice other than flushing? I have even tried restarting the webservice. Thanks Ravi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
