Daniel P. Berrange 615bdfda07 rng: fix port number range validation ... The PortNumber data type is declared to derive from 'short'. Unfortunately this is an signed type, so validates the range [-32,768, 32,767] which excludes valid port numbers between 32767 and 65535. We can't use 'unsignedShort', since we need -1 to be a valid port number too. This change is to use 'int' and set an explicit max boundary instead of relying on the data types' built-in max. One of the existing tests is changed to use a high port number to validate the schema. https://bugzilla.redhat.com/show_bug.cgi?id=1214664 Signed-off-by: Daniel P. Berrange <berrange@redhat.com>		2015-04-23 12:59:52 +01:00
..
basictypes.rng	rng: fix port number range validation	2015-04-23 12:59:52 +01:00
capability.rng
domain.rng	conf: set up for per-grammar overrides in schemas	2014-04-15 21:07:59 +02:00
domaincaps.rng
domaincommon.rng	rng: Move sgio attr definition to a separate block	2015-04-20 10:13:36 +02:00
domainsnapshot.rng
interface.rng	interface: allow multiple IPv4 addresses in interface XML	2015-04-06 13:27:15 -04:00
Makefile.am
network.rng	schema: Fix interface link state schema	2015-03-03 09:43:13 +01:00
networkcommon.rng	RNG schema: allow plain @floor to <bandwidth/>	2015-04-16 09:07:43 +02:00
nodedev.rng	SRIOV NIC offload feature discovery	2015-03-05 11:31:05 +01:00
nwfilter.rng
secret.rng
storagecommon.rng
storagepool.rng
storagevol.rng