READERNAME CATEGORY Handler.java - Revision history

Jmaine at 00:05, 24 November 2008

2008-11-24T00:05:38Z

Jmaine at 00:04, 24 November 2008

2008-11-24T00:04:51Z

Jmaine at 23:32, 23 November 2008

2008-11-23T23:32:01Z

Kyle at 00:33, 12 February 2008

2008-02-12T00:33:57Z

Kyle: /* Reference Implementation */

2008-02-07T02:03:37Z

‎Reference Implementation

Kyle: /* Return Value */

2008-02-07T02:01:37Z

‎Return Value

Kyle at 22:49, 6 February 2008

2008-02-06T22:49:49Z

Kyle: New page:

public CommandObject commandName(CommandObject arg, AbstractReaderSharedResources asr)

2008-02-06T21:44:57Z

New page: <pre>public CommandObject commandName(CommandObject arg, AbstractReaderSharedResources asr)</pre>

New page

<pre>public CommandObject commandName(CommandObject arg, AbstractReaderSharedResources asr)</pre>

@@ Line 2: / Line 2: @@
 The Handler method class is made up of handler methods.  These are special methods designed to take care of one specific reader level command.  For example, when you send a 'get taglist' command to the alien reader, it does the actual work of scanning the radio and getting tags in the taglist command handler.  A handler method class usually has more than one command handler in it, and readers normally have more than one handler method class.  The handler methods can usually be divided up by the type of the command.  For example, in the LLRP reader, the command that deal with ROSpecs are in a different file from the commands dealing with AccessSpecs.
-Each Handler method must registered in the [[emulator.xml]] file. Please see it for how do it.
+Each Handler method must registered in the [[reader.xml]] file. Please see it for how do it.
 =Command Handler Method=

@@ Line 2: / Line 2: @@
 The Handler method class is made up of handler methods.  These are special methods designed to take care of one specific reader level command.  For example, when you send a 'get taglist' command to the alien reader, it does the actual work of scanning the radio and getting tags in the taglist command handler.  A handler method class usually has more than one command handler in it, and readers normally have more than one handler method class.  The handler methods can usually be divided up by the type of the command.  For example, in the LLRP reader, the command that deal with ROSpecs are in a different file from the commands dealing with AccessSpecs.
-Each Handler method must registered in the [[reader.xml]] file. Please see it for how do it.
+Each Handler method must registered in the [[emulator.xml]] file. Please see it for how do it.
 =Command Handler Method=

← Older revision		Revision as of 23:32, 23 November 2008
Line 2:		Line 2:
	The Handler method class is made up of handler methods. These are special methods designed to take care of one specific reader level command. For example, when you send a 'get taglist' command to the alien reader, it does the actual work of scanning the radio and getting tags in the taglist command handler. A handler method class usually has more than one command handler in it, and readers normally have more than one handler method class. The handler methods can usually be divided up by the type of the command. For example, in the LLRP reader, the command that deal with ROSpecs are in a different file from the commands dealing with AccessSpecs.		The Handler method class is made up of handler methods. These are special methods designed to take care of one specific reader level command. For example, when you send a 'get taglist' command to the alien reader, it does the actual work of scanning the radio and getting tags in the taglist command handler. A handler method class usually has more than one command handler in it, and readers normally have more than one handler method class. The handler methods can usually be divided up by the type of the command. For example, in the LLRP reader, the command that deal with ROSpecs are in a different file from the commands dealing with AccessSpecs.

		+	Each Handler method must registered in the [[reader.xml]] file. Please see it for how do it.
	=Command Handler Method=		=Command Handler Method=

← Older revision		Revision as of 00:33, 12 February 2008
Line 1:		Line 1:
		+	[[category:developerDoc]][[category:emulatorDoc]]
	The Handler method class is made up of handler methods. These are special methods designed to take care of one specific reader level command. For example, when you send a 'get taglist' command to the alien reader, it does the actual work of scanning the radio and getting tags in the taglist command handler. A handler method class usually has more than one command handler in it, and readers normally have more than one handler method class. The handler methods can usually be divided up by the type of the command. For example, in the LLRP reader, the command that deal with ROSpecs are in a different file from the commands dealing with AccessSpecs.		The Handler method class is made up of handler methods. These are special methods designed to take care of one specific reader level command. For example, when you send a 'get taglist' command to the alien reader, it does the actual work of scanning the radio and getting tags in the taglist command handler. A handler method class usually has more than one command handler in it, and readers normally have more than one handler method class. The handler methods can usually be divided up by the type of the command. For example, in the LLRP reader, the command that deal with ROSpecs are in a different file from the commands dealing with AccessSpecs.

@@ Line 13: / Line 13: @@
 ==Reference Implementation==
-This is the commandNotFoundError in the alien reader
+This is a command handler in the symbol reader.  All this handler method does is return four bytes.  It places the bytes in the first slot in the RetrunValue array in the command object.  This return value will then later be processed into an outgoing message by the formatter.
 <pre>
-	public ArrayList<Object> commandNotFoundError(ArrayList<Object> arg,
+public CommandObject setSystemParameter(CommandObject arg, AbstractReaderSharedResources asr) {
-			CommandObject obj) {
+    byte[] setSystemParam = { 0x04, 0x06, 0x27, 0x00 };
-		String message = "";
+    arg.getReturnValue().add(setSystemParam);
-		for (Object i : arg) {
+    return arg;
-			message += i.toString();
-−
-		message = "Error 1: Command not understood" + message;
-		ArrayList<Object> returnValue = new ArrayList<Object>();
-		returnValue.add(message);
-                return returnValue;
-−
-−
 </pre>

@@ Line 10: / Line 10: @@
 ==Return Value==
-An array of objects where the first object in the array is a message to be sent back to the client.
+A command object where the first object in the commandObject's return value array is the return value of the funtion
 ==Reference Implementation==

← Older revision		Revision as of 22:49, 6 February 2008
Line 1:		Line 1:
		+	The Handler method class is made up of handler methods. These are special methods designed to take care of one specific reader level command. For example, when you send a 'get taglist' command to the alien reader, it does the actual work of scanning the radio and getting tags in the taglist command handler. A handler method class usually has more than one command handler in it, and readers normally have more than one handler method class. The handler methods can usually be divided up by the type of the command. For example, in the LLRP reader, the command that deal with ROSpecs are in a different file from the commands dealing with AccessSpecs.

		+	=Command Handler Method=

	<pre>public CommandObject commandName(CommandObject arg, AbstractReaderSharedResources asr)</pre>		<pre>public CommandObject commandName(CommandObject arg, AbstractReaderSharedResources asr)</pre>
		+
		+	==Arguments==
		+	#arg - The incoming command
		+	#asr - abstract shared resources
		+
		+	==Return Value==
		+	An array of objects where the first object in the array is a message to be sent back to the client.
		+
		+	==Reference Implementation==
		+	This is the commandNotFoundError in the alien reader
		+	<pre>
		+	public ArrayList<Object> commandNotFoundError(ArrayList<Object> arg,
		+	CommandObject obj) {
		+	String message = "";
		+	for (Object i : arg) {
		+	message += i.toString();
		+	}
		+	message = "Error 1: Command not understood" + message;
		+	ArrayList<Object> returnValue = new ArrayList<Object>();
		+	returnValue.add(message);
		+	return returnValue;
		+
		+	}
		+
		+	</pre>