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 header)

I wonder how someone messed up the WSDL enough to have it try to create a 
structure like that?  I do see that Remedy tries to create with 2 namespaces 
defined (ns0 and ns1), so maybe that is part of it.

Hopefully this gives Pascale enough to correct the problem.

Fred


From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of LJ LongWing
Sent: Friday, September 16, 2011 5:37 PM
To: [email protected]
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 the close tag, you see this
ns1:opCreateTest

Notice the difference in case?....the error may be complaining about the fact 
that you can't close 'Body' because 'opCreateTEST' isn't closed yet.

Export your filter to XML, and correct either the open or the close xml tag, 
re-import, and try again, you may find yourself functional.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
                <soapenv:Header>
                                <ns1:AuthenticationInfo soapenv:actor="" 
soapenv:mustUnderstand="1" xmlns:ns1="urn:testwebWS">
                                                
<ns1:userName>user</ns1:userName>
                                                
<ns1:password>****</ns1:password>
                                                <ns1:authentication/>
                                                <ns1:locale/>
                                                <ns1:timeZone/>
                                </ns1:AuthenticationInfo>
                </soapenv:Header>
                <soapenv:Body>
                                <ns1:opCreateTEST xmlns:ns0="urn:urn:testwebWS" 
xmlns:ns1="urn:testwebWS" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
                                                
<ns1:ProjectNumber>11</ns1:ProjectNumber>
                                                <ns1:Description>this is the 
blah blah for description</ns1:Description>
                                                <ns1:Subject>This is the 
subject of this test</ns1:Subject>
                                                
<ns1:Initiator>ABCCDF</ns1:Initiator>
                                                <ns1:Category>Category 
whatever</ns1:Category>
                                                
<ns1:HourEstimate>1075.00</ns1:HourEstimate>
                                </ns1:opCreateTest>
                </soapenv:Body>
</soapenv:Envelope>

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of [email protected]
Sent: Friday, September 16, 2011 3:45 PM
To: [email protected]
Subject: web service nightmare

**
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 perfectly fine in SoapUI.
I have the pluginserver in debug and all I got is the following below.

We do have a ticket with BMC, but since for them this is a 3rd party publishing 
the web service they can provide more then best effort....  Any one out there 
that knows a whole lot more then I do on web service has any idea what the heck 
is wrong here.  Could this be a Java issue? Apache?

The team publishing the WSDL has no clue either since it is working outside of 
Remedy.

We are running
ARS 7.5 patch 007
Apache/Tomcat 6.0.26
OS Win 2003

Any help would be greatly appreciated


**************************************************************************************

Remedy

2011-09-14 14:53:39,685 INFO  [pool-2-thread-3] 
com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - 
<ARSYS.ARF.WEBSERVICE>Input Env = <soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Header><ns1:AuthenticationInfo
 soapenv:actor="" soapenv:mustUnderstand="1" xmlns:ns1="urn:testwebWS">
                                                
<ns1:userName>user</ns1:userName>
                                                
<ns1:password>****</ns1:password>
                                                <ns1:authentication/>
                                                <ns1:locale/>
                                                <ns1:timeZone/>
                                
</ns1:AuthenticationInfo></soapenv:Header><soapenv:Body><ns1:opCreateTEST 
xmlns:ns0="urn:urn:testwebWS" xmlns:ns1="urn:testwebWS" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
                <ns1:ProjectNumber>11</ns1:ProjectNumber>
                <ns1:Description>this is the blah blah for 
description</ns1:Description>
                <ns1:Subject>This is the subject of this test</ns1:Subject>
                <ns1:Initiator>ABCCDF</ns1:Initiator>
                <ns1:Category>Category whatever</ns1:Category>
                <ns1:HourEstimate>1075.00</ns1:HourEstimate>
</ns1:opCreateTest></soapenv:Body></soapenv:Envelope>
2011-09-14 14:53:39,685 INFO  [pool-2-thread-3] 
com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - 
<ARSYS.ARF.WEBSERVICE>About to invoke
2011-09-14 14:53:39,763 ERROR [pool-2-thread-3] 
com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - 
<ARSYS.ARF.WEBSERVICE>org.xml.sax.SAXException: Bad envelope tag:  Body


************************************************
SoapUI


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:urn="urn:testwebWS">
   <soapenv:Header>
      <urn:AuthenticationInfo>
         <urn:userName></urn:userName>
         <urn:password></urn:password>
         <!--Optional:-->
         <urn:authentication></urn:authentication>
         <!--Optional:-->
         <urn:locale></urn:locale>
         <!--Optional:-->
         <urn:timeZone></urn:timeZone>
      </urn:AuthenticationInfo>
   </soapenv:Header>
   <soapenv:Body>
      <urn:opCreateTest>
         <urn:ProjectNumber>11</urn:ProjectNumber>
         <urn:Description>this is the blah blah for 
description</urn:Description>
         <urn:Subject>This is the subject of this test</urn:Subject>
         <urn:Initiator>ABCCDF</urn:Initiator>
         <urn:Category>Category whatever</urn:Category>
         <urn:HourEstimate>1,075.00</urn:HourEstimate>
      </urn:opCreateTest>
   </soapenv:Body>
</soapenv:Envelope>

Thank you,

Pascale Sterrett
Remedy Technical Lead & Developer
Daimler Trucks North America LLC
Montgomery Park,  9th floor
Portland, OR 97210 U.S.A

Phone:503-745-6569
Email:[email protected]

http://www.daimler-trucksnorthamerica.com





_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to