Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Employee
29 Views

SOAP request can't be parsed by AMT ?

hello

i am trying some simple things with AMT over SOAP, but right now it doesn't work
I am listening messages at the socket level
between a working and non working software
using different SOAP stacks.
First one is working, second one can't be parsed by AMT.

would you have an idea ?
thanks, paul.




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">


xmlns="http://schemas.intel.com/platform/client/RemoteControl/2004/01"/>


OK



xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">


xmlns="http://schemas.intel.com/platform/client/RemoteControl/2004/01"
xmlns:ns2="http://schemas.intel.com/platform/client/Common/2006/01"/>


returns
a:Client
Failed to parse the request

0 Kudos
8 Replies
Highlighted
Employee
29 Views


Hi Paul,
I'm not an expert on the syntax, but I believe it has something to do with the second line in the GetSystemPowerState call--- xmlns:ns2="http://schemas.intel.com/platform/client/Common/2006/01"/

You mention using differnt stacks. How are you generating each of these request messages?

I'm trying to find someone with more experience in this area to take a look.
0 Kudos
Highlighted
Employee
29 Views


One of my collequges looked this over and tried some things and found that the ":ns2" part of the second line of the requestis whatseems to becausing the problem.

The second namespace alone should not be a problem, just those specific characters on that line.
0 Kudos
Highlighted
Employee
29 Views


One of my collequges looked this over and tried some things and found that the ":ns2" part of the second line of the requestis whatseems to becausing the problem.

The second namespace alone should not be a problem, just those specific characters on that line.

Hello

The working one was generated with apache axis for java.
axis is in fact discontinued and should not be used anymore.

The second one (not working) was generated by the soap engine
included in java6 from sun (replacing axis and other stacks).
It's the standard, included in the JVM, and used in
countless enterprise class web services systems.
the class files were generated by wsimport, a tool included in the java SDK.

So i think the SOAP engine is rather bulletproof,
but i may configure it the wrong way or course,
or the WSDL files could be wrong,
or the AMT engine parser (let's hope not).

I used the WSDL files from the rdk, but you may have
recent, upgraded WSDL ?

regards, paul
0 Kudos
Highlighted
Employee
29 Views

You can try the WSDL files in the latest SDK available here.
The files can be found in ./DOCS/WSDL
0 Kudos
Highlighted
Employee
29 Views

You can try the WSDL files in the latest SDK available here.
The files can be found in ./DOCS/WSDL

hello

i already had the 5.1 version, but i've redownloaded the sdk,
replaced the WSDL and recompiled.
same thing.

I tried with another service : RemoteAccessAdminInterface.wsdl
same thing

BUT i tried with another AMT computer and it works !
same WSDL, same code, same binary, same SOAP messages generated,
just the hostname changing.

The working machine is a good old lenovo T61
the non working machine is a brand new lenovo W500.
I've just upgraded the BIOS, doesn't help

Strange, the generated SOAP message is the same !

The conclusion is that Java JAX-WS SOAP messages
are not understood by AMT on some machines.

regards, paul.
0 Kudos
Highlighted
Employee
29 Views

Thanks for the info Paul.

I will try to find out if this is a known compatibility issue or a bug.

Can you provide the AMT versions on the two systems?
0 Kudos
Highlighted
Employee
29 Views

Thanks for the info Paul.

I will try to find out if this is a known compatibility issue or a bug.

Can you provide the AMT versions on the two systems?

AMT ME versions :
T61 : 2.5.18.0000 (working)
W500 : 4.0.4.0006 (not working)
0 Kudos
Highlighted
Employee
29 Views


Thanks Paul, we are working on this and may file a bug if we cannot find an explanation.
I'll let you know.
0 Kudos