#43 GetMaxNumberSupported bug of TagField

[Anonymous]

TagField object should have method "GetMaxNumberSupported", this can not be seen from the command list in test client

If construct the xml request manually as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>10</id>
<targetName></targetName>
<tagField>
<getMaxNumberSupported/>
</tagField>
</ns2:command>

Then get response as follow:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:reply xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>10</id>
<resultCode>27</resultCode>
<error>
<name>ERROR_TAGFIELD_NOT_FOUND</name>
</error>
</ns2:reply>

However, GetMaxNumberSupported is a static method, if we keep <targetName> empty, reader should also be able to response correctly.

If you try following request, you will get the right response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>10</id>
<targetName>defaultTagField</targetName>
<tagField>
<getMaxNumberSupported/>
</tagField>
</ns2:command>

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:reply xmlns:ns2="urn:epcglobal:rp:xsd:1">
<id>10</id>
<resultCode>0</resultCode>
<tagField/>
</ns2:reply>

Is "defaultTagField" parameter a must???

[Wang Yun]

Logged In: YES
user_id=2176449
Originator: NO

similar problem also exist in TagSelector