Order of generating Classes / Dependencies about soap-client HOT 5 CLOSED

Hi @tknuppe,

Some questions:

• Can you tell me more about your use-case?
  -Are you talking about XSD complex types that extend a different complex type? (I am not sure how ext-soap handles these.)
• Can you provide me a WSDL for this?

The ExtendAssembler was not created for this purpose but for extending an existing class to e.g. provide ways to place collection code in an abstract class.

I would prefer to keep both the constructor and jsonserializeable they way they are in this package. Unless you have a very common use-case.

from soap-client.

Yes, a complex type extending another complex type. Sorry I cannot give you the WSDL but I could try to give you an excerpt:

<xs:complexType name="MarkenAuftrag"> <xs:complexContent mixed="false"> <xs:extension base="tns:BasisAuftrag"> <xs:sequence/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="MarkenAuftrag" nillable="true" type="tns:MarkenAuftrag"/> <xs:complexType name="BasisAuftrag"> <xs:sequence> <xs:element minOccurs="0" name="Auftragsnummer" nillable="true" type="xs:string"/> <xs:element minOccurs="0" name="Eingangsdatum" nillable="true" type="xs:dateTime"/ </xs:sequence> </xs:complexType> <xs:element name="BasisAuftrag" nillable="true" type="tns:BasisAuftrag"/>

What if I edit the constructor and jsonserializable assember and implement a switch to turn the function on (off by default)? I just call the parent __construct and jsonSerialize functions to handle the case. You can decide when I create the pull request. I don't want to force you into this. It could be useful for others, too.

The only other way for me is to use a fork for the rest of the project lifetime :(

from soap-client.

You could also create a custom assembler inside your project ;)
I'll need a WSDL to see how ext-soap parses this exactly.

from soap-client.

Okay, then I will keep it for now. Actually I don't know if it works. I'm in the middle of developing. The Assemblers are now ready. I have to use the SOAP functions and then I will see if it works.
Thanks for the hint to put the Assemblers into my project. That should do it.

from soap-client.

Update: Doesn't work. I needed to build a static SoapType for that cases. The idea with extending the construct and jsonSerialize functions was good but the SOAP-XML could not be built properly.

from soap-client.