Russell Butek
[EMAIL PROTECTED]
---------------------- Forwarded by Russell Butek/Austin/IBM on 06/21/2002 09:15 AM ---------------------------
To: [EMAIL PROTECTED]
cc:
From: Russell Butek/Austin/IBM@IBMUS
Subject: Re: Call object and properties
Importance: Normal
We're on your side. We fought for precisely your scenario when JAX-RPC was being written. Unfortunately we sort of lost and now we must comply with JAX-RPC. It says you can't set/get an unsupported property, but doesn't really define what unsupported means.
A possible solution is to require your handler to register the properties it needs. Then your property is no longer "unsupported". I don't like this myself. I prefer a bit more freedom.
Another solution might be to call all properties that start with "org.apache.axis." supported.
We don't want you to be broken, but we have to follow the spec. It remains to be seen how we can satisfy both.
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Call object and properties
Hi,
In Beta 2 I used the following trick: in the stub generated
by WSDL2Java I set some properties, which were used by a client
side handler later. Now I fetched yesterday's nightly build, and
I try to execute the same test. Now it gives me a failure, because
the Call object will accept only properties listed in the Call
class, and nothing more. How can I set named properties then ?
Will this support be discontinued, or is this just a temporary
situation in this nightly build ? Maybe we have an other way to do this ?
Help with this please, because if I fail with this, I'll probably
will have to rewrite my whole project. :(((
- Br, Geza
