Thanks for the hint.
But the following hierachy works fine:
public abstract class WsOrderDto implements java.io.Serializable
{
private java.lang.String orderNumber;
private java.lang.String primaryKey;
...
}
public class WsOrderDtoV1 extends ams.seci.webservice.dto.WsOrderDto implements
java.io.Serializable
{
private java.lang.Long producedNotOkRepairableQuantity;
....
}
Hasn't anybody expierenced problems with class hierachies deeper than 2 levels ?
Ingo
-----Ursprüngliche Nachricht-----
Von: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 03. April 2007 15:40
An: [email protected]
Betreff: Re: Problems with inheritance
As a general rule, you don't want to expose abstract types through your service
interface. Many SOAP toolkits cannot cope with abstract types and substitution
groups.
Anne
On 4/3/07, Hackl Ingo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a problem when I create the wsdl-file for the following class
> hierachy.
>
> public abstract class WsSetPointDto implements java.io.Serializable {
> ...
> }
>
> public abstract class WsSetPointDtoV1 extends WsSetPointDto implements
> Serializable {
> private String typeNumber;
> private String machineStructureName;
>
> ...
> }
>
> public abstract class WsSetPointMachineStructureComponentDtoV1 extends
> WsSetPointDtoV1 implements Serializable
> {
> private int cycleTime;
> private float quantityPerCycle;
> private float maxNotOk;
> private float availability;
> private double desiredQuantityPerHour;
> private int timePerQuantity;
>
> ...
> }
>
> public class WsSetPointBasicSystemDtoV1 extends
> WsSetPointMachineStructureComponentDtoV1 implements Serializable {
> }
>
> The generated wsdl-file looks like the following:
>
> <complexType abstract="true" name="WsSetPointDto">
> <sequence/>
> </complexType>
> <complexType abstract="true" name="WsSetPointDtoV1">
> <complexContent>
> <extension base="tns2:WsSetPointDto">
> <sequence/>
> </extension>
> </complexContent>
> </complexType>
> <complexType abstract="true"
> name="WsSetPointMachineStructureComponentDtoV1">
> <complexContent>
> <extension base="tns2:WsSetPointDtoV1">
> <sequence/>
> </extension>
> </complexContent>
> </complexType>
> <complexType name="WsSetPointBasicSystemDtoV1">
> <complexContent>
> <extension base="tns2:WsSetPointMachineStructureComponentDtoV1">
> <sequence/>
> </extension>
> </complexContent>
> </complexType>
> </schema>
>
> So the <element name>-tags for all attributes are missing. This error
> only occurs if the class hierarchie has more than two levels. Is there
> a general restriction that class hierachies can only have two levels
> or is this a bug ? Is there a work around for this problem ?
>
> Thanks
>
> Ingo
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
