I have fixed it locally, but I have been too busy to submit the patch yet. I hope to do it later today or tomorrow!

-Øyvind

On Thu, 2006-03-30 at 10:21 +0800, ray wrote:
This is also my problem.Have you solved it?Thx.

On 2/3/06, Øyvind Matheson Wergeland <[EMAIL PROTECTED]> wrote:
On Fri, 2006-02-03 at 12:51 +0100, Mika Göckel wrote:
> are you talking of inheritance in the schema definition?

Yes, I am.

> The problem with that is, it contradicts basic profile (www.ws-i.org)
> interoperability.

I just searched the WS-I Basic Profile 1.1, and I only found a
restriction for arrays:
R2110  In a DESCRIPTION, declarations MUST NOT extend or restrict the
soapenc:Array type.

But - if not using inheritance, how should the following example be
mapped to WSDL then?

abstract public class Animal {
  // Has property 'name'
}

public class Mammal extends Animal {
  // Has property 'legs'
}

public class Bird extends Animal {
  // Has property "wingspan"
}

public class AnimalService {
  public void storeAnimal(Animal animal)
}

Is it the in-message for storeAnimal that must declare that it accepts
either of Animal's concrete implementations?

> P.S.: Do you mean XFIRE-247 by you solved your problem? I just committed
> something that seems to fix it, could you test if it does?

The fix for maps is okay - thanks for including it so quickly! The
superclass mappings are still ignored though, but the workaround still
works, so it's no hurry for me. :)

-Øyvind

Reply via email to