Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some fields are not parsed correctly, getter/setter only for attrib, not for content #3

Closed
bajoodoo opened this issue Nov 14, 2019 · 3 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@bajoodoo
Copy link

For example verwaltung_techn->master has only a method to get its visibility but not its content, the value of the tag. The same goes for the setter.

Similar:
freitexte->objekt_text
freitexte->user_defined_simplefield
preise->aussen_courtage

@mgrundkoetter
Copy link
Member

Hm, the xsd for this part looks like this:

<xsd:element name="aussen_courtage">
	<xsd:annotation>
		<xsd:documentation>Courtage, die der Kunde zu zahlen hat, als Betrag in ? / % / MM, daher Textfeld</xsd:documentation>
		<xsd:documentation xml:lang="en"></xsd:documentation>
	</xsd:annotation>
	<xsd:complexType mixed="true">
		<xsd:attribute name="mit_mwst" type="xsd:boolean">
			<!--Kennzeichen für MWST bei Courtage-->
		</xsd:attribute>
	</xsd:complexType>
</xsd:element>

As there is no type set (should be string), but "mixed" is set to true, I guess we have to take this into account while generating the API classes and expect them to be strings (value) if they do not have structured children. I will not have time to make this changes by the end of 2019, so if anyone wants to open a PR, you're very welcome :-)

@mgrundkoetter mgrundkoetter added bug Something isn't working help wanted Extra attention is needed labels Nov 14, 2019
@mgrundkoetter
Copy link
Member

Hm, seems like the xsd parser cannot handle this as well as the jms serializer. So as long as there is no way for us to read or write the actual value, we have to wait for an implementation in those bundles, I guess.

mgrundkoetter added a commit that referenced this issue Feb 4, 2020
…ovide any information about the "mixed=true" attribute of the xsd node, we have to generate the $value property for every class, although this is not correct.
@mgrundkoetter
Copy link
Member

@bajoodoo I worked on a fix based on the patch provided in goetas-webservices/xsd-reader#50
Can you please try it out? It is in the branch bugfix/issue-3 for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants