Diskussion:Release 0.4 - Versionsgeschichte

Holtermp am 30. März 2017 um 14:04 Uhr

2017-03-30T14:04:45Z

Bachemj am 27. März 2017 um 13:50 Uhr

2017-03-27T13:50:35Z

Holtermp am 27. März 2017 um 09:40 Uhr

2017-03-27T09:40:28Z

Holtermp: First impressions of prorgamming with the API.

2017-03-27T09:00:42Z

First impressions of prorgamming with the API.

Neue Seite

To get a feel for the API I created a temporary WSDL with two operations "quote" and "book".
From this I created a dummy java web application (WAR) using "wsimport" and played around with it a little.

Here are my first impressions and suggestions:

* Generation of code works fine with only one little problem:
** There are a few abstract types in the definitions, e.g. "StringCommonTravellerType". This prevented travellers to be created from the input xml request at runtime.
** So for the time being, I removed all four "abstract=true" statements in my local copy of the xsds. We should look into this.
* We should get rid of the "String"-Prefix of every type name.
** It just causes names to be longer without any additional information.
** It makes code completion features in IDEs difficult to use, if everything starts with "String...".
* Maybe we can get rid of redundant collection containers, i.e. if we have a ''<services/>'' element we do not need a ''<service/>'' element below that which in turn contains the concrete element ''<Accommodation/>'' . We should eliminate the generic ''<service/>'' element in between:

Currently we have to write:
<pre>
<ns2:Services>
<ns2:Service>
<ns2:Accommodation>
<ns2:Identifier>DUMMY_TEST_RESULT</ns2:Identifier>
<ns2:EndDate xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns2:Stay xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ns2:Accommodation>
</ns2:Service>
</ns2:Services>
</pre>
Which could be written more concise as:
<pre>
<ns2:Services>
<ns2:Accommodation>
<ns2:Identifier>DUMMY_TEST_RESULT</ns2:Identifier>
<ns2:EndDate xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns2:Stay xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ns2:Accommodation>
</ns2:Services>
</pre>

← Nächstältere Version		Version vom 30. März 2017, 14:04 Uhr
Zeile 40:		Zeile 40:
	<hr>		<hr>
	I (bachemj) agree to the removal of String* and *Type of type names as they indeed are redundant.		I (bachemj) agree to the removal of String* and *Type of type names as they indeed are redundant.
		+
		+	(pholtermann): I also still think the name "String" for the project is problematic. IMHO the association with the programming data type "String" is to strong. (An alternative name could be '''T'''ravel '''A'''pplications '''N'''ext '''G'''eneration '''A'''PI :)

← Nächstältere Version		Version vom 27. März 2017, 13:50 Uhr
Zeile 37:		Zeile 37:
	</ns2:Services>		</ns2:Services>
	</pre>		</pre>
		+
		+	<hr>
		+	I (bachemj) agree to the removal of String* and *Type of type names as they indeed are redundant.

@@ Zeile 10: / Zeile 10: @@
 ** It just causes names to be longer without any additional information.
 ** It makes code completion features in IDEs difficult to use, if everything starts with "String...".
 * Maybe we can get rid of redundant collection containers, i.e. if we have a ''<services/>'' element we do not need a ''<service/>'' element below that which in turn contains the concrete element ''<Accommodation/>'' . We should eliminate the generic ''<service/>'' element in between: