web service nightmare

2011-09-17 Thread John Baker
Hello, Would it help you understand the problem if I said that, the last time I checked, the AR System webservice consumption code does not implement a 'standardised' approach to consuming webservices? Let me expand. There are three ways a Java developer would normally consume a WS: 1. Generat

Re: web service nightmare

2011-09-16 Thread pascale . sterrett
6569 Email:pascale.sterr...@daimler.com http://www.daimler-trucksnorthamerica.com lj.longw...@gmail.com Sent by: arslist@ARSLIST.ORG 09/16/2011 03:36 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: web service nightmare ** Pascale, I have often found it nic

Re: web service nightmare

2011-09-16 Thread pascale . sterrett
PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: web service nightmare ** Nice catch LJ, I hadn’t looked that closely, but I thought it was a Remedy hosted WS (since I have not seen any other system use the AuthenticationInfo structure that ARS uses in the he

Re: web service nightmare

2011-09-16 Thread Grooms, Frederick W
riday, September 16, 2011 5:37 PM To: arslist@ARSLIST.ORG Subject: Re: web service nightmare ** Pascale, I have often found it nice to put things into 'proper format' to look at them. Below I started looking for tags that didn't match...I found it. You see this ns1:opCreateTEST but in th

Re: web service nightmare

2011-09-16 Thread LJ LongWing
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of pascale.sterr...@daimler.com Sent: Friday, September 16, 2011 3:45 PM To: arslist@ARSLIST.ORG Subject: web service nightmare ** Hi all, I need help with a web service that we are tryi

web service nightmare

2011-09-16 Thread pascale . sterrett
Hi all, I need help with a web service that we are trying to consume within Remedy. We were able to load the WSDL fine (after multiple attempt and corrections). But when we try to consume it, it fails with the error org.xml.sax.SAXException: Bad envelope tag: Body But the same WSDL runs perf