qualified names vs. multiRefs

[Dan Stone <da...@qsent.com>]

My AXIS RPC service takes a bean for an argument. This bean contains an
array of another bean.
The server is configured to map these beans based on qualified names as
defined in the beanMappings in the server-config.wsdd.

.NET clients are able to create requests to the service that use the
necessary qualified name.
My AXIS client is not.  I get a 'Server.NoService' fault.

The problem seems to stem from the 'multiRef' labeling of the array
elements.

If I change 'multiRef' to the qualified name of the type of bean in the
array (as defined in the beanMappings), and manually POST the SOAP Envelope
to the end-point, I can get the service to recognize the type and things
work great...

example -
DOESN'T WORK:
<multiRef id="id1" xsi:type="ns4:Request" xmlns:ns4="someNS">....

DOES WORK:
<ns4:Request id="id1" xsi:type="ns4:Request" xmlns:ns4="someNS">....


Can anyone shed some light here? This only seems to cause difficulties
within the array, because I DON'T need to alter the 'multiRef' name of the
bean that CONTAINS this array and the service recognizes ITS correct type!

I have tried with multiRefs 'off' on the client, and the service still can't
seem to recognize the beans...

Is there a way to define the qualified name for the array elements? 

Thanks,

Dan Stone