ATL - Axis SOAP incompatibility?

[Moshe Kravchik]

Hi all!

I've encountered with what seems to be a compatibility problem between ATL
SOAP Web Service and Axis client.
The minimal scenario is like that. I create a service having the following
function:

struct SITest{

int val;

};

[id(1)] HRESULT PassStructInt([in]SITest data);

When I create the proxy classes using WSDL2Java and try to call this
function, I get back the SOAP fault response and I can see in debugger
console the following lines:

ATL Server only allows href's on arrays and structs.

ATLSOAP: fatal parse error: Unspecified error

I've got the SOAPToolkit trace and I can see that in the request the val
inside the struct is passed using href.

So I've two questions:

1. Is that a known issue and how do I overcome it? I need to pass structures
back and force, it is basic mechanism.

2. What other incompatibilities are waiting for me between ATL and Java?

Thank you,

Moshe.

[WTH]

Just out of curiousity, isn't the default HTTP method of Java a POST?
Doesn't SOAP expect a GET?

Had this problem a week ago helping some Italian Java integrators using a
'open api' SOAP service I'd written. They found a 'GET' http class for Java
by googling for it (really simple actually.)

Don't know if that will help you. We found the problem by looking at the
IIS logs.

WTH

[Moshe Kravchik]

No, it has nothing to do with GET/POST. It indeed uses POST, but the c#
client that uses POST as well work correctly.
The problem is that Axis passes values inside structs by href.

Moshe.
"WTH" <sp*******@Ih8it.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

Just out of curiousity, isn't the default HTTP method of Java a POST?
Doesn't SOAP expect a GET?

Had this problem a week ago helping some Italian Java integrators using a
'open api' SOAP service I'd written. They found a 'GET' http class for Java by googling for it (really simple actually.)

Don't know if that will help you. We found the problem by looking at the
IIS logs.

WTH

[Simon Trew]

Moshe,

I don't know exactly what you mean here, but I know ATL SOAP has problems
with other things-- XML attributes, for example (as hrefs typically are). I
worked around this by making the attribute into a separate, subsidiary
element in the WSDL provided to SPROXY, and then hacking the incoming HTTP
responses and outgoing HTTP requests to correspond to this.

This was for an ATL SOAP client with an Axis server; the other way round, of
course, would have incoming requests and outgoing responses. That is, I only
hacked SendRequest ad GetResponse in my SOAP Client Archetype, but
presumably similar hacks would need to be applied to the corresponding
functions in the server.

Of course this is far from ideal as you have to hack the WSDL every time it
changes (i.e. I hope you have a stable WSDL).

As you say, this has nothing to do with GET/POST.
S.

"Moshe Kravchik" <mkravchik_AT_NO_SPAM_hotmail.com> wrote in message
news:%2******************@TK2MSFTNGP14.phx.gbl...

No, it has nothing to do with GET/POST. It indeed uses POST, but the c#
client that uses POST as well work correctly.
The problem is that Axis passes values inside structs by href.